I'd prefer it if these were always done as separate steps so it can be more easily integrated into other build scripts. (Build systems and scripts suck btw, but they suck less than the confusion caused when files can be read and written arbitrarily by the compiler, which already has hidden dependencies).
Re: DIP81: Writing files at compile time
Adam D. Ruppe via Digitalmars-d Wed, 12 Aug 2015 12:01:06 -0700
I've been looking at a company's build system recently and it
makes me think this is a bad idea: we have enough problems
tracking import dependencies and changes as it is without other
files being written in the middle of the process too.
- DIP81: Writing files at compile time JDemler via Digitalmars-d
- Re: DIP81: Writing files at compile t... via Digitalmars-d
- Re: DIP81: Writing files at compile t... Adam D. Ruppe via Digitalmars-d
- Re: DIP81: Writing files at compi... via Digitalmars-d
- Re: DIP81: Writing files at c... JDemler via Digitalmars-d
- Re: DIP81: Writing files ... via Digitalmars-d
- Re: DIP81: Writing f... via Digitalmars-d
- Re: DIP81: Writing f... JDemler via Digitalmars-d
- Re: DIP81: Writi... via Digitalmars-d
- Re: DIP81: W... JDemler via Digitalmars-d
- Re: DIP81: W... via Digitalmars-d
- Re: DIP81: W... JDemler via Digitalmars-d
- Re: DIP81: Writing files at compi... lobo via Digitalmars-d
