ABorka schrieb: > Funny... always these problems with C and bounds checkings > > http://www.theregister.co.uk/2009/05/15/microsoft_banishes_memcpy/
I'll continue here because my remark is fpc related :) Maybe we should add something like move_s (taking the destination size as well as the memcpy_s recommend by MS does) in fpc as well though I can rarely remember bugs where move overwrote destination memory. _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
