The great thing about standards is that there are so many to choose  
from.

I can't think of a single programming language that has a consistent  
standard. In python you see 2 spaces and 4 spaces and tabs; camelCase,  
lower_lower, and ProperCase.  Ruby is pretty consistent because it  
enforces ProperCase for classes/modules and UPPER_CASE for "constants"  
and lower_case for methods (which makes using rjb a blast) but you  
still see variations.  C -  K&R or BSD or GNU or Linux or ...?  C++ -  
ha!

Pick a style that works for you and run with it.  When using others'  
code, use their style.


On Sep 11, 2009, at 10:37 AM, Danny wrote:

>
> When I say Zend I reffer to the Zend Company (PHP Company, 
> http://www.zend.com 
> ),
> not the framework.
> I think that all the PHP developers should just follow one coding
> standard
>
> Zend more than a framework.
>
> (I have never use the Zend Framework, so this don't have anything to
> do with my preferences, I really prefer the Symfony coding standar but
> there is not any PHP universal standard that is a -1 for PHP)
>
> On Sep 11, 12:49 am, Sid Bachtiar <[email protected]> wrote:
>>> Why Symfony don't follow the Zend PHP coding Standard and use it own
>>> standar?
>>
>> Because Symfony is not Zend?
>>
>> On Fri, Sep 11, 2009 at 4:21 PM, Danny <[email protected]> wrote:
>>
>>> Why Symfony don't follow the Zend PHP coding Standard and use it own
>>> standar?
>>> http://framework.zend.com/manual/en/coding-standard.html
>>
>>> I think all the php coders should follow just one standard.
>>
>>> Sorry for my english.
>>
>> --
>> Blue Horn Ltd - System Developmenthttp://bluehorn.co.nz
> >

--
Jacob Coby







--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to