From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: trouble with MSDOS Macro
Date:	6 Feb 2001 16:18:54 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	19
Message-ID:	<95p85e$46a$1@nets3.rz.RWTH-Aachen.DE>
References:	<3A80185B DOT 27921 DOT F696E AT localhost> <3A801968 DOT 39E6D7B2 AT gmx DOT de>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 981476334 4298 137.226.32.75 (6 Feb 2001 16:18:54 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	6 Feb 2001 16:18:54 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Silver <SilverBanana AT gmx DOT de> wrote:
[...]
> Thanks, but I'm writing a C++ library and I've set up several naming
> conventions for this, so I would REALLY appreciate it to call it
> "MSDOS". Besides I'm pretty sure that it is not a good style for DJGPP
> to use nonstandart macros for its own purposes without underscores and
> without documentation. What I need is a way to get DJGPP compatible.

MSDOS is by no means a nonstandard macro, for a DOS compiler. Just
about all of them predefine this macro, AFAIK.  Of course, there are
ways to disable it. In 'gcc -ansi' mode, you'll be rid of it, and only
the ANSI-blessed 'implementor namespace' version __MSDOS__ is still
there.

So I agree with Andris: you really should choose a different namespace
name, here.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -