We have made larger course correcrions in the past and there is no reason make_immutable would stop working until we found a better solution. Which is to say this ship might have sailed but we are its skippers.
On Aug 20, 2009 4:43 AM, "Piers Cawley" <pdcaw...@gmail.com> wrote: On Thu, Aug 20, 2009 at 7:25 AM, Jesse Luehrs<d...@tozt.net> wrote: > On Thu, Aug 20, 2009 at 06:56:1... You don't, obviously. I'd argue that make_immutable is, in fact, poorly named - it seems overly imperative and bound up with assumptions about implementation. Surely it would be better to have something more generic, say: __PACKAGE__->meta->finalize_definition; # Terrible name which has the effect of making the class immutable where possible. And if, in the future, we find a better way of closing a class which doesn't involve immutability it can still be triggered off finalize_definition. However, given the mindshare that make_immutable has by now, that boat has probably sailed.
