From: "trans.  (T. Onoma)" <transami@...>
Date: 2004-10-09T12:32:40+09:00
Subject: Re: ANN: Free-form-operators patch

On Friday 08 October 2004 11:12 pm, Markus wrote:
| This is a very good description of why I'm unsure about letting the
| user set the precedence/associativity/arity.  Do you mind if I use it?
|
|      The best answer I have come up with so far, is to require that if
| they're compile-time properties are changed they must be declared before
| their first use, and that any additional declaration must match.
| Declarations of this sort are not commonly done in ruby (but they are
| not unheard of either).

Just a thought. Since you are already using only character already used in 
Ruby operators (which I think is good idea) then you may also fix the 
precedence according to those. You would just need to come up with good set 
of rules. For example, where R means one or more other op-chars:

  Ruby (high to low)        User defined examples with same precedence
  **                        R** **R R**R  (contains ** goes right to top)
  ! ~ + -                   all unary operators (can we do those 'def @++' ?)
  * / %                     *R /R %R
  + -                       +R -R
  &                         &R
  ^ |                       ^R |R
  < >                       <R R>
  =                         =R R=R  (equals on end illegal)

It may have to be a bit more complex then that but you get the idea. Like I 
said, just a thought.

T.