Ruby 1.8.6

[dysinger]

I upgraded for fun today and ruby is complaining that rails methods
are now 'private' like ActiveRecord update and Time to_date

?

[dysinger]

I get messages like this:

NoMethodError: private method `update' called for #<Xyz:0x33ee2b8>
NoMethodError: private method `create' called for #<Xyz:0x34050f8>

Which is a regular ActiveRecord object

I'm not seeing the Time to_date NoMethodError that I saw earlier
though

[dysinger]

Now I am seeing the to_date problem again (strange)

NoMethodError: private method `to_date' called for Tue Mar 13 04:10:37
UTC 2007:Time

which is a regular rails extension to Time

[dysinger]

Ahh!

The to_date method problem is on rails 1.2.2
The update and create method problem is on rails edge

Both of them don't appear to like Ruby 1.8.6

[Jeremy Kemper]

On 3/12/07, dysinger <dysi...@gmail.com> wrote:
> Ahh!
>
> The to_date method problem is on rails 1.2.2
> The update and create method problem is on rails edge
>
> Both of them don't appear to like Ruby 1.8.6

This and other 1.8.6 incompatibilities are fixed in the upcoming Rails
1.2.3 release. Look for it shortly.

I haven't seen that #update/create error on trunk.

jeremy

[dysinger]

Ok I got everything working now with rails edge and ruby 1.8.6

Only changes I had to make were no calling create and update on active
record models but instead calling save

On Mar 12, 8:06 pm, "Jeremy Kemper" <jer...@bitsweat.net> wrote:

[Jeremy Kemper]

On 3/13/07, dysinger <dysi...@gmail.com> wrote:
> Ok I got everything working now with rails edge and ruby 1.8.6
>
> Only changes I had to make were no calling create and update on active
> record models but instead calling save

Base#create and #update have always been private methods. They 'broke'
because they were accidentally made public by wrapper methods and a
recent change made them private again:
http://dev.rubyonrails.org/changeset/6396#file5
So this is unrelated to Ruby 1.8.6.

jeremy