Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_language_scanner.l
| From: | Marcus Boerger | Date: | Thu, 10 Jun 2004 13:12:07 +0000 |
| Subject: | Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_language_scanner.l | ||
| References: | 1 2 | Groups: | php.zend-engine.cvs |
| Request: | Send a blank email to php-zend-engine-cvs+get-2691@lists.php.net to get a copy of this message | ||
Hello Derick,
maybe we need some kind of workaround for
'/************************/' lines but generally there are
tons of code out there where the doc comment starts right
after '/**'. A solution would be to start doc comments
after '/**<ANY-WHITE-SPACE>' or to ignore doc comments if the
consist of only '*' (very slow) or to simply ignore all doc
comments that start with '/***'. Ideas?
marcus
Thursday, June 10, 2004, 3:03:46 PM, you wrote:
> On Thu, 10 Jun 2004, Marcus Boerger wrote:
>> helly Thu Jun 10 07:40:34 2004 EDT
>>
>> Modified files:
>> /ZendEngine2 zend_language_scanner.l
>> Log:
>> Do not require NEWLINE at start of doccomment
> This is actually required, now /***** will also start a doc comment,
> which it shouldn't do.
> regards,
> Derick
--
Best regards,
Marcus mailto:helly@php.net