3 ms·
I read c# spec when it was in beta, going fast through it, skimming less informative parts, taking quick notes as bullet points in form of single statement or q
by mirekrusin 10y ago
I read c# spec when it was in beta, going fast through it, skimming less informative parts, taking quick notes as bullet points in form of single statement or question. It was one of the best experiences, it put me in flow mode and I learned a lot in very short time. I used c# later professionally and never had problems. Great thing about language specs is that is very precise, without mistakes. The art is to read+skim+note it quite fast.
- majewsky 10y ago> Great thing about language specs is that is very precise, without mistakes. I'd also add "concise" to the list of required traits for a good language spec. If you don't believe me that's important, go check out the C++ specification. IIRC it contains some 50 pages of rules on how to choose implementations of an overloaded function.
- joatmon-snoo 10y agoAnd if you're looking at modern C++, you also get to learn about lvalues, glvalues, xvalues, rvalues, and prvalues!
- webmaven 10y agoprvalues are the ones that return a promise about a system's future state which are commonly expected to prove false, right?
- hardwaresofton 10y agoWas this not a direct (possibly knee-jerk) reaction to the ease with which you could shoot yourself in the foot, and undefined behavior C allows?