Let's clarify something, when I am talking about "quality of code", I am not thinking about indentation. Any IDE can fix the indentation of your files in a second.
I am talking about : - naming conventions (camelCase vs underscores in yml) - decoupling of concerns - Test Driven Development - Documentation - Code reusability - Design patterns IF NEEDED etc. Complaining about indentation and brackets is pointless. You like using one bracket per line, good for you. It takes a second to format all my files using the indentation I like. On Dec 10, 2007 11:59 AM, Charley Tiggs <[EMAIL PROTECTED]> wrote: > > > On Dec 10, 2007, at 10:54 AM, Ian P. Christian wrote: > > > > > mozey wrote: > >> give it the "Symfony stamp of approval" > > > > > > Good idea in principle - doubt many people will have time to do > > this though. > > > > Perhaps the rating system needs to have different ratings, for > > example... > > > > ease of use: > > features: > > quality of code: > > extensibility: > > I support this approach, with the exception of "quality of code". > It's too subjective unless we have some explicit guidelines that > define what "high quality" means. Just because I choose to use > double spacing, it doesn't follow that the quality of my code is > bad. That's a personal preference of the developer, not a sign that > the code is bad. > > Charley > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
