[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[dist-obj] RE: Native Java compilers ?
The short answers are:
(a) you don't use or see the C tools directly when you work in Eiffel. You
use a C debugger about as often as you use an assembly-level debugger when
you code in C++, get my drift?
(b) the Boehm-Demers-Weiser is still the most popular free GC for C/C++.
There are a couple of commercial alternatives as well these days; they seem
to come and go over the years. Finally, note that garbage collection is
now "native" to gcc 3, so you have a built-in derivative to use as well.
There are several GC FAQs and similar online that give you all the options.
Intelligently coded C++ isn't *that* bad, though I'd *always* investigate
my other options...
Joseph R. Kiniry http://www.cs.caltech.edu/~kiniry/
California Institute of Technology ID 78860581 ICQ 4344804
--On Monday, September 24, 2001 04:15:58 AM -0700 Dmitri Kondratiev
> --- "Joseph R. Kiniry" wrote:
>> Must you use Java?
>> In our experience at DALi, the native code compilers
>> for Java just simply
>> were not up-to-snuff. The cutting-edge JITs did
>> better in many cases, the
>> compilers didn't have either complete language or
>> core library coverage,
>> there were a variety of deployment issues, etc. Why
>> not just go with an
>> available, superior language on QNX like Eiffel?
> I got your point. And thanks for sharing your
> experience with Java native code compilers.
> Eiffel may be a good idea but I don't know anything
> about Eiffel compilers supporting QNX.
> Besides I never programmed in Eiffel myself. On the
> other hand I have two people who created Visual Eiffel
> working with me now in my new team. From them I know
> that Small Eiffel and Visual Eiffel too generate C
> code that can be compiled along with glibc on QNX. So
> we can try these, I think.
> Another problem with compilation of high-level
> language source (such as Eiffel, Java) to C source is
> debugging on the target platform. The main question
> here is how good is a mapping of high-level classes
> and other constructs to C.
> In other words is it easy to understand how the code
> you are debugging relates to the original program
> source. I'll try to find this out for GCJ case at
> least, and may be for Eiffel too, and share the
> results with anybody interested in this.
> Well, but we still have buisness requirement to
> produce working prototype in two month from now.
> Because of that well balanced C++ coding rules may be
> the only solution for this release.
> That's why I also need suggestions on the good C++
> containers and garbage collector libraries.
> Thanks !
To manage your subscription, mailto:email@example.com
Archives, FAQ, etc. http://www.distributedcoalition.org/mailing_lists/