Subject: Re: future NetBSD cpp predefines...
To: Ted Lemon <email@example.com>
From: proprietor - Foo Bar And Grill <firstname.lastname@example.org>
Date: 12/21/1994 15:16:07
#define AUTHOR "email@example.com (Ted Lemon)"
* It might be worthwhile also to #define __NetBSD__ to some value - say,
* the major version times 100 plus the minor version. E.g., 100 for
* version 1.0, 101 for version 1.1, 112 for version 1.12, et cetera...
Shall we get really absurd (or useful, depending on point of view) and
have __NetBSD_MAJ__, __NetBSD_MIN__, and __NetBSD_REV__ defined?
Stuff like OS versioning is probably better defined in Makefiles than
in the compiler.
* I'm not sure what the planned numbering scheme is - for example, what
* would 1.0a translate to. However, something that allowed us to
* figure out what version of NetBSD we're compiling for would probably
* be useful in enough cases to justify doing it.
* Gcc currently does something similar with __GNUC__ - its value is
* currently 2. __GNUC_MINOR__ is 6. There's no predefine to
* differentiate between 2.6.0 and 2.6.2, though, which I think is a bug.
Compiler versioning, however, is better defined in the compiler
#undef AUTHOR /* "firstname.lastname@example.org (Ted Lemon)" */
______________ ___ ________ _____WHO: Greywolf (unto death)
/ ___\ _ \ __\ V / \ / /__ \| | __/WHAT: UNIX System Mangler...er, Admin
\ \| | < _| ` ' \ '` / \/ /|_| _/ WHERE: Ithaca SW, 1301 Marina Village Pkwy
\___|_|\_\__\|_| \/\/ \__/___/_| Alameda, CA 94501 (415) 332-2344 x7255