|
Re: changes to command line parsing: msg#00018lang.nasm.devel
Ed Beroset wrote: In cleaning up the preproc.c interfaces, I notice that several functions are exported solely for the use of nasm.c when it processes command line options. It occurred to me that it might provide a better and more concise interface if the interface were made a little more generic, since my primary interest in cleaing up the interface is to allow for alternate preprocessors to be built. I thought of several options on which I would like your opinions: I am for option B with a modification: NASM itself is treated just like the preprocessor (i. e. it gets the command line and returns everything it doesn't understand) and is called before the preprocessor. That way NASM options would be picked out first, and the preprocessor(s) can get what is left. - VP ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | changes to command line parsing: 00018, Ed Beroset |
|---|---|
| Next by Date: | Re: changes to command line parsing: 00018, anonymous coward |
| Previous by Thread: | changes to command line parsingi: 00018, Ed Beroset |
| Next by Thread: | Re: changes to command line parsing: 00018, anonymous coward |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |