It means "at any point in the future, an ANSI-compliant compiler can give an error when compiling such code". Just because it works now, doesn''t mean you should rely on it. Maybe some future compiler will optimise their symbol table in such a way that the leading underscore truly becomes reserved, and then your code will need fixing.
[ MSVC Fixes | STL | SDL | Game AI | Sockets | C++ Faq Lite | Boost ]
What is the best way to have your project set up for a large project (and a few Qs)
>> Drop the leading underscore - it's illegal.
It is? I compile code every day with this in it...
#ifndef __YERMOMMA_H__
#define __YERMOMMA_H__
and it works just fine.
Standards are for sissies.
[edited by - Buster on March 20, 2002 3:18:45 PM]
It is? I compile code every day with this in it...
#ifndef __YERMOMMA_H__
#define __YERMOMMA_H__
and it works just fine.
Standards are for sissies.
[edited by - Buster on March 20, 2002 3:18:45 PM]
how old are you?
(sorry but that was the first thing came into my mind when I read the last sentence of your post)
(sorry but that was the first thing came into my mind when I read the last sentence of your post)
Hmm, so it seems prefixes are reversed for std and compiler implementation. Just like member variables, we should stick with postfixes instead.
quote:Original post by Buster
>> Drop the leading underscore - it''s illegal.
It is? I compile code every day with this in it...
#ifndef __YERMOMMA_H__
#define __YERMOMMA_H__
and it works just fine.
Standards are for sissies.
quote:
Original post by Kylotan
It means "at any point in the future, an ANSI-compliant compiler can give an error when compiling such code". Just because it works now, doesn''t mean you should rely on it. Maybe some future compiler will optimise their symbol table in such a way that the leading underscore truly becomes reserved, and then your code will need fixing.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement