Warp wrote:
> Darren New <dne### [at] sanrrcom> wrote:
>> Patrick Elliott wrote:
>>> Trying to work out what went wrong, and why, from the damn code, and the 
>>> code that built the code, and the code that ran the code, that built the 
>>> code... o.O
> 
>> Precisely. When the configuration file to create the build tools is based on 
>> turing-complete macro processing, you're gonna just be screwed if there's 
>> anything wrong.
> 
> Yet this is still somehow a problem with makefiles.

Where did I say makefiles in there?

I'm railing against arbitrarily complex build systems where you can't look 
at the configuration file and figure out what it's going to compile. It's 
the same thing I have against C include files: if they were limited to 
declarations, it would be far, far less of a problem.

-- 
Darren New, San Diego CA, USA (PST)
  "How did he die?"   "He got shot in the hand."
     "That was fatal?"
          "He was holding a live grenade at the time."

Post a reply to this message