Rails core - Mar 2007 - Smooth Transition verus Cliff Jump

I like the strategy of issuing deprecation notices way in advance.
But, I think we need to allow people an alternative _which will run in
Rails 1.1_.

That is, we shouldn''t force people to choose between dropping 1.1
support *or* cluttering up their console with zillions of deprecation
warnings.

Most of the time, you can find a solution which does this.  But there
are some exceptions - end_form_tag, for example (note that I do *not*
consider succumbing to the </form> asymmetry a good way to support
both).


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

> Most of the time, you can find a solution which does this.  But there
> are some exceptions - end_form_tag, for example (note that I do *not*
> consider succumbing to the </form> asymmetry a good way to support
> both).
So you''d prefer to have warnings spammed into your console than just
write </form>?   It''s not like end_form_tag actually does
anything.

def end_form_tag
  "</form>"
end

Are there any other cases you''ve come across where there
wasn''t a
simple alternative?
-- 
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 rubyonrails-core@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-core-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---