I believe Enumerable#group_by also migrated from Rails.
James Edward Gray II
···
On Feb 5, 2009, at 6:40 AM, David A. Black wrote:
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Hi --
On Thu, 5 Feb 2009, Radosław Bułat wrote:
On Thu, Feb 5, 2009 at 4:09 AM, Ken Bloom <kbloom@gmail.com> wrote:
AFAIK, Rails isn't available for 1.9 yet, and much of the good stuff in
the Ruby 1.9 APIs is actually inspired by and taken from Rails.
I don't think so. I can name only one thing (Symbol#to_proc) which was
popularized by rails (and even not invented by rails itself).
There's also #each_with_object.
Radosław Bułat wrote:
AFAIK, Rails isn't available for 1.9 yet, and much of the good stuff in
the Ruby 1.9 APIs is actually inspired by and taken from Rails.
I don't think so. I can name only one thing (Symbol#to_proc) which was
popularized by rails (and even not invented by rails itself).
HashWithIndifferentAccess?
What does this have to do with Ruby 1.9 inclusions?
sandal:~ $ irb19
{ :a => 1 }["a"]
=> nil
HashWithIndifferentAccess
NameError: uninitialized constant HashWithIndifferentAccess
from (irb):2
from /Users/sandal/lib/ruby19_1/bin/irb:12:in `<main>'
Unless it's under another name, I think this was an idea that was
toyed with a while ago and dropped.
-greg
···
2009/2/5 Phlip <phlip2005@gmail.com>:
On Thu, Feb 5, 2009 at 4:09 AM, Ken Bloom <kbloom@gmail.com> wrote:
--
Technical Blaag at: http://blog.majesticseacreature.com
Non-tech stuff at: http://metametta.blogspot.com
"Ruby Best Practices" Book now in O'Reilly Roughcuts:
http://rubybestpractices.com
I'd definitly put the whole string encoding: that's changed pretty
much completely. And there are a few more things within the string
class but they are pretty minor. Also there's some trickery about
variables scopes in 1.8 that has been "fixed" in 1.9.1.
But as others said for most people the transition from 1.8 to 1.9
should be pretty painless (transitioning the actual codes may be
another matter, I don't know). And if you are stuck at any point, feel
free to send a message to this list and I am sure you'll get tons of
advices plus people will warn you if that's something that's been
changed in 1.9.
So in the end, enjoy learning 1.8: 1.9 is still pretty similar! 
Diego
···
On Feb 3, 7:12 pm, Zayd Abdullah <devruby...@gmail.com> wrote:
Thanks Guys. So in a short list, what should be the features to stay away
from in 1.8, I just purchased "Beginning Ruby" by Peter Cooper, I really
would hate to struggle trying to get something then find out its no longer
needed or being used in 1.9 lol.
It is also in ruby facets. I guess that facets invented many things
that was imported to rails but I don't know what about group_by.
···
2009/2/5 James Gray <james@grayproductions.net>:
On Feb 5, 2009, at 6:40 AM, David A. Black wrote:
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Hi --
On Thu, 5 Feb 2009, Radosław Bułat wrote:
On Thu, Feb 5, 2009 at 4:09 AM, Ken Bloom <kbloom@gmail.com> wrote:
AFAIK, Rails isn't available for 1.9 yet, and much of the good stuff in
the Ruby 1.9 APIs is actually inspired by and taken from Rails.
I don't think so. I can name only one thing (Symbol#to_proc) which was
popularized by rails (and even not invented by rails itself).
There's also #each_with_object.
I believe Enumerable#group_by also migrated from Rails.
--
Pozdrawiam
Radosław Bułat
http://radarek.jogger.pl - mój blog
Facets *collects* many more things than it invents.
-greg
···
2009/2/5 Radosław Bułat <radek.bulat@gmail.com>:
It is also in ruby facets. I guess that facets invented many things
that was imported to rails but I don't know what about group_by.
--
Technical Blaag at: http://blog.majesticseacreature.com
Non-tech stuff at: http://metametta.blogspot.com
"Ruby Best Practices" Book now in O'Reilly Roughcuts:
http://rubybestpractices.com