Comments on: delicious! http://entland.homelinux.com/blog/2006/01/27/delicious/ Code, 3D, Games, Linux and much more... Fri, 12 Feb 2010 17:01:11 +0100 http://wordpress.org/?v=2.9 hourly 1 By: ent http://entland.homelinux.com/blog/2006/01/27/delicious/comment-page-1/#comment-19 ent Tue, 31 Jan 2006 09:52:19 +0000 http://entland.homelinux.com/blog/?p=48#comment-19 Paquete :-) Paquete :-)

]]> By: chanka http://entland.homelinux.com/blog/2006/01/27/delicious/comment-page-1/#comment-17 chanka Tue, 31 Jan 2006 09:16:09 +0000 http://entland.homelinux.com/blog/?p=48#comment-17 sorry, bad post commnet :D sorry, bad post commnet :D

]]> By: chanka http://entland.homelinux.com/blog/2006/01/27/delicious/comment-page-1/#comment-16 chanka Tue, 31 Jan 2006 09:14:48 +0000 http://entland.homelinux.com/blog/?p=48#comment-16 >> Use the IsBadWritePtr function against the pointers returned by the DirectX API and if you get a bad pointer return a pointer to a dummy memory block internally allocated by you. To me, this is the cleanest and safest option. You should return a memory block long enough to hold the size requested by the Lock. What if the pointer is invalid after the call to IsBadWritePtr? >> Use the IsBadWritePtr function against the pointers returned by the DirectX API and if you get a bad pointer return a pointer to a dummy memory block internally allocated by you. To me, this is the cleanest and safest option. You should return a memory block long enough to hold the size requested by the Lock.

What if the pointer is invalid after the call to IsBadWritePtr?

]]>