🚀 go-pugleaf

Forget this for a minute because I need to fix the issue with not waiting 
for CleintWrite event after a WSAEWOULDBLOCK

Eric

"Eric Patterson" <eric.patterson@bepco.com> wrote in message 
news:44490de6$1@newsgroups.borland.com...
>I seem to still have an invalid pointer.  I was using this snippet:
>
> TCustomWinSocket *Socket =
> Server->ServerSocket1->Socket->Connections[ii];
>    AnsiString temp = AMsg + "\n";
>    int len;
>
>    while( temp.Length() > 0 )
>    {
>        len = Socket->SendText(temp);
>        if( len > 0 )
>        {
> -->       temp = temp.SubString(len+1, MaxInt);
>            continue;
>        }
>
>        if( (len == -1) && (WSAGetLastError() == WSAEWOULDBLOCK) )
>        {
>            Sleep(10);
>            continue;
>        }
>
>        break;
>    }
>
> 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. I am going to attempt using the sendbuf example that you provided 
> since that makes more sense and I can control the bounds of the pointers. 
> I do have a question regarding AnsiStrings now though: 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? Maybe my AMsg array is being taken way before sendbuf (or 
> sendtext) is done with it.
>
> Eric
>
>
> "Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
> news:44480aa5$1@newsgroups.borland.com...
>>
>> "Eric Patterson" <eric.patterson@bepco.com> wrote in message
>> news:4447c0b0$1@newsgroups.borland.com...
>>
>>> That is all fine but why?
>>
>> I already gave you a detailed explanation about that.  Please go re-read 
>> my
>> earlier reply more closely.
>>
>>> I would love to fix my issue
>>
>> Then please try the code I already gave you.
>>
>>
>> Gambit
>>
>>
>
>