🚀 go-pugleaf

Hans Galema wrote:
> So we spoke about different code and did a different test.

Sorry. I changed the code because I realized after I posted my first code 
chunk that I had made an error. Because when only 1 byte was left in the 
socket buffer, 1 / 2 = 0 in a integer, so it was being told to read 0 
bytes. So that is why I changed it.

However, it didn't hang the app, nor show any signes of problems when only 
half-reading available bytes.

Jonathan

"Hans Galema" <notused@notused.nl> wrote in message
news:4367395a@newsgroups.borland.com...

> Well I have to. But you did not know why

As I said before, the Size property already checks the capacity of the
currently allocated Memory and then reallocates the Memory only when
actually needed.  TMemoryStream has a Capacity property tha indicates the
size of the allocated memory.  That is different than the Size property,
which specifies the number of bytes that are available in the allocated
Memory.  Setting the Size also sets the Capacity, which may be more than the
Size.

> I never size the stream down.

If you don't do that, then the stream will slowly continue allocating more
and more memory until it runs out.  You should reduce the Size periodically
to reduce the amount of unused memory.


Gambit

"Hans Galema" <notused@notused.nl> wrote in message
news:436739a0@newsgroups.borland.com...

> Where is the AnsiString ?

In Alfred example code:

    Memo->Lines->Add(AnsiString((char*)Data, DataLength));

DataLength ensures that all characters are handled without having to
transmit a null terminator over the socket, and AnsiString always has a null
terminator at the end of its allocated memory (otherwise the char* string
from c_str() would never be terminated).


Gambit