> >What if I want to overload && and || so that they help built an expression > >tree, rather than immediately evaluating? > > Is it worth the damage it will cause to fragile brains like mine? "Pain is the weakness leaving your body!" ;-) > I have often wondered whether a language could allow user-defined > operators. The fact that none have done it should be a clue :-) I guess > it's getting too incestuous with the lexer. User-defined operators are a can of rattle-snakes that I *seriously* recommend we don't open. Damian
- Re: Overloading && || Nick Ing-Simmons
- Re: Overloading && || Nathan Torkington
- Re: Overloading && || Bryan C . Warnock
- Re: Overloading && || Dan Sugalski
- Re: Overloading && || Bryan C . Warnock
- Re: Overloading && || Dan Sugalski
- Re: Overloading && || Chaim Frenkel
- Re: Overloading && || David L. Nicol
- And A Parser In A Pared Tree ... Bryan C . Warnock
- Re: And A Parser In A Pared T... David L. Nicol
- Re: Overloading && || Damian Conway
- Re: Overloading && || Damian Conway
- Re: Overloading && || Dan Sugalski
- Re: Overloading && || Randal L. Schwartz
- Re: Overloading && || Nathan Torkington
- Re: RFC 49 (v1) Objects should have builtin string... Nathan Wiger
- Re: RFC 49 (v1) Objects should have builtin st... Ken Fox
- Re: RFC 49 (v1) Objects should have builti... Nathan Wiger
- Re: RFC 49 (v1) Objects should have bu... Michael Fowler
- Re: RFC 49 (v1) Objects should ha... Bart Lateur
- Re: RFC 49 (v1) Objects should have builtin string SCAL... Jeremy Howard