 
            
            
            
            
                10 Apr
                
                    2009
                
            
            
                10 Apr
                
                '09
                
            
            
            
        
    
                5:33 p.m.
            
        IMO, there is absolutely no reason to /rely/ on non-standard features even if /all/ compilers supported it in this case.
Cleaner code? Avoiding nasty copy/paste problems with include guard names? The fact that you can still automatically easily generate standards-compliant code for release tarballs? Anyway, I understand that a library like Boost doesn't want to rely on this, but personally, but it sounds sane to me that other projects (that are less depended on and don't need to support a gazillion of compilers) use it. cheers, Remko