Re: Wierd Problem-missing .lib files even after successful dll creation
Mark Randall wrote:
"Ulrich Eckhardt" <eckhardt@satorlaser.com> wrote:
Identifiers beginning with an underscore and a capital are reserved, you
shouldn't use them.
Hmm is that so?
Yes, those and any identifier with two consecutive underscores (not just at
the beginning). Furthermore, why would you use them? In my eyes, they don't
add anything to readability of code and for include guards, which are less
for reading but rather for functioning, it is even less useful.
I have recently changed my coding style to use underscore caps as argument
names (like the 2005 STL), I find it a much cleaner way of coding.
The standardlibrary does that exactly because you are free to
#define M (8,13)
and the standardlibrary must still work correctly. On the other hand, the
standardlibrary might have a macro called _T, which shouldn't affect your
code though.
This rule is intended to split the macro-namespace in two sections, one for
the user and one for system implementers. IOW, your use of identifiers is
not allowed by the C++ standard.
I know I'm nitpicking a bit but in my eyes there is no reason to risk the
portability of your code by using such identifiers. If you're porting to a
new environment, you usually have enough other things to worry about than
finding out all the environment's macros and their use in your code.
Uli