In message
Curt said:
Thanks Stephen, for your input below. I don't recall those facts
coming out in the previous thread so I will add your comments in to
the mix.
Sorry, I don't read all threads, must have missed it. I track a lot of
newsgroups, looking for various things and can't read everything. I'm
not yet good enough at Ruby to discuss the finer points most of you
discuss (I simply don't get the chance to write much Ruby in my work and
I'm far too busy or tired to do it in my spare time). Still despite
that, Ruby is up there with my favourite languages, C++ and assembly
For what its worth I vote to stick with VC6 (or some other form of
Visual Studio). It makes working on the Ruby code a lot easier,
especially if you have to drop into the debugger.
I can understand some open source purists may want to go some other
direction so they can have an open source debugger such as gdb etc.
I'm interested in using the best tool for the job, so its Visual Studio
if you are on Windows. I'd imagine that anyone that works on Windows
will already have Visual Studio and won't want to learn (or re-learn in
my case) emacs/gdb (*) as debugging combination.
I'm hoping to get some time later this year to do the work I said I'd do
on the memory allocation tracker and some other stuff. I won't do this
work if it moves away from Visual Studio. It will then be too much
effort. This will most likely before you get to choose which direction
to go.
Stephen
(*) I'm pretty sure emacs is what caused my RSI what with all the
Alt-this Ctrl-that key combinations. So I'm going to resist going there
as an IDE.
