Author: Miguel A. Ballicora
Date: 08:14:52 01/21/02
Go up one level in this thread
On January 21, 2002 at 09:10:49, Marcel Veldhuizen wrote: >On January 21, 2002 at 09:04:05, Miguel A. Ballicora wrote: > >>1) It is for the same reason that a macro has to be in an .h file. >>The compiler has to include as inline what it "sees", rather than what is has >>been compiled somewhere else in another object file. > >Macros don't have to be in a .h file, what gave you that idea? They do have to be in a .h file (or whatever file that you #include that generally are .h) if you want that macro to be used in different objects. That is the analogy I am doing. Regards, Miguel >Your explanation makes sense though, otherwise the compiler would need to >reopen, parse, etc the appropriate .c(pp) file, which it can't do, because it >doesn't even know which file the code is in.. > > >Marcel Veldhuizen
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.