On Wed, Sep 23, 2009 at 02:00:15PM -0000, Parrot wrote: > #389: subs with :method should not be entered as symbols in the namespace > I would also argue that the proper way to do introduce this that allows > people to adopt it painlessly would be: > * provide a way to override the default with the desired new behavior. > (e.g. :no_nsentry) > * provide a way to explicitly declare you want the default behavior (e.g. > :nsentry) > * With the next release, declare that the old default will change after > the release after that. > > This allows users to update their code in advance and have it keep working > when the default changes; it also allows users to adopt the new behavior > asap.
Note that the existing (incorrect) default has already been listed as deprecated in DEPRECATED.pod, so _technically_ we can make the change anytime we wish. That said, I'm fine with the interim approach given above -- if a :no_nsentry flag is added, then PCT can immediately start defaulting generation of methods to automatically include that flag (unless 'nsentry' is provided in the PAST structure). Thanks! Pm _______________________________________________ parrot-tickets mailing list [email protected] http://lists.parrot.org/mailman/listinfo/parrot-tickets
