Christopher Carver wrote: > I think I'm straight forward and I find to many cooks in the kitchen > arguing what to call s spoon, that they forget to make the soup. Call it > half a dozen or six and it's the same thing. > > For the original poster, strings in C and strings in C++ can be > different depending on who and what train of thinking they have and what > context the two are talking about. But basically it's nothing more than > a series of bytes with a terminating character at the end. That's not > 100% true all the time, but usually the case.
Wrong. I don't use null-terminators for in-memory data storage. I haven't done that for almost a decade (since 1998). Using a special character to signify the end of a chunk of data was and still is one of the worst ideas _ever_. That alone has caused WAY more problems (buffer overflows, etc.) than I care to count. > In context to the question initially posted a string, character array, > buffer, etc. etc. all mean the same thing, they just different ways to > get to the same thing. There are those that would like to polish their > word smithing and say otherwise. > > If you are serious about learning about pointers then I suggest a book > called Understanding Pointers in C by Yashavant P. Kanetkar. Though it > might be a hard book to find. I picked it up when I was in India. > > -- Chris Yashavant Kanetkar may have an easy-to-understand style of writing, BUT he is a non-ANSI Standard author. If you watch this list, you'll notice the following bit of canned response show up when I reply to a "I'm looking for a good book" question: ----- Beware any C/C++ author who does not adhere closely to the ANSI C/C++ Standard. One very popular author is Yashavant Kanetkar who is the author of "Let Us C". His writing may be simple to understand however his code is non-ANSI Standard. Similar great writers have shown up over the years who tell wonderful stories but don't adhere to the Standards defined by the ANSI C/C++ committees. ----- I've personally contacted Yashavant and he pretty much flat out refused to look at the ANSI C/C++ Standard - the document on which all compliant compilers AND book authors rely - to author his books in compliance of. His books may be easy to read but he is definitely an author to avoid. The other major author to avoid like the plague is Schildt. Unfortunately, the latter hasn't done _nearly_ as much damage as Yashavant has - and Yashavant is a relatively recent author. Please do not recommend either author. c-prog doesn't enjoy doing damage control. -- Thomas Hruska CubicleSoft President Ph: 517-803-4197 *NEW* MyTaskFocus 1.1 Get on task. Stay on task. http://www.CubicleSoft.com/MyTaskFocus/
