zlacker

[parent] [thread] 4 comments
1. aston+(OP)[view] [source] 2007-07-06 23:22:35
Automatic creation of the numerical lambda return. Clever...

Why "atom" instead of "leaf"? Especially since you acknowledge it's a "tree"?

replies(1): >>pg+r1
2. pg+r1[view] [source] 2007-07-07 16:12:12
>>aston+(OP)
It's even simpler than that. I changed function application so that if the first element of the expression is a simple type (e.g. a number), it just gets returned.
replies(1): >>aston+r2
◧◩
3. aston+r2[view] [source] [discussion] 2007-07-08 00:49:38
>>pg+r1
That's cool enough. Though, potential spot for allowing subtle bugs? If I'm tossing around what I believe is a function (but instead happens to be a simple type, maybe even like #f or something), when I apply it I'd prefer to get a runtime error instead of a silent value return.
replies(2): >>pg+s3 >>pg+t3
◧◩◪
4. pg+s3[view] [source] [discussion] 2007-07-08 13:13:09
>>aston+r2
Having a more dense language inevitably means that more programs turn out to be accidentally meaningful. Since Arc is designed to be an LFSP, that trade-off is worth it.
◧◩◪
5. pg+t3[view] [source] [discussion] 2007-07-08 13:15:18
>>aston+r2
Having a more dense language inevitably means that more programs turn out to be accidentally meaningful. If the power of a programming language is the inverse of how long programs are (which is the best definition I've found so far), you can't make a language more powerful without the space of meaningful programs becoming denser.
[go to top]