The Evolution of C Programming Practices: A Study of Unix (2016) [pdf]

Re:The Evolution of C Programming Practices: A Study of Unix... by buserror on Friday May 11, 2018 @03:50PM (#17050350)

Yes and it annoys me no end that clang has refused to implement them as well, as they were part of my codebase as well... How better to implement stuff like qsort() callbacks than with a simple, contextual small function just over it ??

YES it is dangerous due to stacks etc etc but hey, we're grown up adults, not script kiddies.

[ Parent | on HN ]

Re:The Evolution of C Programming Practices: A Study of Unix... by basementcat on Friday May 11, 2018 @05:47PM (#17050998)

Clang has Blocks instead of nested functions. There may be patches for gcc-4.2 for Blocks but they didn't make it to the mainline.

https://en.wikipedia.org/wiki/Blocks_(C_language_extension)

[ Parent | on HN ]

Re:The Evolution of C Programming Practices: A Study of Unix... by pjmlp on Saturday May 12, 2018 @02:14AM (#17052723)

> YES it is dangerous due to stacks etc etc but hey, we're grown up adults, not script kiddies.

That is how CVEs are born.

[ Parent | on HN ]

Re:The Evolution of C Programming Practices: A Study of Unix... by bgongfu on Saturday May 12, 2018 @06:06AM (#17053329)

Using a chainsaw without paying attention is how fingers are cut off, using that as an argument against making chainsaws easier to use doesn't make any kind of sense.

[ Parent | on HN ]

Re:The Evolution of C Programming Practices: A Study of Unix... by pjmlp on Saturday May 12, 2018 @10:31AM (#17054213)

Good chainsaws have protection mechanisms builtin.

C does not.

[ Parent | on HN ]

Re:The Evolution of C Programming Practices: A Study of Unix... by bgongfu on Sunday May 13, 2018 @06:52AM (#17058285)

Good for you maybe, projecting that on people who have a clue what they're doing doesn't make sense either. They're mostly messing up chainsaws as well these days, for the same misguided reasons.

[ Parent | on HN ]