On Wed, Nov 02, 2022 at 09:16:22PM +0100, Christian Köstlin via Digitalmars-d-learn wrote: > On 02.11.22 20:16, H. S. Teoh wrote: [...] > > IMO, the ideal situation is a hybrid situation: the underlying build > > mechanism should be purely declarative, because otherwise the > > complexity just goes out of control and you end up with > > non-portability, non-reproducible builds, intractibility of static > > analysis (e.g., for an external tool to understand what the build > > does). However, quite often in a large project you need to perform > > some complex tasks, and doing this declaratively can be too > > cumbersome. So what you want is a procedural element to the build > > description that *generates* the underlying declarative elements of > > the build. The procedural part does not perform any build actions; > > its job is to generate the declarative build description. The > > actual build is carried out based on this declarative build > > description. [...] > Thats an interesting approach. Reggae goes a little bit in that > direction, right? [...]
I haven't actually used reggae myself, but a cursory look suggests that this is probably the case. T -- A mathematician is a device for turning coffee into theorems. -- P. Erdos