Re: [Flex-devel] Issues with option processing
flex is a tool for generating scanners
Brought to you by:
wlestes
From: Aaron S. <aa...@se...> - 2008-10-16 17:58:14
|
We'll have to see if any of those options are relied upon by Makefiles, but otherwise I like your idea. I don't recall if --nofoo is something that's part of lex-ancient or flex-2.5.4 or not. Aaron On Oct 16, 2008, at 8:03 AM, Joe Krahn wrote: > I noticed that the option processor allows a 'no' prefix even where it > doesn't make sense. In most cases, it probably is not that important, > but someone may get confused if they try to use an option like > "noextra-type". > > Also, there are a few more functions that could be disabled by a > no<func_name> option. Instead making command-line options even more > numerous, maybe it would be a good idea to add a flag --options=LIST, > where LIST is a string containing options processed exactly as in the > %option directive. > > Joe Krahn > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Flex-devel mailing list > Fle...@li... > https://lists.sourceforge.net/lists/listinfo/flex-devel |