Requesting more info from the bug-reporter, I noticed this:
> I just installed your utility belt on my laptop and it took
> a while to realize that it was causing a very strange behavior on some of my
> apps: The edit action on many controllers was not being executed.
****
Utility Belt adds a command-line method called "edit" to IRB. Adding
command-line methods in IRB really means adding methods to Object.
This supports my theory that Rails is loading Utility Belt by
requiring .irbrc (as does the anecdotal stuff about seeing "Constant
already initialized" errors for constants which were only used in
my .irbrc and nowhere else).
The weird part is that it suggests that the .irbrc must be mistakenly
loaded *after* the controller is defined (since if it happened before
the controller itself was loaded, the newer and more specific
definition of edit in the controller would override the older, more
general one in Object).
This is cool because it means I can probably change the name of my
method and get Rails compatibility. But it's not really Rails
compatibility, it's just dodging one frequent symptom of an underlying
problem which persists. So I'm going to see if I can find out more.
I'll submit a patch if I discover anything useful.
giles
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
