Re: cvs: pear /Event_Dispatcher Dispatcher.php Notification.php package.xml /Event_Dispatcher/examples bubbling.php cancel.php notification-class.php
object.php /Event_Dispatcher/tests Console_TestListener.php Dispatcher_testcase.php test.php

From: Date: Sat, 05 Feb 2005 15:28:45 +0000
Subject: Re: cvs: pear /Event_Dispatcher Dispatcher.php Notification.php package.xml /Event_Dispatcher/examples bubbling.php cancel.php notification-class.php
object.php /Event_Dispatcher/tests Console_TestListener.php Dispatcher_testcase.php test.php
References: 1 2  Groups: php.pear.cvs 
Request: Send a blank email to pear-cvs+get-29154@lists.php.net to get a copy of this message
Hi Bertrand: On Sat, Feb 05, 2005 at 04:15:12PM +0100, Bertrand Mansion wrote: > > The RFC has not been accepted yet AFAIK, this will be changed when the RFC is > accepted. Dude, it's at 11 votes. > AFAIK Phpdocumentor is smart enough to find the parameters name by itself. This > is a nice feature, as parameters names might change, without the user being > concerned. ... > AFAIK, this doesn't affect how Phpdocumentor works. So I'd leave that up to the > developer. The idea is that the API documentation be generated right. ... > I hate to waste space. ... > My text editor is not limited to 80 chars. As long as my code is readable and > respect Coding standards, it should be ok. It is easy today to get a text editor > with this "feature". It's not about how you or phpDocumentor interracts with the file. It's not about me being majorly pedantic -- though I AM. It's about readability by large numbers of people. That's the point of coding standards. Making it easy for people to find and comprehend things quickly because they're in the expected locations and in the expected format. Thanks, --Dan -- T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y data intensive web and database programming http://www.AnalysisAndSolutions.com/ 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409

« previous php.pear.cvs (#29154) next »