On 8 Nov 2008, at 10:07, Aliaksey Kandratsenka wrote: > If I understand correctly this means that old versions of code will > remain. I think that better approach is to provide better explanations > of what's going on, so that people don't try to preserve instances or > classes between requests.
I agree that reload having no effect on cached instances could be a little confusing. On the other hand, perfectly good production code being banned from develepment mode seems overkill, and also confusing. > We can do so by defining #method_missing on > zombie classes. What do you think ? The issues are not always to do with missing methods, class inheritable attributes are just as bad, so existing methods that reference class inheritable attributes would still explode without reason. Any ideas on how to do this nicely? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
