From: Ryan Davis <ryand-ruby@...>
Date: 2008-10-09T03:47:42+09:00
Subject: [ruby-core:19215] Re: Request For Removal: No Operator Concatenation


On Oct 8, 2008, at 11:14 , James Gray wrote:

> I admit that I wasn't aware this was a parse-time optimization.   
> Knowing that at least helps me understand why we have it.

no no no... that's only for my parser (lexer actually). I'm taking  
advantage of it because it is an easier mechanism to use than a lot of  
the other crap that has built up in the grammar. I'm hoping to use it  
to cut out a fair amount of code.

Don't take what I said as ANY reason to keep it in MRI. I agree with  
you that it can be a source of confusion. I just think there are other  
ways you can go about that like the "interpreted as X, make sure"  
warnings we currently get.