On Mon, 21 Jun 2010 21:44:04 -0700
Mark Engelberg <mark.engelb...@gmail.com> wrote:

> The new uber-loop is fantastic.
> 
> So I guess the main point still to be finalized is whether the default
> arithmetic ops will auto-promote or error when long addition
> overflows.

I think calling them "default" gives the wrong idea here. We have two
behaviors for the math operators, so we need two sets of names. When
the existing set auto-promoted and the "other" set worked with
primitives, then calling them <op>' was a mnemonic (PRIMe implying
PRIMitive math).

But if it's going to be the other way 'round, then the "new" names
don't work as well. I propose (again, since nobody commented on it the
first time) that the two sets of ops be:

non-autopromoting math: +, -, *, /, ++, -- (if you want to muck with
the rules for symbols, the last two could be drawn from [+-]?1[-+]?
instead).

autopromoting math: add, sub, mul, div, inc, dec

No mucking about with namespaces, no settings to toggle behaviors -
you use the set you want. When teaching the language, you can use the
words and not have to worry about explaining about primitive types,
boxing, or anything else.

While I'm at it, do we still need the postfix N on bignums? Since both
the reader and humans do the right thing even if it's not there, we
shouldn't need it for output any more, even there might be times when
it's handy for input.

     <mike
-- 
Mike Meyer <m...@mired.org>             http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.

O< ascii ribbon campaign - stop html mail - www.asciiribbon.org

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en

Reply via email to