[Flex-devel] Issues with option processing
flex is a tool for generating scanners
Brought to you by:
wlestes
From: Joe K. <kr...@ni...> - 2008-10-16 15:04:16
|
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 |