Andrei Alexandrescu wrote:
Sergey Gromov wrote:
Don wrote:
If you could completely ignore keyboard and display issues, and use any
unicode character as an operator, which ones would you actually use?
I'd use dot ⋅ and cross × products for 3D, union ∪ and
intersection ∩, subset ⊂ and superset
Andrei Alexandrescu wrote:
* There is a way of specifying that precedence of a function defined as
above is the same as precedence of a built-in operator.
That throws out the ability to parse without semantic analysis. It's not
worth it.
Walter Bright wrote:
Andrei Alexandrescu wrote:
* There is a way of specifying that precedence of a function defined
as above is the same as precedence of a built-in operator.
That throws out the ability to parse without semantic analysis. It's not
worth it.
It doesn't per a previous post
Don wrote:
If you could completely ignore keyboard and display issues, and use any
unicode character as an operator, which ones would you actually use?
I'd use dot ⋅ and cross × products for 3D, union ∪ and
intersection ∩, subset ⊂ and superset ⊃ and their negative forms.
I don't think I'd use
Sergey Gromov:
I'd use dot â
and cross à products for 3D, union ⪠and
intersection â©, subset â and superset â and their negative forms.
I don't think I'd use anything else.
I just want to note that the whole thread is almost unreadable on the
digitalmars.com/webnews/, because it
On Wed, Oct 29, 2008 at 4:12 AM, Andrei Alexandrescu
[EMAIL PROTECTED] wrote:
Sergey Gromov wrote:
Don wrote:
If you could completely ignore keyboard and display issues, and use any
unicode character as an operator, which ones would you actually use?
I'd use dot ⋅ and cross × products for
