Comments for Real Time Software Rendering http://code.dawnofthegeeks.com Doing Things the Hard Way Sun, 14 Mar 2010 01:26:28 +0000 http://wordpress.org/?v=2.7.1 hourly 1 Comment on FYI: New Vs Malloc by Seth Morris http://code.dawnofthegeeks.com/2009/05/04/fyi-new-vs-malloc/comment-page-1/#comment-53 Seth Morris Sun, 05 Jul 2009 23:13:59 +0000 http://code.dawnofthegeeks.com/?p=52#comment-53 I the performance difference is vital to your code, then you probably need to look at the design anyway. New and delete can be overridden on a more granular level than malloc and free and mixing the two (new/delete for for objects, malloc/free for intrinsic types) makes for hard-to-maintain code. In most code you'd rather wrap intrinsic allocations in "smart"(ish) objects anyway so they can be deleted if an exception is thrown (malloc'd memory won't) and you don't have to remember to add a free to every return statement if you use multiple returns. Most Win32 code, even server-side, spends most of its time waiting on users, IO completion, etc., and every code I've seen that had a serious problem with allocation performance was better solved by managing heaps, getting allocations out of loops, moving to stack-based intrinsics, etc. Having said that, I *do* like alloca(), which cleans itself up because it just opens some stack space. I the performance difference is vital to your code, then you probably need to look at the design anyway. New and delete can be overridden on a more granular level than malloc and free and mixing the two (new/delete for for objects, malloc/free for intrinsic types) makes for hard-to-maintain code.

In most code you’d rather wrap intrinsic allocations in “smart”(ish) objects anyway so they can be deleted if an exception is thrown (malloc’d memory won’t) and you don’t have to remember to add a free to every return statement if you use multiple returns.

Most Win32 code, even server-side, spends most of its time waiting on users, IO completion, etc., and every code I’ve seen that had a serious problem with allocation performance was better solved by managing heaps, getting allocations out of loops, moving to stack-based intrinsics, etc.

Having said that, I *do* like alloca(), which cleans itself up because it just opens some stack space.

]]> Comment on About by Java Lesson 1: Initializing the screen and creating some static « Real Time Software Rendering http://code.dawnofthegeeks.com/about/comment-page-1/#comment-2 Java Lesson 1: Initializing the screen and creating some static « Real Time Software Rendering Wed, 06 May 2009 21:45:15 +0000 http://code.dawnofthegeeks.com/?page_id=2#comment-2 [...] About [...] [...] About [...]

]]>