News for hackers. Stuff that matters.
Re:Deconstructing "K&R C" by bonzoesc on Wednesday January 11, 2012 @03:39PM (#3453570)
How do you test that something in C is a string?
Re:Deconstructing "K&R C" by tedunangst on Wednesday January 11, 2012 @04:26PM (#3453772)
You don't, because you can't. That's basically the same as the beginner question, "How can you test if a pointer has been freed?"
Re:Deconstructing "K&R C" by bonzoesc on Wednesday January 11, 2012 @05:20PM (#3453970)
It was a rhetorical question. What's the sense in having functions that operate on "strings" if you can't figure out what a "string" is at runtime? It's much saner to have functions operate on "strings that are 80 characters or less" or "a structure containing a integer `length` and an array of `length` chars."
Re:Deconstructing "K&R C" by ori_b on Wednesday January 11, 2012 @09:58PM (#3454847)
What's the sense in having functions that operate on "pointers to valid memory" if you can't figure out if it's "valid memory" at runtime?

The point is that the function is not buggy. You may not like the specification for it. You may think it should be designed differently. This is not the same as the code being buggy.

Re:Deconstructing "K&R C" by ori_b on Wednesday January 11, 2012 @09:54PM (#3454840)
The same way you test that a pointer is intialized to a valid value. You don't.