From: Simon Cozens Date: 2002-11-26T18:46:12+09:00 Subject: Re: Things That Newcomers to Ruby Should Know (11/24/02) "Gavin Sinclair" writes: > > Confusing implementation limitations and language design was Perl 5's big > > problem. Don't let it become Ruby's big problem too. > > The above code merely demonstrates that String#chomp! doesn't modify 'self', > rather it modifies the data of the object. What I'm saying is that proof-by-current-implementation isn't a great way to argue the presence or absence of a feature. > The only "implementation limitations" discussed here are that > integers are immediate values. No problems arise from this - except > that ++ doesn't behave as in C/Java/Perl. And that's not even a > problem, just a surprise for some people. It may not even be a surprise. I don't think that most people would care (or even notice) that a hypothetical foo.succ! gave them a different object back from the one they started with. -- There's no cinnamon and no lemon or orange involved. If there were, it was a heretic who mixed it up and the mixer should be impaled on a stake and buggered by the Shrike for two hours, then taken down and forced to rub the wounds with the mix until death sets in. - Ingvar Mattsson *cares* about cocktails.