From: "Vic" <noway AT somewhere DOT com>
Newsgroups: comp.os.msdos.djgpp
References: <%vPy5.1883$C7 DOT 75408 AT wagner DOT videotron DOT net> <n6tnss08pgbeb998e8vfavvgj0etuvod71 AT 4ax DOT com>
Subject: Re: DJGPP and C++ standard
Lines: 23
Organization: none
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Message-ID: <R7Uy5.3173$C7.96357@wagner.videotron.net>
Date: Fri, 22 Sep 2000 21:56:57 -0400
NNTP-Posting-Host: 24.200.220.117
X-Complaints-To: abuse AT videotron DOT net
X-Trace: wagner.videotron.net 969674353 24.200.220.117 (Fri, 22 Sep 2000 21:59:13 EDT)
NNTP-Posting-Date: Fri, 22 Sep 2000 21:59:13 EDT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


Jason Green <news AT jgreen4 DOT fsnet DOT co DOT uk> wrote in message
news:n6tnss08pgbeb998e8vfavvgj0etuvod71 AT 4ax DOT com...
> The real difference in standards compliance is between those compiler
> writers that are working very hard towards the standard, and those
> that show contempt for any open standards and no intention of becoming
> compliant.  Guess which categories GCC and VC fall into...

so I should assume GCC is as compliant as you can get to the latest C++
draft?

> > will I have any problem compiling C++ code for a class that doesn't even
> > touch classes (stops at pointers)
>
> Sorry, I don't understand the question.  Can you rephrase this?

I mean, the C++ used in the class will be of the IO kind (like ios::setw()
and all that IO manipulations stuff), nothing related to classes and
inheritance and templates etc. I assume there won't be any problems there
(it should all be standard stuff)