1> Yes thats correct. My bad sorry.
BTW the ARRANGEMENT of the three '*' is pretty immaterial. These four all work the same.
"STRING*** myString;", "STRING* **myString;", "STRING** *myString;", and "STRING ***myString;".
So find a format that suits you. I use the "* **" format so I know that the
right-hand "*" is number of dimensions, and the optional left hand ones are
required by EACH of the objects that the array will be 'built' of.
ie: "STRING* **myString;" means create a two(**) dimensional array which contains
an array built of "STRING*" objects.
But what works for me might not suit you... So go with what works for you.


2> Im not actually sure WHAT yours would have done. But I SUSPECT it would have
made a 5x5 array of dynamically-sized string arrays.

FYI:: This is what Ive been TOLD about the brackets from multiple reliable sources.

In STANDARD-C, fixed-sized multi-dimesnional arrays can be accessed via
the 'arr[x][y]' syntax, whereas dynamic arrays must use the '( arr[x] ) [y]' syntax.
Lite-C does the same in order to remain as Standard-C compatible as possible.

But Ive never used dynamic arrays in anything other than lite-c, so
Ive never experienced the issue in standard-C. So I take it on faith...

I've come to the conclusion that this is because fixed-size multi-dimensional
arrays are 'known' to the compiler, and so the compiler then knows how to
reference the 'arr[x][y]' to the data-table that IT created itself.

Whereas with the dynamic arrays, the compiler doesnt know in which order you
have/will create the indexs, so it doesnt know whether to treat the X or the Y
as the 'primary' index. So it then needs the brackets to determine the 'order'
of processing the lookups. Start creating arrays with more than two dimensions
and things start getting even more tricky if there was NO brackets...
This way, the deepest dimension within the brackets get processed first, of course.


But be aware, my conclusion is based on some knowledge, some faith, quite
a few assumptions and a little guesswork.... In that order.
And if I am wrong its 'not important' because it has NO impact on coding techniques.

I would like to know 'the truth' of course, but I dont NEED to...

I hope this explaination of my 'belief' is of some help to you...