Rails - Oct 2007 - Why does error_messages_for take string as param?

Hi,

I wonder why error_messages_for take strings as params instead of
instance variables.

error_messages_for ''user''
instead of
error_messages_for @user

''user'' is translated into @user eventually.
If so, who not take the instance variables directly?
Is there any reason for that?

Thanks in advance.

Sam
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Take a look at this patch http://dev.rubyonrails.org/ticket/9699

On Oct 3, 6:14 pm, Sam Kong
<rails-mailing-l...-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:
> Hi,
>
> I wonder why error_messages_for take strings as params instead of
> instance variables.
>
> error_messages_for ''user''
> instead of
> error_messages_for @user
>
> ''user'' is translated into @user eventually.
> If so, who not take the instance variables directly?
> Is there any reason for that?
>
> Thanks in advance.
>
> Sam
> --
> Posted viahttp://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Pablo Castellazzi wrote:
> Take a look at this patch http://dev.rubyonrails.org/ticket/9699
Thanks for the info.
So now the method definition is officially changed?

Sam
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

On 4 Oct 2007, at 16:33, Sam Kong wrote:
>
> Pablo Castellazzi wrote:
>> Take a look at this patch http://dev.rubyonrails.org/ticket/9699
>
> Thanks for the info.
> So now the method definition is officially changed?
>
Nope - I submitted that patch, but it hasn''t yet been committed.

Fred

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---