>> I think we are saying the same thing: using the object's own methods >> (to_i, to_a, to_f, etc.) to typecast/coerce is absolutely the right >> thing to do. Unfortunately, Rails currently goes beyond that level of >> coercion and Josh's original proposal on this post was to go even >> further to coerce booleans using external logic. It's the use of >> external logic that I characterized as "guessing." > > Agreed :-)
I'd definitely love to see some work done on tidying up the conversion code and making it more consistent and testable. In the meantime the patch is a nice pragmatic solution until someone has the time and the inclination to spend time doing that rework. If you're that person, drop us a line :) -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
