News for hackers. Stuff that matters.
Re:Dale – A Lisp-flavoured C by hermitdev on Monday April 10, 2017 @09:07PM (#14084047)
Yikes, yeah, this is bad. I only went through the readme, I didn't look at the source, and just...no. NULL? no. nullptr, please. And, as you've said, const char* as strings? again, no. I know GLS isn't terribly old, but something like string_view is in order. Arguments as undecorated pointers...no. Are they in or out? optional? C++ has semantics to indicate these things (even without GLS).
Re:Dale – A Lisp-flavoured C by andrewchambers on Monday April 10, 2017 @10:13PM (#14084331)
This thread of conversation is unproductive. Could you link me to both of your respective github accounts so I can nitpick without any stake or contribution in your projects?
Re:Dale – A Lisp-flavoured C by kazinator on Monday April 10, 2017 @11:49PM (#14084698)
You may criticize anything I've ever written that you can find. As a software developer, that's my daily assumption.

The increasing adoption of code review tools like Gerrit is one of the best things that has been happening in recent years.

No piece of code I've written in the past few years on the job has gone into the stream without the approval of several people.

Frequently, it had to be revised. More than once.

Re:Dale – A Lisp-flavoured C by hermitdev on Tuesday April 11, 2017 @08:52PM (#14093905)
No, because I'm bound by contract, cannot disclose my source, and I'm under NDA. That said, my comments are not unreasonabe or overly critical for C++11 or newer code. Quite honestly, if I desired to, there's more I could probably find issue with in even that small of a code sample.
Re:Dale – A Lisp-flavoured C by milesrout on Monday April 10, 2017 @11:11PM (#14084544)
It's not unproductive. The project was linked, and code quality is relevant.