> > They behave similarly like &&, ||, and, or operator with one main > > distinction they "backtrack" for example: > > > > { block1 } B<andthen> { block2 }; > > This would be a good use of the to-be-liberated => operator: > > { block1 } => { block2 }; > > In any case, "andthen" doesn't seem like a good choice. > Other possibilities: > therefore > implies > segue > seq > so ]- any proposal for the name are welcome....they must be two..... the reason I decided to use this is cause it works like/is similar to -> if-then-else, also look like and/or comparions operator. The Prolog operators "," and ";" are already overused in perl. THEN is not used by PERL, so here comes : AND+THEN OR+THEN :") ===== iVAN [EMAIL PROTECTED] =====
- RFC 104 (v1) Backtracking Perl6 RFC Librarian
- Re: Component wise || and RFC 82 (was Re: RFC 104... Damien Neil
- Uses for array notation (was Re: RFC 104 (v1) Bac... Jeremy Howard
- Array notation (was Re: RFC 104 (v1) Backtracking... Jeremy Howard
- Re: RFC 104 (v1) Backtracking raptor
- Re: RFC 104 (v1) Backtracking Jeremy Howard
- Re: RFC 104 (v1) Backtracking Jonathan Scott Duff
- Re: RFC 104 (v1) Backtracking:example raptor
- Re: RFC 104 (v1) Backtracking raptor
- Re: RFC 104 (v1) Backtracking Johan Vromans
- Re: RFC 104 (v1) Backtracking Jeremy Howard
- Re: RFC 104 (v1) Backtracking John Porter
- Re: RFC 104 (v1) Backtracking raptor
- Re: RFC 104 (v1) Backtracking Chaim Frenkel
- Re: RFC 104 (v1) Backtracking John Porter
- Re: RFC 104 (v1) Backtracking David L. Nicol