Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_language_scanner.l
| From: | Andi Gutmans | Date: | Sat, 12 Jun 2004 16:19:32 +0000 |
| Subject: | Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_language_scanner.l | ||
| References: | 1 2 3 4 5 | Groups: | php.zend-engine.cvs |
| Request: | Send a blank email to php-zend-engine-cvs+get-2700@lists.php.net to get a copy of this message | ||
Well I guess we could leave it (with the WHITESPACE rule).
Any idea how it affects existing php doc tools?
At 11:29 AM 6/12/2004 +0200, Marcus Boerger wrote:
Hello Andi, Saturday, June 12, 2004, 12:59:11 AM, you wrote: Although it might not be critical, I still fail to understand why requiring a newline after /*** to mark the doc as a phpdoc comment as a limitation/bug? Why can't you put that @ on the next line? Andi Because no other system has this requirement and always doing things different that already exists and are known to many people is simply the wrong way and make peoples lie very hard. (Another reason is that you cannot see from the code if the comment becomes a doc comment or not because you cannot see if '/**' is followed by a new line or a space in which case it wouldn't with the old model). marcus