umptious
2/14/2005 11:04:00 AM
> > JC wrote:
>
> So why does the FreeRIDE homepage say: "Unfortunately, the debugger
> still does not work on Windows. We are actively trying to resolve this
> problem."? And why does the Ruby 182-14 install that I downloaded NOT
> having aworking debugger?
Further comments: if I run rubygems, then the debugger semi-works - ie
I can step through code but see the state of variables (which seems
pretty pointless).
Comments:
- Five minutes of documentation would have made using the debugger
such as it is much smooother. Yes, there had been some sort of
"require rubgems" message, but that's not the same as saying "there's
a separate program caled rubygemsetcetc.exe that you if have to run to
make the debugger work" - this looked like a library error at first,
then when I checked the FreeRIDE site simply like a completely broken
debugger.
- A debugger that won't show variable values (if this is the case)
should be documented in the faq and Ride help.
I know these tools are written for volunteers for free, but if want
Ruby to spread the last thing you want is tools that cause FUD. Right
now that's what you have - when even basic tools are this poorly
documented its bound to settle new users. A few minutes documentation
effort would avoid this. You don't have to get the debugger to work,
but you really should document how to switch it on (!) and what its
limitations are. This is literally ten minutes effort.