Il est bete. C est magnifique pour les personnes qui savent qu'ils faisent. Utilisez le bon outil pour le bon travail. (Or something like that.)
http://www.mtl2600.org/forum/index.h...=1&mid=338
Very nice post. Has some good points.
Il est bete. C est magnifique pour les personnes qui savent qu'ils faisent. Utilisez le bon outil pour le bon travail. (Or something like that.)
C is a great, strong, classic language. It is a bit dated when trying to do certian programming, but it is one of the best tools to use when doing Computer Engineering because of it's structural programing techniques.
:![]()
Buffer overflows would never happen if people used the appropriate functions in C. I mean I know it's oh so difficult to put (usually) an extra letter in the function name (strcpy/strncpy) and specify the length of the array, but I'd say it's worth the extra 3 or more keystrokes.
Kenshi: Stop changing nicknames! The only way I can recognize you is from your picture.
C rules. If there was no C, there would be no Ruby, GnuVince.
Hey Greg, j'faisais yenque poster un lien moé, erlax!
Kenshi (or Tekii): more than 50% of the people don't know how to preoperly use C's functions. *Also, strn commands are a bit weird; for safer and simpler behavior, use strlcpy and strlcat.
Edit: Plus, you saw what we did in the Hacking challenge: buffer overflow exploit, tmp racing conditions exploit, etc. For a end-user application (payroll program, IRC clients, IM clients, etc.), I would probably use something that's safer without having to worry about it.
Just wait until I start changing pictures too.Kenshi: Stop changing nicknames! The only way I can recognize you is from your picture.
Yeah, but that was all due to poor programming. I still think that any programmer good enough to have his stuff used by others should be good enough to use C more wisely.Kenshi (or Tekii): more than 50% of the people don't know how to preoperly use C's functions. Also, strn commands are a bit weird; for safer and simpler behavior, use strlcpy and strlcat.
Edit: Plus, you saw what we did in the Hacking challenge: buffer overflow exploit, tmp racing conditions exploit, etc. For a end-user application (payroll program, IRC clients, IM clients, etc.), I would probably use something that's safer without having to worry about it.
GnuVince: le lien marchait pas avant...faque j'savais pas...mais la y marche.
Man I'm beat. I want to sleep.
Bookmarks