[#6864] ruby 1.8.4 rc breaks alias_method/rails in bad ways — "Ara.T.Howard" <ara.t.howard@...>

20 messages 2005/12/09
[#6870] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — =?ISO-8859-15?Q?Florian_Gro=DF?= <florgro@...> 2005/12/12

Ara.T.Howard wrote:

[#6872] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — ara.t.howard@... 2005/12/12

On Tue, 13 Dec 2005, [ISO-8859-15] Florian Growrote:

[#6873] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — James Edward Gray II <james@...> 2005/12/12

On Dec 12, 2005, at 1:19 PM, ara.t.howard@noaa.gov wrote:

[#6874] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — ara.t.howard@... 2005/12/12

On Tue, 13 Dec 2005, James Edward Gray II wrote:

[#6891] Time.utc! and Time.localtime! — Daniel Hobe <hobe@...>

Writing a script yesterday I found out, much to my surprise, that the

16 messages 2005/12/14

[#6918] change to yaml in 1.8.4 — ara.t.howard@...

14 messages 2005/12/16

[#6934] 1.8.x, YAML, and release management — Ryan Davis <ryand-ruby@...>

I'm concerned that 1.8.3's acceptance of non-backwards-compatible

28 messages 2005/12/18

[#6996] Problems building 1.8.4 with VS8 C++ Express Edition (cl 14.00) — Austin Ziegler <halostatue@...>

Visual Studio C++ 2005 Express Edition (VS 8.0)

20 messages 2005/12/27

Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways

From: James Edward Gray II <james@...>
Date: 2005-12-12 20:36:44 UTC
List: ruby-core #6877
On Dec 12, 2005, at 2:10 PM, James Edward Gray II wrote:

> I'm *assuming* the change is that we've updated the vendor/rails/  
> directory to a more recent version.  I'm still running Ruby 1.8.2,  
> but was when I was seeing the errors too.  Might make sure your  
> Rails is up-to-date.

As usual, I was wrong.  The /vendor/rails/ is the same version.  My  
partner changed the constant definitions to avoid the warnings:

OUR_CONST = ... unless const_defined? "OUR_CONST"

So, I added a warning statement above those declarations and I see  
that it is indeed executed twice.  While I was in there, I noticed  
that controller is a base controller that at least one other  
controller inherits from.  Testing a theory, I added a warning to an  
uninherited controller and this is what I see in my test output:

...
Loading uninherited controller.
Loading base controller.
Loading base controller.
...

Something is fishy there.  Does Rails munge const_missing() by chance?

James Edward Gray II


In This Thread