Message-Id: <200101211745.MAA24614@qnx.com> Subject: Re: Another item for develop.txi To: djgpp-workers AT delorie DOT com Date: Sun, 21 Jan 2001 12:45:21 -0500 (EST) From: "Alain Magloire" In-Reply-To: <200101211631.RAA10217@father.ludd.luth.se> from "Martin Str|mberg" at Jan 21, 2001 05:31:24 PM X-Mailer: ELM [version 2.5 PL0b1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > > According to Eli Zaretskii: > > > Date: Sun, 21 Jan 2001 08:54:15 -0500 (EST) > > > From: "Alain Magloire" > > > Variables, macros, etc .. that are start with a leading '_' are reserved > > > by the C/C++ implementation > > > > That's true if the identifier begins with an underscore and an > > upper-case letter, or with two underscores. One underscore and a > > lower-case letter should be okay. hmm .. I do not have the Std so can not confirm. > Isn't the C library part of the C implementation? 8-) Yes, I believe so. GNU Lib C can get away with it since they follow GNU C and make sure of not having clashes. The problem is a bit more difficult for other free standing C Lib. I'm not saying not to use it, because that is the way the lib can protect itself from things like // User fonction #define my_dj_string int #include and in stdio.h // Library prototypes char *fgets(char *s, int my_dj_string, FILE *stream); I suppose, I was pointing out little gotchas, for example _Bool I believe is a reserved word in the C99 drafts, so doing this char *fgets (char *_s, int _Bool, FILE *_stream); Can get you in trouble on certain compilers, like lcc. IIRC, djgpp will compile with no other compiler then gcc, so tracking gcc and keeping out of trouble should be enough. > Right, > > MartinS > -- au revoir, alain ---- Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!!