News for hackers. Stuff that matters.
Re:My Code made it to a Hollywood Movie by ars on Sunday December 08, 2013 @06:21PM (#6871959)
> The file ends in `.c`, but the return type of `malloc` is cast to different pointer types

I was taught this way, and lint used to complain if I didn't. Just because it's legal not to cast doesn't also mean it's bad to cast.

Re:My Code made it to a Hollywood Movie by asveikau on Sunday December 08, 2013 @06:35PM (#6872022)
And just because a tool tells you to do it ... I'll let you fill in the rest.
Re:My Code made it to a Hollywood Movie by Dylan16807 on Sunday December 08, 2013 @07:05PM (#6872149)
...you make the intent clear?
Re:My Code made it to a Hollywood Movie by asveikau on Sunday December 08, 2013 @07:15PM (#6872193)
I get the impression from some of these responses that you folks would prefer:

    struct foo *bar = (struct foo*)malloc(sizeof(struct foo));
Over:

    struct foo *bar = malloc(sizeof(*bar));
I suppose the former is more clear by somebody's definition but I am going to continue to consider it somewhat ridiculous.
Re:My Code made it to a Hollywood Movie by mhogomchungu on Sunday December 08, 2013 @08:12PM (#6872364)
I do something like this:

    char * buffer = ( char * )malloc( sizeof( char ) * 32 ) ;
Why? because i like to look at my code written that way.

If i code for somebody else's preference,i do it their way,if i code for my own consumption,i code it the way it pleases me.