Just like DDOC adds auxiliary information to create documentation, build comments would add auxiliary information to create build scripts (which a tool could just use right away without generating garbage in the form of build script files).
On Tue, Nov 27, 2012 at 11:44 AM, Gor Gyolchanyan < [email protected]> wrote: > The convenience of RDMD comes from the fact, that it looks into the source > files to determine what to do. I think it would be even more convenient to > make a build tool for D, which would read special comments (much like DDOC, > but dedicated to build process) for compiler flags and other build > variables. > > > On Tue, Nov 27, 2012 at 11:38 AM, Jacob Carlborg <[email protected]> wrote: > >> On 2012-11-27 08:13, Gor Gyolchanyan wrote: >> >>> I'd recommend RDMD. It can compile (and run) the given module and it's >>> entire import tree. No build scripts are necessary. >>> Very convenient with pragma(lib, "...") >>> >> >> RDMD is quite good for compiling executables. It won't work for compiling >> libraries. Quite often a build script is needed to avoid repeating the same >> compiler/linker flags over and over again. >> >> -- >> /Jacob Carlborg >> > > > > -- > Bye, > Gor Gyolchanyan. > -- Bye, Gor Gyolchanyan.
