[#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:10:02 UTC
List: ruby-core #6876
On Dec 12, 2005, at 1:42 PM, ara.t.howard@noaa.gov wrote:

> On Tue, 13 Dec 2005, James Edward Gray II wrote:
>
>> I haven't followed this discussion much, but I've seen similar  
>> issues with
>> Rails.  Our current app at work defines some constants and we see  
>> constant
>> redefined warnings every time we run the tests.
>
> o.k.  that's pure evil.  any suggestions?

Hmm, I just went to look into this a little with the aforementioned  
app, and guess what's gone?  No warnings at all now.  Guess I should  
look before I complain.  ;)

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.

Sorry for the misinformation.

James Edward Gray II

In This Thread