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

Daniel Convissor wrote:

Playing with these useless "rules" is unfortunately not my cup of tea and I don't have the time for that.

You chose to release the package through PEAR. PEAR is a community project with community standards. If you're not interested in feedback and adhering to standards, it seems releasing it through SourceForge is the way to go.

Lets not blow things out of proportion here. These are of course by no means show stoppers and certainly nothing important enugh to send Bertrand to sourceforge if he doesnt change them. Actually I think the main point, atleast that I was trying to make, is to try and incorporate these guidelines into everybodies development style so that they really become effortless (as much as possible atleast). Also I wanted to note that the 80 chars thing is not so much related to possible editor limitations, but more regarding the amount of characters people can easily parse as they move through your code line by line. Here I have found 80 chars max to be a good goal to reach and usually quite attainable. It certainly has helped me understand my code better. Although I do admit at having a few lines that go to 90 or 100 in my code as well. Anyways everybody take a hit from the peace pipe .. its all cool and all :-) regards, Lukas