Re: Select and how to read the api

Phlip wrote:
>>> (And note to whoever named a method 'select' - please don't!!!)
> 
>> Why not use 'select'? It works fine.
> 
> Because programs must share a large namespace in memory, and a larger 
> one in
> our brains. 'select' is already used by Array, certain network sockets, 
> and
> (in some languages) a keyword. Primitive things should have primeval 
> names,
> such as 'select', and complex & specific things should have decorated 
> names.
> If all the other Rails HTML generators end in _tag, then select_ should 
> too!

I understand. But it must be a Rails-tag, otherwise it wouldn't work.

I just couldn't get the select_tag to work with manual values. I mean 
what's the point of using it, and some other rails-tags actually, when 
it's as much hassle to write the html-tag?

I think this is a good example of the backside of Rails, the 
documentation. I wonder if they plan to update it? Wouldn't hurt if they 
did.
--

-- 
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@...
To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---