Now, may I ask you to at least try to tell where exactly did I claim that. I know that e.g. accusing other people of rape without a reason is a cultural norm in some countries, but I'm not from there.
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…
> 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…
> 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…
> 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.…
> 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…
Yay, arbitrary undocumented language for comments!
> 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…
Now, may I ask you to at least try to tell where exactly did I claim that. I know that e.g. accusing other people of rape without a reason is a cultural norm in some countries, but I'm not from there.
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…
> 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…
> 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…
> 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.…
> 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…
Yay, arbitrary undocumented language for comments!
> 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…