Compiler Predefined Symbols

Tech-Archive recommends: Fix windows errors by optimizing your registry

Does anyone know how to get a list of the symbols pre-defined by the
compiler?

How can one determine what the value of MSC_VER is?

I have inherited some code that checks for "MSC_VER >= 1400", but that is
not sufficient to prevent linker errors when using the DDK 3790+ compiler.

I need to figure out how to support the compilers for VS 2005, the DDK's
CL.EXE, and VisualStudio 6.

The "/u" option will "remove all predefined macros" -- is there an option to
"list all predefined macros"?

Thanks.


.

Relevant Pages

  • Re: Reflections on a classic Lisp Paper
    ... lisp dialects. ... user-defined special forms - Macros, Fexprs, and Nlambda. ... compilable because the compiler just couldn't do it. ...
    (comp.lang.lisp)
  • Re: Cpp Considered Harmful
    ... > However, in either case, assertions are invaluable in making certain ... because we now have our own cpp ... > macros, we can use several different compilers and have our system ... > built into the compiler. ...
    (comp.lang.cpp)
  • Re: Doing mini-languages in CL
    ... > Thats it in a nutshell. ... I think the detail to note is that the Macro facility is a Compiler ... simply put you may well be able to leverage CL macros in building your ...
    (comp.lang.lisp)
  • Re: Why doesnt Lisp automatically differentiate functions and macros?
    ... what stops a Lisp machine from figuring automatically which ... small subset of things macros can do that you are thinking is all they can ... This requires the compiler to know how to do things. ... things that the compiler writer didn't think to, ...
    (comp.lang.lisp)
  • Re: Doing mini-languages in CL
    ... "Will Hartung" writes: ... >> address fixup grunt work to it. ... > Your compiler will already take S-exprs, but there's nothing that says those ... and you find you won't necessarily need macros. ...
    (comp.lang.lisp)