This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Development Tools (was Re: Patch: New version of "UTF-16 to 'Win32 locale' conversions" and filenames (replacing convertion tables with Win32 API calls))
- From: Mohan Embar <gnustuff at thisiscool dot com>
- To: java-patches at gcc dot gnu dot org
- Date: Sat, 20 Sep 2003 09:09:45 -0500
- Subject: Development Tools (was Re: Patch: New version of "UTF-16 to 'Win32 locale' conversions" and filenames (replacing convertion tables with Win32 API calls))
- Reply-to: gnustuff at thisiscool dot com
Hi Andrew,
> > Okay: first convince my project manager to replace MS Visual Studio
> > with gcc and then we'll talk.... :)
>
>Well, okay. But you don't want to base an entire system's design
>around the limitations of particular debugging environment. gdb can
>debug C and Java, and I'm told Sun have a debugger that can do that
>too.
It's sad, but sometimes, the choice of developer tools is based on
(arbitrary) external influences and is immutable. As such, the design
of the system is sometimes affected. The JNI library example I gave
you is one. Another example is having IBM's VisualAge shoved down
our throats. (Fortunately, we're moving to WSAD/Eclipse now.) In addition
to the nightly tears I'd shed after seeing that marvel of a tool scramble
my source code, I also noted that many developers were using package-private
classes where nested classes would have been called for because
they couldn't set a breakpoint in the nested class in Visual Age. (Or
Visual Rage, as I called it.) In the end, they found a kludgy workaround,
but most continued using package-level classes.
(I clandestinely installed JBuilder 4, which didn't have the licensing restrictions
that subsequent versions had, but that's another story.)
-- Mohan
http://www.thisiscool.com/
http://www.animalsong.org/