Re: [Algorithms] Complexity of new hardware

[Alen L. <ale...@cr...>]

I am talking about dependencies between magic files causing the
generated files to be rebuilt too often.

Any change to *.myformat can cause change to *.cpp and/or *.h. Most
often you do implementation changes which impact only .cpp, and it is
possible to detect that you have nothing new to change in .h. But, can
be hard to explain this kind of "conditional" dependency to a build
system. If you leave .h as always changed, you get a lot of unneeded
recompiling.

So, parsing the header, where the header contains extra meta info you
need and generating your metadata from that, while letting the
compiler use that same header directly works better, IME.

Alen



Friday, April 17, 2009, 10:42:05 PM, you wrote:

> Do tell! Are you talking about cross dependencies between magic file<->C++?

> MSN
> -----Original Message-----
> From: Alen Ladavac [mailto:ale...@cr...]
> Sent: Friday, April 17, 2009 1:37 PM
> To: Mat Noguchi
> Cc: Game Development Algorithms; Jarkko Lempiainen
> Subject: Re[2]: [Algorithms] Complexity of new hardware

> Friday, April 17, 2009, 9:59:01 PM, Mat wrote:
>> You could always flip that around and have a to-C++ compiler.

> And get tangled in a dependency quagmire. Used that a long time ago
> and I like this direction much better.  

> Alen




-- 
Best regards,
 Alen                            mailto:ale...@cr...