Re: RFC 159 (v1) True Polymorphic Objects
[email protected] (Damian Conway)
| Newsgroups | perl.perl6.language.objects |
|---|---|
| Message-ID | <[email protected]> |
> Data Conversion and Access > ------------------------------------------------- > STRING Called in a string context > NUMBER Called in a numeric context > BOOLEAN Called in a boolean context > > > Operator Overloading > ------------------------------------------------- > PLUS Called in + context > MINUS Called in - context > TIMES Called in * context > DIVIDED Called in / context > MODULUS Called in % context DIV and MOD would suffice I think > NUMCMP Called in <=> context > NUMEQ Called in == context > NUMNE Called in != context > NUMLT Called in < context > NUMGT Called in > context > NUMLE Called in <= context > NUMGE Called in >= context > > STRCMP Called in cmp context > STREQ Called in eq context > STRNE Called in ne context > STRLT Called in lt context > STRGT Called in gt context > STRLE Called in le context > STRGE Called in ge context CONCAT Called in . context > BITAND Called in & context > BITOR Called in | context > BITXOR Called in ^ context > BITNOT Called in ~ context LOGHIGHAND Called in && context LOGHIGHOR Called in || context LOGLOWAND Called in and context LOGLOWOR Called in or context LOGIFELSE Called in ?: context > Assignment and Existence > ------------------------------------------------- > CREATE Called in object creation I'll address this more fully in a forthcoming RFC Damian