Comments on: Mental note about #ifndef’s

By: Luanatic con features » disléxicos del mundo unisors!!!

Luanatic con features » disléxicos del mundo unisors!!! — Sun, 13 Apr 2008 17:49:12 +0000

[...] del primer mandamiento, viene el de “evitarás la [...]

By: Jcl

Jcl — Thu, 10 Apr 2008 10:35:13 +0000

My first comment seemed to get lost somehow (I asked for a test case too, like slack)… I’ve been doing exactly that (comments before include guards) many times and have never had a problem with that, either with gcc, borland c, or visual c (all under Windows/DOS).

Can’t figure what the problem with comments before include guards could be. Even if the compiler did not ignore the comments (which it does), I can’t see how that could change even a bit of it. #including a file is just embedding that file on the stream that goes to the code compiler… I can’t see how having comments -anywhere- could make it fail, unless it’s certainly a bug in the compiler.

By: sole

sole — Wed, 09 Apr 2008 07:35:07 +0000

:-P

I had the ‘;’ after the class, that was an example only. I’ll fix that!

I’ll check again just in case it’s an Apple+GCC bug O_O

Or maybe an Apple+GCC+Sole bug :D

By: slack

slack — Wed, 09 Apr 2008 00:07:35 +0000

It seems to work here:
#include guard after comment
.

The only reason the code above does not work should be the missing ‘;’ after the class definition, but you wouldn’t have lost hours in THAT (yes, I know I’m being pedantic here, but that’s required when talking about compiler quirks ;), so there must be another cause. This is an interesting bug :)

By: sole

sole — Tue, 08 Apr 2008 20:29:59 +0000

Yes:

/************************************

 A certain class



@author blabla



(C) My company



************************************/



#ifndef CERTAINCLASS_H

#define CERTAINCLASS_H



class CertainClass { ... };



#endif

That does not work.