🚀 go-pugleaf

Maurice Anderson wrote:

>> Bob Gonder wrote:
>> Look carefully at that:
>> MS:   string IPAddress[]
>> You:  String IPAddress1[2]
>
>Answer - I believe the "s" is the equivalent of "S" in BCB for a string data
>type, so as far as I know, there is no difference.

I can't confirm that, as I have never been able to find where string
is defined in any of the headers.  There is just the general belief
that when things don't work right, you should use what the headers say
to use. In this case, that's "string" not "String".
I am also thinking that "string" is supposed to be a C thing that is
essentially char*, whereas "String" is a C++ thing with functions and
sizes and stuff.


>> I would also think that  IPAddress1[1] should be emptied.
>Answer - Why?? In either case, I shouldn't get the compiler error.

Well, if you are just passing an array, how is the guy that gets that
array supposed to know how many elements are in it? There are 2 ways
this is usually handled: 1) pass the number of elements (not done in
this case) and 2) have an extra null at the end.


>> Example: "192.168.12.1 192.168.46.1"
>Are you saying the code should read like this:
>  ret_code =  (Variant(NetAdapter)).Exec(Function("EnableStatic") <<
>       "192.168.12.1 192.168.46.1", "255.255.255.0 255.255.255.0");

Well, that's what the MS docs imply: that string is nothing more than
typedef char*string
and that string [] is just concatinated values with blank seperation
and terminating 0.