vwwvvw

5 ms·

1.
by vwwvvw 8y ago
I don't remember what we read in university, but here's a short list from the top of my head: 1. Read "Dragon Book" as an easy reading. Nothing from it is going to end up in your programming language, but it puts you on
2.
by vwwvvw 8y ago
> Is there any reason I should avoid having too many keywords? Yes, a lot of the reasons. Not only users might want to use those words for something else, and not only you make your parser bigger, but you also make a language description
3.
by vwwvvw 8y ago
> Not array, but list. First, nobody needs lists in 2018. Lists is a horrible data structure with most operations having bad asymptotic complexity. There are usages in algorithms (skip lists etc), but end-user code just never uses lists.
4.
by vwwvvw 8y ago
> Let me start off by conceding that you're more knowledgable and experienced than me (which you inferred from my post and attempt at designing a language anyway) and I am in no way trying to challenge that. Self-humiliation never
5.
by vwwvvw 8y ago
> Only people who have trained at the feet of experts are allowed to try their hand at designing a language? You have to be able to design language to start doing it. We do not expect random people giving other people drug recipes to bec
6.
by vwwvvw 8y ago
Yay, arbitrary undocumented language for comments!
7.
by vwwvvw 8y ago
> Flat is better than nested That's fine for namespaces, but given the choice of aggregation (which implies more nesting) or inheritance (which implies lack of rigor), I'd choose more nesting. > Errors should never pass sile