RE: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_compile.c zend_compile.h zend_globals.h zend_highlight.c zend_language_parser.y
zend_language_scanner.l

From: Date: Wed, 19 Mar 2003 23:00:24 +0000
Subject: RE: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_compile.c zend_compile.h zend_globals.h zend_highlight.c zend_language_parser.y
zend_language_scanner.l
References: 1  Groups: php.zend-engine.cvs 
Request: Send a blank email to php-zend-engine-cvs+get-1057@lists.php.net to get a copy of this message
Marcus, I don't know, I know people use this comment form a lot: /** * This is a comment. */ But if the majority says it's fine, let's go ahead.. -Andrei > -----Original Message----- > From: Marcus Borger [mailto:marcus.boerger@t-online.de] > Sent: Wednesday, March 19, 2003 4:47 PM > To: Andrei Zmievski > Cc: zend-engine-cvs@lists.php.net; Andi Gutmans > Subject: Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_compile.c > zend_compile.h zend_globals.h zend_highlight.c zend_language_parser.y > zend_language_scanner.l > > However i dislike the format: a trailing space after "/**" will bring us > some bug > reports because simply noone will understand the necessaty of > that space and > if you're editing code and do not start your coment after the /** your > editor simply > may remove that space and bang. > > The only reason to have this is to differentiate between normal > comments and > doc-comments but a normal comment is either '/' '*' '*' > '*'+ .* '*' '/' > (three '*' after > '/') or only one '*' after the '/'. In other words when making > use of > doc-comments > you know that you must not use '/**' elsewhere.

« previous php.zend-engine.cvs (#1057) next »