> I really do have to take issue with this; I would argue that the > current behaviour of after_initialize is based on a 'thin and literal > interpretation of the word "initialize"'. Decanting an object from > storage is not initialization; initialization is what happens when an > object is first created, back before it got poured into the storage > jar.
I can buy your argument, but if I do so, there doesn't seem to be a need for after_initialize: def initialize(attrs) do_stuff super end All we'd be doing is reinventing an initialize method which hid the arguments. Doesn't seem particularly necessary, especially at the cost of backwards compatibility for the people who use after_initialize at present. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
