Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_language_scanner.l
| From: | Andi Gutmans | Date: | Thu, 10 Jun 2004 21:34:23 +0000 |
| Subject: | Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_language_scanner.l | ||
| References: | 1 | Groups: | php.zend-engine.cvs |
| Request: | Send a blank email to php-zend-engine-cvs+get-2695@lists.php.net to get a copy of this message | ||
Marcus,
Are you sure we need to make this change at this point in the release cycle? I'm not really against this patch, but I wouldn't consider the previous state a "bug". Actually strictness might have it's advantages as it forces a very strict layout which will be easier to interpret by doc tools.
Andi
At 01:38 PM 6/10/2004 +0000, Marcus Boerger wrote:
helly Thu Jun 10 09:38:31 2004 EDTModified files:/ZendEngine2 zend_language_scanner.lLog: - Require a single white-space char after /** to start a doc comment thatway we prevent /*** from becoming a doc comment (as requested Derick).http://cvs.php.net/diff.php/ZendEngine2/zend_language_scanner.l?r1=1.109&r2=1.110&ty=u Index: ZendEngine2/zend_language_scanner.l diff -u ZendEngine2/zend_language_scanner.l:1.109 ZendEngine2/zend_language_scanner.l:1.110 --- ZendEngine2/zend_language_scanner.l:1.109 Thu Jun 10 07:40:34 2004 +++ ZendEngine2/zend_language_scanner.l Thu Jun 10 09:38:31 2004 @@ -19,7 +19,7 @@+----------------------------------------------------------------------+*/ -/* $Id: zend_language_scanner.l,v 1.109 2004/06/10 11:40:34 helly Exp $ */ +/* $Id: zend_language_scanner.l,v 1.110 2004/06/10 13:38:31 helly Exp $ */ #define yyleng SCNG(yy_leng) #define yytext SCNG(yy_text) @@ -1445,7 +1445,7 @@}} -<ST_IN_SCRIPTING>"/**" { +<ST_IN_SCRIPTING>"/**"WHITESPACE {CG(comment_start_line) = CG(zend_lineno); BEGIN(ST_DOC_COMMENT); yymore();-- Zend Engine CVS Mailing List (http://cvs.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php