Re: configuration-scanner.lex "extension" weirdness

> configuration-scanner.lex doesn't recognize the "extension" token if > it is followed by a space. It ends up being scanned as the STRING > "extension " because that is a longer match than just "extension". > > So the question here would be, is STRING defined incorrectly, or is > EXTENSION defined incorrectly? At the very least, EXTENSION could > be defined as "extension"[ \t]* to soak up the extra whitespace. I think STRING should swallow the whitespace before the '=', but I'll let Zeev or Andi make this change. -Rasmus -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net