This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] specs changes for libstdc++ debug mode


Martin Sebor <sebor@roguewave.com> writes:

| Matt Austern wrote:
| 
| > On Monday, July 14, 2003, at 05:02  PM, Doug Gregor wrote:
| >
| ...
| > Stupid question: is there any other place in the compiler where we change
| > the behavior of the driver based on whether the user defines a special
| > macro?
| > If so, if we're just carrying on with something we've done already,
| > then
| > I don't have a problem with this.  If not, then I'm a bit uncomfortable
| > with it.  -D is documented to define a macro.  Having it do other things
| > as well, for special macros, strikes me as non-obvious.
| 
| FWIW, the MSVC #pragma comment feature allows program source
| to embed commands for the linker in the object file, so there
| is existing practice for this non-obvious feature. E.g.,
| 
|      #ifdef FOO
|      #  pragma comment (lib,libfoo)
|      #else
|      #  pragma comment (lib,libbar)
|      #endif

I'm not really found of the idea of having pragmas (or any CPP hack)
silently change portions of program semantics.  I believe in compiler
switch controlling whole translation units (or better the whole
program) for that purpose. 

-- Gaby


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]