🚀 go-pugleaf

"Eric Patterson" <eric.patterson@bepco.com> wrote in message
news:44490de6$1@newsgroups.borland.com...

> The exception occured on the line using SubString function (denoted
> with an arrorw).  I looked at the details of the SubString method and
> in this case it will return a substring starting at len+1 and go all the
way to MaxInt.

Using MaxInt does not tell SubString() to return a new string that is MaxInt
in length.  The count parameter is truncated to the minimum value between
the specified value and the source string's actual length before the new
string is then allocated.  Using MaxInt is a common way to tell SubString()
to return everything that is remaining in the source string after the
specified position.  But, if it concerns you, you can calculate the
remaining length manually:

    temp = temp.SubString(len+1, temp.Length()-len);

> when using an equal operator is that doing a copy from one memory
> location to another or is that just creating another pointer to point to
> the same location AMsg is sitting?

The latter.  AnsiString is reference-counted.  When one AnsiString is
assigned to another, they share the same memory for the character data, and
a reference count within that memory is incremented.  When an AnsiString is
freed or modified, the reference count on the existing memory is
decremented.  AnsiString copies the characters to a new memory block only
when the string is being modified.

> Maybe my AMsg array is being taken way before sendbuf (or sendtext)
> is done with it.

Nope.  SendText/Buf() copies the specified data into the socket's internal
buffer.  What happens to your data when the call exits is irrelevant.
Besides, you are appending a '\n' character to the end of the AMsg data, so
it doesn't matter what happens to AMsg because your sending is working with
a local AnsiString that has its own memory separate from AMsg.


Gambit