Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

What would you change in C?

Name: Anonymous 2009-08-26 13:44

It's the time for the next revision of the C standard and for some reason they want your advice. What do you add, remove, rename, etc ?

Name: Anonymous 2012-02-27 0:19

This thread is fucking fail. C needs:

1. Real string library. Yes, ASCIIZ was a mistake.
2. Expanded standard library. File system abstractions are the big one. Why do we assume all implementations will have files but not folders? struct packing is another problem that is incredibly common and frequently done horribly horribly wrong, but solved with a very simple library.
3. Minor stylistic fixes including non-semicolon terminated labels before end of block, const const cast fixes, remove the untagged nested struct/union bubbling crap, remove the sole register storage class semantic.
4. Better specified sequence point model, in particular synchronizing the order of execution of side-effects between sequence points with the order of evaluation.
5. Consolidation of types. The int, short, long, long long, uint, ushort, ulong, size_t, ptrdiff_t, int, uintn_t, intn_t, intptr_t, int_fastn_t, uint_fastn_t, int_leastn_t, uint_leastn_t, uintptr_t crap is just remarkably stupid. int and char should be implementation defined widths, but it does not make sense for anything else.
6. Better error handling mechanisms. Huge swathes of most large codebases are dedicated to checking return values, the errno crap is incredibly stupid, not thread safe, not even internally consistent. Look at the code for parsing a long in man 3 strtol, and compare with Java catch(NumberFormatException e).
7. Unicode support, wide characters are a fucking plague.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List