On Fri, Oct 04, 2002 at 04:26:28AM +0900, Travis Whitton wrote:
> I'm writing this to report a bug as related to Ruby's principle of
> least surprise regarding nested string interpolation. I was happily
> coding along and accidently constructed something equivalent to the
> following:
> 
> list = %w{yes it can}
> puts %Q! Nested string interpolation
>          cannot be done in ruby...
>          #{
>             list.map {
>               |elem|
>               ".. #{elem} .." # weird nest
>             }
>           }
> !
> 
> I was so certain this wouldn't work that I barely bothered to test it.
> Imagine my surprise at seeing the following:
> 
>  Nested string interpolation
>         cannot be done in ruby...
>         .. yes .... it .... can ..
> 
> So, the bug is that Ruby is "too slick", and I demand that this bug be

IMO Ruby's design is broken with regard to slickness. Furthermore, it
seems that matz won't ever even consider to fix this bug. It probably
could only be solved if he were hit by a bus.

IMNSHO Rubyists who --- justifiedly --- view this as a bug should
seriously consider to move to Basic, which arguably provides the
ultimate brain-dead-language experience.

> "patched" to insure fair competition with other languages. Am I correct
> in assuming that parse.y would be the proper place to start tracking down
> this "problem"?

I think the best way to cope with Ruby's excessive slickness is, ahem,
doing something about matz. You understand what I mean.

> Sincerely,
> Travis Whitton <whitton / atlantic.net>
> 
> p.s., yes this is a joke ;-)

And a good one :) better than by baroque humor.

-- 
 _           _                             
| |__   __ _| |_ ___ _ __ ___   __ _ _ __  
| '_ \ / _` | __/ __| '_ ` _ \ / _` | '_ \ 
| |_) | (_| | |_\__ \ | | | | | (_| | | | |
|_.__/ \__,_|\__|___/_| |_| |_|\__,_|_| |_|
	Running Debian GNU/Linux Sid (unstable)
batsman dot geo at yahoo dot com
  
* gb notes that fdisk thinks his cdrom can store one terabyte
	-- Seen on #Linux