file extension for the build file gives off a red flag for me. It's not objectively incorrect but feels like the authore has no idea what is happening around him.
Name:
Anonymous2018-02-03 13:46
Bro look at this dude uhu uhu wait till you see the f... uhohohoho no no NO NO.. OH HA HOH ohhhHOHOoooo.... ARHHHHHHH HAHAHAHAHAHAHAHAHAHA AAA LOOK AT THE TOP OF HIS CODE HRHHHHHHHAHAHAHAHAHAAA LOOK AT HIS SITE HASHHHJAHAHAHAHAHAHAHHHH
Name:
Anonymous2018-02-03 15:47
Someone who doesn't understand the reason for some of the few reasonable choices in C reinvents it badly and tacks a few GCC extensions and Sepples things on. Pretty much the only change that isn't pointless or actively harmful is the part about modules.
At first I wanted to ask why things like these happen so often, but after a while I remembered a post about Unix and C from a while ago (it might even have been a Naggum post on Usenet) that makes the reason very clear. It claimed that Unix shit is so popular because it is so obviously broken that people see it and think: ``I can fix this!'', thereby leading another poor soul to its doom creating another Unix developer. Anybody can look at C and find something stupid that is easy to fix — now try this with a language like Common Lisp. Not only does it often already have your great idea but better, but when it doesn't, the idea usually wasn't very great to begin with and rooted in some misunderstanding about the language or programming. inb4 dead dog
>>1 Lemme guess: the author doesn't understand header files and thinks the preprocessor must be erased at all costs (instead of being fixed), just like any other nu-C does ("Those damn pointers and preprocessor are so hard to understand!!")?!?
Also:
Language changes [..] * All global variables are initialized by default
...REALLY? Oh yeah right, because they're called static and not global in C or what?
Name:
Anonymous2018-02-04 17:37
* All global variables are initialized by default
Same for C though..
Name:
Anonymous2018-02-04 17:58
>>20,21 Reminds me of the GNOME version of free whose only ``difference'' was that free(NULL) was defined. Shows you how competent these pioneering Redhat luminaries are.
Name:
Anonymous2018-02-04 20:34
>>22 You and the GNOME devs haven't even read da standard
The free function causes the space pointed to by ptr to be deallocated, that is, made available for further allocation. If ptr is a null pointer, no action occurs.
Name:
Anonymous2018-02-04 23:56
>>23 That's my point. They ``fixed'' a problem that didn't exist, yet think they are qualified to write a better standard library for applications.