Tom Christiansen wrote: > > That's hardly the problem with indirect object syntax. Besides > what I just mentioned, there is the fact that it's acting in a > fashion that you could call stronger than a unary operator in terms > of precedence. This is also mentioned in the RFC, although probably not clearly enough. I also wasn't claiming to fix *the* problem, just *a* problem. If you read the RFC, I think you'll see this opens doors to a lot of benefits. It probably has to be fleshed out considerably, but I'm sure the people on -subs will definitely be able to help there. -Nate
- Re: RFC 168 (v1) Built-in functions should be functi... David L. Nicol
- Re: RFC 168 (v1) Built-in functions should be functi... Damian Conway
- Re: RFC 168 (v1) Built-in functions should be fu... Tom Christiansen
- Re: RFC 168 (v1) Built-in functions should b... John Porter
- Re: RFC 168 (v1) Built-in functions should b... Piers Cawley
- Re: RFC 168 (v1) Built-in functions shou... Tom Christiansen
- Re: RFC 168 (v1) Built-in functions... Piers Cawley
- Re: RFC 168 (v1) Built-in functions... Damian Conway
- Re: RFC 168 (v1) Built-in functions should be fu... Nathan Wiger
- Re: RFC 168 (v1) Built-in functions should b... Tom Christiansen
- Re: RFC 168 (v1) Built-in functions shou... Nathan Wiger
- Re: RFC 168 (v1) Built-in functions should be fu... John Porter
- Re: RFC 168 (v1) Built-in functions should be functions Damian Conway
- RE: RFC 168 (v1) Built-in functions should be functions Fisher Mark