2 ms·
If it helps, I opted for the paperback. Looking forward to giving this one a read. The caps point is interesting to me. I can't think of a good reason why ca
by taeric 6y ago
If it helps, I opted for the paperback. Looking forward to giving this one a read.
The caps point is interesting to me. I can't think of a good reason why caps should be shouting, but I definitely agree with it. Hilarious to remember back when mixed case was not the norm. (Also, awkward to work in languages where symbols are case sensitive. Worse when they are case significant.)
I'm curious on the tree representations you mean. Most make some use of whitespace, that I have seen. But they lose the portability of the representation that I have with easy copy/paste to other environments. (To and from chats, emails, etc.)
- Hyolobrika 6y agoWhat is "case significant" vs "case sensitive"? You seem to be speaking as though there is a difference but I can't find anything online.
- taeric 6y agoIn go, starting a function with a capital letter means something.
- nils-m-holm 6y ago> I'm curious on the tree representations you mean. I guess OP meant symbolic expressions (LISP expressions) in general, which can be viewed as trees. E.g.: (FOO BAR . BAZ) would be O / \ FOO O / \ BAR BAZ
- taeric 6y agoRight, I get that. My question is what other forms did they mean? One could use indentation. Basically yaml. That is notoriously bad for copy paste between files, though. Edit: I see you made the same point in another post. I'm calling that portability of the code, though not sure that is the best term.