According to Lachlan Andrew: > Greetings, > > New line handling in the config files needs surgery. See also bug > #823455 at > <https://sourceforge.net/tracker/?func=detail&aid=823455&group_id=4593&atid=104593>
Yeah, if a line without a \n is going to cause the whole config parser to core dump, we really do need to address this problem. If there are no currently active developers who are comfortable enough in lex/flex to address this issue, then we may want to reconsider the need for using this tool in the first place. What we have now seems to be pretty unmaintainable. Am I missing something here, or is lex really overkill for this parser? I don't think the lexical analysis portion of the config parsing is particularly complex, and could probably be done quite easily, and with more control, in C/C++ code. If we still need yacc/bison for the higher-level parsing, that's another matter, but at least we seem to need more control over what gets fed into that parsing engine. > On Wed, 19 Nov 2003 04:50, Gilles Detillieux wrote: > > I don't see anything in HtConfiguration.cc, conf_lexer.lxx, or > > conf_parser.yxx that would allow us to intercept the unterminated > > last line and add the newline to it, so it would be taken by the > > lexer to be a full line. That means the only way to deal with > > this, short of telling users "tough luck, just properly terminate > > your files," would be to rewrite the grammar in conf_lexer.lxx to > > be less dependent on newlines. Maybe define an EOL character class > > that can be \n or EOF, and use that instead of \n everywhere? But > > would this break the current EOF handling, or something else? I > > don't understand lex/flex enough to venture into this. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
