Size_t existence
–>
There's no need to quote… what do you think this is, Internet? 🙂
<–
No, but I know *I* appreciate quotes, since I can't always get full context of
a message just from the title (I may be using Navigator, requiring another
inconvenient message fetching pass to get the parent message, or the parent
message may have scrolled off the forum, or the message I'm reading may have
scrolled to Email). Thus, I do the same for others, if I want to make sure
folks know what I'm talking about and can't find any way to directly refer to
the topic at hand (like here 🙂 ).
File parsing wouldn't be a concern if you #ifndef…#endif around the whole
thing, since the preprocessor (or the lexical scanner in some cases) would turn
everything in the middle into whitespace; it would never even get to the
parser. You'd still have to do file I/O (though not necessarily disk I/O, if
you've got a tuned disk cache) to read the whole file, though.
–>
Including the header more than once leads to a warning from most compilers, I
want to avoid that, too.
<–
That's not true. Including a header may lead to warnings, but that's only due
to multiple redefinitions of variables or symbols. From what Phil said in
another message, redefining a preprocessor symbol to the same text won't
generate a warning under pure ANSI C (I'll admit, though, I haven't tried this
yet). Even without that, though, here's an #include file that can be included
multiple times (and isn't empty 🙂 ):
// file MultiInclude.h
#undef MySym
#define MySym "This is MY symbol, you can't have it!"
// EOF
Joe