C IS SHIT

REASONS FOR WHY C IS SHIT

1)

int ANUS = 5/0; //VALID CODE; PROGRAM WILL CONTINUE TO RUN WHILE SOMETHING SOMEWHERE IN MEMORY GETS UTTERLY FUCKED

2)

struct anus *new_anus(...)
...
struct anus *FAGGOT = anus_new(...);//VALID CODE: WILL PRODUCE WARNING

3)C LEAKS WORST THAN GC WHEN USED WRONG

//IF YOU MALLOC THEN YOU NEED FREE FAGGOT
MALLOC(...);
FREE(...);

4) FROZENVOID

5)HORRID API
MAKEAWINDOW(NULL,NULL,NULL,NULL,800,600,NULL,NULL,NULL,NULL,NULL);

6)

INT *P = MALLOC(SIZEOF(INT));
PRINTF("SUCK MY %d",P);//VALID CODE, ENJOY YOUR WRONG PRINTED VALUE, SAME GOES FOR A LOT OF MISMATCHED TYPES

7)

STRUCT ANUS{
  CHAR FAG;
};
INT *P;
STRUCT ANUS *FAG = MALLOC(SIZEOF(INT));
P = (INT *)((VOID *)FAG)); //VALID CODE, NO ERROR AT RUNTIME. ENJOY YOUR MEMORY FAIL

AND THE LIST GOES ON

0/1000, not even trying

4) FRONZENVOID

only valid comment in that whole post

The reason that make C suck also make it great (for those particular low-level purposes).

1) Wrong; it generates a SIGFPE, but does not cause 'something somewhere in memory [to get] utterly fucked'
2) I have no idea what you're talking about here. There are multiple errors, including a missing semicolon and the use of unmatched identifiers, new_anus and anus_new.
3) Exactly, 'when used wrong'. This does not degrade C itself.
4) This does not degrade C itself.
5) Looks like some library (WinAPI?). This does not degrade C itself, as it is not part of the C stdlib API.
6) Programmer deficiency; this does not degrade C itself.
7) Programmer deficiency; this does not degrade C itself.

1/10 for making me reply.

>>5
GC WHEN USED RIGHT IS GOOD, BUT THAT DOESNT MEAN GC ISNT SHIT

>>5
5) Looks like some library (WinAPI?). This does not degrade C itself, as it is not part of the C stdlib API.