On 26.11.2010, at 15:54, Lukas Kahwe Smith wrote: > > On 23.11.2010, at 09:58, Fabien Potencier wrote: > >> I'm working on unifiying the method names throughout the framework. We >> already have some implicit naming conventions, and I want to write them down >> and validate them once and for all. >> >> These conventions are for internal use only (you can use them if you want in >> your own code, but that's not the main goal). >> >> Here is the naming convention RFC: >> >> When an object has a "main" many relation with related "things" (objects, >> parameters, ...), the method names are normalized: >> >> * get() >> * set() >> * all() >> * replace() >> * remove() >> * clear() >> * isEmpty() >> * add() >> * register() >> * count() >> * keys() > > > has() seems to be missing from this list?
init() and reset() to initialize as well as return the object state to the original status might also be useful to define. regards, Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
