RE: TK_mem problem and replacement
- Posted by Derek Parnell <Derek.Parnell at SYD.RABOBANK.COM> Jun 24, 2002
- 402 views
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C21BE5.8BB8CCC0 charset=iso-8859-1 Actually, now that I look again, I can see a bug in tk_mem. It treats Long, DWord, Ptr and UInt as the same. This is wrong because Long and DWord are a signed 32-bit and Ptr and UInt are unsigned 32-bit. I'll fix this immediately. --------------- Derek. ================================================================== De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en de afzender direct te informeren door het bericht te retourneren. ================================================================== The information contained in this message may be confidential and is intended to be exclusively for the addressee. Should you receive this message unintentionally, please do not use the contents herein and notify the sender immediately by return e-mail. ================================================================== ------_=_NextPart_000_01C21BE5.8BB8CCC0 Content-Type: application/ms-tnef