>>7
What syntax would you use? I'd be tempted to just steal Seppples', but I think you could probably get away with hacking the preprocessor to do it instead(using #export and #use or something similar)
Name:
Anonymous2009-08-26 14:27
* Remove pointers
* Add compulsory garbage collection, remove free()
* Get rid of the shitty format strings ("%d %s\n")
* Trash the preprocessor
Name:
Anonymous2009-08-26 14:28
Change the syntax so that all types are capitalized, and all other identifiers are lowercase. Or change the type declaration syntax altogether.
>>13
Cause all the kewl pr0gramm3r5 use references AMIRITE?
Name:
Anonymous2009-08-26 15:45
>>2 >>6 >>10
Also true modules, none of this #include "somefile.h" shit (at least not as the only way to split code between compilation units; I'd leave the preprocessor as it is).
I would remove most of the shit in C99 that nobody has implemented anyway. Other than that, C is perfect and changing it requires renaming the result because it isn't C. I will admit, however, that adding namespaces and function overloading would be nice.
>>23 here: I would also like to see someone implement function overloading by return type.
Name:
Anonymous2009-08-26 21:57
Macros that don't suck are the thing it needs most, but the problem with C is that it's not actually powerful enough to write macros in, so any macro system would need to be a completely different language. Ugh.
Name:
Anonymous2009-08-26 22:02
C is the most optimization-friendly language. That is the only thing I care about.
>>27
That would make it so that x ** y could either mean pow(x, y) or mul(x, *y). This ambiguity is unacceptable, because no compiler can tell the difference.
>>24
C's type conversion rules are already enough of a pain to remember without adding even more confusion. I never liked overloaded function arguments either, for this exact same reason.
>>36
There's the question of why you'd want an exponentiation operator in a systems programming language in the first place. Use FORTRAN for maths please.
Name:
Anonymous2009-08-27 3:32
I'd like to add the following:
1) A universal way to link libraries, i.e:
#inclib("libc");
2) Standard GUI , like allegro etc, but as a standard c library.
3) Standard Sound , sort of the same as the above.
4) Allocation function, like malloc, but that you can choose the virtual offset, like VirtualAlloc on windows.
Name:
Anonymous2009-08-27 3:35
>>38
OHHHH, also a Standard C Library for multi threading and chmod etc.