I was bothered by “I still use Vim in 2015 as my primary text editor”, not because Vim is bad, but because it feels apologetic. Lots of developers still use Vim–prefer it, even, over everything else. Don’t ever apologize for a preference.
As for the rest of the article, this is very neat. Automated, autoupdating tags is somethi g Ive always wanted in emacs.
That was actually a kind of ironic/sarcastic. :) But anyway, I decided to remove it, thanks.
There are C++ compilers for some embedded CPUs, but they are uncommon, so I need to stick to C, in the name of portability.
Then get a different CPU/toolchain. Why would you make things more difficult for yourself. Also, C++-to-C compilers exist (or used to exist)
Discussed a lot already. See the discussion on HN: https://news.ycombinator.com/item?id=10260517
Excellent write-up. I too was confused by the Wikipedia definition of a closure and found your article and diagrams very helpful. Thanks for writing this! :)
Glad you liked it, you’re welcome!
I’d like to add two more tags to this publication: “unit-testing” and “embedded”. Sadly, there are no such tags, and I seem unable to create them. If someone with powers reads this, please consider adding the aforementioned tags. Thanks.
Seconding that an embedded tag would be appreciated! “Hardware” isn’t quite the same.
An embedded tag would be great, and a testing one too. I wouldn’t restrict it to “unit-testing”, mind you.
Oh, agreed, no need to be that precise. testing is great.