Re: Language module support modified
Bram Moolenaar <[email protected]>
| Newsgroups | gmane.comp.tools.aap.devel |
|---|---|
| Message-ID | <[email protected]> |
Lars Ivar Igesund wrote: > I understand you, but I don't think I explained myself good enough. > Debug constructs are a part of the language in the same way as version > constructs are. Thus a $DDEBUG variable should be present IMHO. OK, then we should add $DDEBUG and explain what values Aap understands. Then it will work for kinds of D compilers. That is, the tool will convert $DDEBUG to what the compiler understands. > > The same applies to optimizing flags. > > > > > OPTIMIZE might make sense as it is now. The current version of the > > > compiler takes only one optimize flag, -O, but it would probably > > > be ignorant not to expect more. > > > > > > > - Each tool and/or module uses the standard $DEBUG and $OPTIMIZE > > > > variables. These need to be converted to arguments that the > > > > specific compiler accepts. > > > > You could probably use something like: > > > > @if _no.OPTIMIZE and int(_no.OPTIMIZE) > 0: > > oarg = -O > > @else: > > oarg = > > > > :sys $DMD ... $oarg ... > > Just what I was thinking. I guess this must be present in the dmd.py too. Yep. I have collected the remarks and modified the tool and module. Please check version 1.037! -- If bankers can count, how come they have eight windows and only four tellers? /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html /// ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf