News for hackers. Stuff that matters.
Re:Deconstructing K&R C (2010) by informatimago on Sunday January 04, 2015 @07:32AM (#8834236)
This is so dumb.

   safercopy(42,a,33,b);
Just use lisp!
Re:Deconstructing K&R C (2010) by SixSigma on Sunday January 04, 2015 @08:25AM (#8834330)
How do I link LISP into my C project to do this safer copy you recommend ?
Re:Deconstructing K&R C (2010) by jwdunne on Sunday January 04, 2015 @09:26AM (#8834473)
First, you must build a half-baked version of Common Lisp in C.
Re:Deconstructing K&R C (2010) by PuercoPop on Sunday January 04, 2015 @06:10PM (#8836284)
You use ECL[0] o MKCL[1], but don't let snarkyness get in the way of reality.

[0]: http://ecls.sourceforge.net/

[1]: http://common-lisp.net/project/mkcl/

Re:Deconstructing K&R C (2010) by zedshaw on Sunday January 04, 2015 @11:48AM (#8834928)
People are downvoting you, but as the author of this I can say you're right. Not necessarily lisp, but using any language that doesn't have the fatal flaw of totally broken strings is better.

C is still a large historical influence on many languages, and knowing it makes people more capable as programmers. That's why I teach it, and I use it because I'm just old like that. Once someone knows C they can fix all kinds of problems, and then can learn a huge number of languages fairly easily.

But these days, without a solid reason for using it, I'd avoid C and use a better alternative.