Re: Two dimensional array Question

On May 11, 8:16 pm, Richard Heathfield <r...@[EMAIL PROTECTED]
> wrote:
>
> Writing code "to figure things out" is a two-edged sword. It can
certainly
> be helpful for discovering how things *appear* to work, but it is a poor
> guide for discovering how things *must* work.


Point made and taken...thanks.


> > char arr [3][3] = {"One", "Two", "Lst"};
>
> Legal, but dangerous. Don't treat these arrays of char as if they were
> strings. They aren't.

OK..now let me show my total ignorance.

So,  can multidim char arrays ever be treated as strings and would
this then be the correct intialization? char arr[] [] = "one, two";
And, for a regular (one dim) char array,  would this be a string
intialization?  char arr[]= "something" or the use of strcpy?

And, somewhat philosophically, a (one dim)  char array is simply a
contiguous set of bytes. If one ? *knows* the array is NULL
terminated, then we can safely treat it as a string. But the *only*
way to know this is if it is correctly initialized in the first place.
Is this a fair way of looking at it?



> > p=&arr[i][j];
> > printf( "%p\n", p);
>
> Although the representations of char * and void * are required to be the
> same, it is generally wiser to insist on void * for %p:
>
>   printf("%p\n", (void *)p);

I did read today about the need for a pointer to be cast to
void ...but is there a reason for this? Other than the language says
it should be so.


>
> You fell into the trap.

Yup!

> The easiest way to comprehend multidimensional arrays is to think of
them
> as arrays of arrays. If you never try to breach the bounds of an object,
> all will be well. By treating arrays-of-arrays as if they were a single
> contiguous object (EVEN IF THAT IS TRUE), you're violating that
principle

Yes..I like it...thanks.