From:	"Sven A. Havemann" <havemann AT uran DOT informatik DOT uni-bonn DOT de>
Date:	Wed, 22 Mar 1995 14:45:53 -0800
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	What will djgpp 2.0 contain?

Dear DJGPPers!
==============

I found that:

On Mar 21,  6:21pm, Eli Zaretskii wrote:
> top of 16-bit, real-mode DOS without go32 helping it.  In DJGPP
> v2.0, go32.exe will go32 away (pun intended), and you will only
> need a DPMI server, but that dream is still a few months away.
>-- End of excerpt from Eli Zaretskii

Now I wonder: WHAT WILL DJGPP 2.0 BE LIKE?

We're a bit curious about any new feature that might be contained in djgpp
because we have been spent some work in order to keep portability between DOS
and unix (i. e. SUN, SGI, Linux) in programming a fairly big software package
at the University of Bonn, and we found the differences between various
compilers especially annoying. I know that djgpp cannot be faster than the GNU
stuff in developing new features, but maybe it would be enlightening to know a
little bit more about the future releases of DJGPP as well as coming GNU stuff.

Is there any way to contact people who are concerned with including features as
repository directories for templates, exceptions, RTTI, foundation classes and
so on? - When is #pragma interface/implementation going to die? What IS 'in
transition' and what will remain meriting the efforts to 'program around'? -
What is the 'compiler avantgarde' in the gcc group planning?

I really have the impression that there are more activities in fairly exotic
things such as to adapt GCC to Objective C and ADA than to SIMPLY BUILD A
COMPILER THAT WORK ACCORDING TO THE SPECIFICATIONS OF THE ANNOTATED C++
STANDARD. - I would really like C++ if there was one.

Still I AM a big fan of djgpp and I did a lot for making it popular in our
group, so please take my remarks as constructive critics and do not feel
offended. - I got a little nerved by adapting to different versions of four
compilers on four platforms, and I am not the only one, I know.

                                   Your's, Sven Havemann.

- Raw text -