On Nov 9, 9:44   
>
> I suppose the whole discussion is moot as Ruby will likely never see a ++
> operator.
>
> I was just trying to make clear the limitation wasn't a technical one, and
> further show how a ++ operator could be "Ruby-like" while still retaining
> C/C++/Java-like semantics.

If implementing ++ requires changes to the parser, that seems like a
pretty technical limitation to me! :)

Matter of interpretation?

BTW in all your posts on the topic, you don't seem to address pre-
increment vs post-incrememt.  (Forgive me if I'm wrong.)  If Ruby
implemented ++ and didn't address that, it wouldn't be C or C++
semantics at all.

--
Gavin Sinclair