UnmanagedImage.Create could have option not to zero unmanaged memory

[Google Code Exporter]

UnmanagedImage.Create allocates fresh unmanaged memory for the image, and sets 
it to zero before returning to the caller.

This is good default behavior, but optionally, it's a step that can be avoided 
in many algorithms (in particular, those that immediately fill up the new image 
with fresh data before ever reading from it).

The patch I've attached simply adds an overload with a zeroMemory boolean 
parameter. A more thorough patch would go through the whole library to check 
for cases where UnmanagedImage.Create can be safely called with 
zeroMemory=false.

Original issue reported on code.google.com by ncruces on 25 Nov 2013 at 4:25

Attachments:

• zeroMemory.patch