Timeline for Generic stack in C
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 15, 2015 at 7:10 | comment | added | lord.garbage | @Lundin, fair point! | |
| Jul 14, 2015 at 18:38 | comment | added | Lundin | @brauner There's a lot of sloppy, ugly and incorrect things that are common practice among C programmers... | |
| Jul 14, 2015 at 15:51 | comment | added | lord.garbage |
@Lundin, thanks. Though MISRA states that !x as advisory (Rule 13.2) and not required and only in the interest of clarity. It is such a common C idiom that I do not necessarily see a problem with this unless required by a specific coding style.
|
|
| Jul 11, 2015 at 13:15 | comment | added | Lundin |
@jacwah Because ! is a boolean operator and for the sake of readability it should only be used on expressions that are "effectively boolean". Good C programmers program as if C had a real, type safe boolean type. Don't mix up booleans with integers or pointers. In any other programming language such things wouldn't even compile. References MISRA-C:2004, MISRA-C:2012 etc.
|
|
| Jul 11, 2015 at 13:05 | comment | added | Lundin | @Edward Because that's how you properly design C programs with private encapsulation. Why would I assume that the OP doesn't want a proper program design? | |
| Jul 11, 2015 at 1:26 | comment | added | jacwah |
This would be a gret answer if you went a bit more into the why?, especially in the style part were you make some controversial claims (return from main and dont' use !) without backing them up.
|
|
| Jul 10, 2015 at 13:52 | comment | added | Edward | Why do you assume that an opaque type was a design goal? | |
| Jul 10, 2015 at 13:40 | history | answered | Lundin | CC BY-SA 3.0 |