Interesting C code
a1k0n.net
Interesting C code
1–10 of 31 posts
Re: Interesting C code
#2Re: Interesting C code
#3I'm not impressed. It could be done in 1 line of C when he left out the line-breaks.
I don't think obfuscated code is interesting. It's unreadable. And therefore it's hard to learn something from it.
But it's nice he is explaining the code. Now that is interesting!
Re: Interesting C code
#4Re: Interesting C code
#5"in six lines of C" I'm not impressed. It could be done in 1 line of C when he left out the line-breaks. I don't think obfuscated code is interesting. It's unreadable. And therefore it's hard to learn something from it. But it's nice he is explaining the code. Now that is interesting!
Re: Interesting C code
#6'warnings which real programmers ignore' ... That tells me pretty much all I needed to know about that article.
Re: Interesting C code
#7'warnings which real programmers ignore' ... That tells me pretty much all I needed to know about that article.
$ gcc -o yanim yanim.c -lm
yanim.c:1:1: warning: data definition has no type or storage class [enabled by default]
yanim.c: In function ‘main’:
yanim.c:5:24: warning: incompatible implicit declaration of built-in function ‘cos’ [enabled by default]
yanim.c:5:33: warning: incompatible implicit declaration of built-in function ‘sin’ [enabled by default]Re: Interesting C code
#8"in six lines of C" I'm not impressed. It could be done in 1 line of C when he left out the line-breaks. I don't think obfuscated code is interesting. It's unreadable. And therefore it's hard to learn something from it. But it's nice he is explaining the code. Now that is interesting!
Re: Interesting C code
#9'warnings which real programmers ignore' ... That tells me pretty much all I needed to know about that article.
Re: Interesting C code
#10"in six lines of C" I'm not impressed. It could be done in 1 line of C when he left out the line-breaks. I don't think obfuscated code is interesting. It's unreadable. And therefore it's hard to learn something from it. But it's nice he is explaining the code. Now that is interesting!
I assume the line-breaks are to allow the code to fit within 80 columns to display on most standard terminals. If you look closely, they occur at places you wouldn't expect them to. I'm guessing they were placed by cat and not the author.