Fabian, I think this can be handled with a regex (too match invalid php class names) and a list of reserved words. I think this only needs to be handled in the generate:* tasks.
Can we come up with a list of reserved words (outside of php in general) and maybe a patch for the documentation? - Dustin On 2/13/08 11:06 AM, "Fabian Lange" <[EMAIL PROTECTED]> wrote: > Hi, > There is a new ticket. > It is allowed to do: > symfony init-module frontend sf > > which will autogenerate > class sfActions extends sfActions > > which does not compile. > I noticed that the pake task does not do any validation on the argument. > > So possible errors are : > - conflicts with ³special² names like the ³sf² example above > - conflicts with restrictions on php names e.g. ³2do² > - duplicates on case sensitive file systems: ³main² and ³MAIN² action > > I wonder how to resolve these. I also could not find good documentation which > describes restrictions on ³whatever² > > Ay good proposals? > .: Fabian > > PS ah forgot the ticket is, if that is of interest: > http://trac.symfony-project.com/ticket/2927 > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
