I sent this on to some runner friends of mine, and a couple of them said it'd be pretty cool if there was an optional box for "time run" as well. (Marathon runners like to train by time, I guess).
Paul, I think a lot of the arc emo-kids would be assuaged if you would talk a little bit more about whether you outright reject the possibility of unicode in Arc versus whether or not you just hadn't gotten to it.
I mean, I think a lot of this would die down if you were to say something like "Look, I'm building a language, I haven't gotten to unicode. If someone builds a patch that works, I'd be happy to integrate it in". Or something like that.
I know it would make a difference to me, and would let a lot of people look past the fact that it's missing _right now_
As I read it, character set support isn't that interesting to him right now, and he'd rather focus on other things. Everyone keeps treating it like this version of the language is the final one. Of course it's going to constantly gain new functionality.
If that had been my impression I'd never have posted anything on this rather boring topic. What made me think it might be a permanent design decision is this extract from the Arc intro: "[...] it doesn't support any character sets except ascii. Such things may have their uses, but there's also a place for a language that skips them"
The problem is that it's left open to interpretation. Sure, he said Arc is a work in progress, and everyone gets that. The problem is knowing what's on the table for change, and what's not.
An instance of MzScheme will only use one cpu even on multi-cpu machines. In order to use more than one cpu, start several instances and let them communicate either via tcp or via files.
