On Tue, 26 Mar 2002, Philippe Canal wrote: > Hi Gerco, > > When the macro has the extension '.c' (lower c), it is considered > a C macro (as opposed to C++). > > Please only use extension like .C, .cpp, .cxx. > > Cheers, > Philippe. Hi Philippe, Since when is this? I never before had problems with the `.c' extension. I have several hundreds of macros lying around to testify that, which, admittedly, were mostly used with the ancient version 2.25. Apart from that, why does CINT, being a pure C++ interpreter, need to distinguish a C++ macro from a C one? Isn't C considered a subset of C++? I thought so, but perhaps that isn't (entirely) true if you're a computer scientist rather than a physicist? I can understand that for puristic reasons there is a distinction, but other than that I don't see the logic. BTW, giving my macro the extension `.f' or `.p' or no extension at all works just fine. As long as it isn't `.c'. In any case, this requirement (which was obviously introduced in a version after 2.25) isn't particularly well documented (just try a search for `extension' or `macro extension' on the root web site). To light another little fire, I always thought that identification by extension was a Windows thing, which we were very happy to get rid of using Linux ;) Thanks for your reply, -- Gerco Dr. C.J.G. Onderwater, VRAP Nuclear Physics Laboratory 476 Loomis Laboratory of Physics University of Illinois at Urbana-Champaign 1110 West Green Street Urbana, IL 61801-3080 Phone : (217) 244-7363 Fax : (217) 333-1215 E-mail: onderwat@uiuc.edu
This archive was generated by hypermail 2b29 : Sat Jan 04 2003 - 23:50:47 MET