Funny... always these problems with C and bounds checkings
http://www.theregister.co.uk/2009/05/15/microsoft_banishes_memcpy/
Mailing lists / fpc-pascal / 2009-05
Microsoft to ban Memcpy() :)
4 messages · 4 people ·
- ABorka 1
- Florian Klaempfl 1
- Jonas Maebe 1
- Marco van de Voort 1
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
ABorka wroteFunny... always these problems with C and bounds checkings
Please use the fpc-other list for remarks like this.
Jonas
FPC mailing lists admin
Funny... always these problems with C and bounds checkings…
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.
In our previous episode, Florian Klaempfl said:
Show quoted text 8 lines
> 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.
Why, do you want FPC to be certified? :-)