On Sun, Nov 29, 2009 at 2:24 PM, Dan Kegel wrote:
> On Sun, Nov 29, 2009 at 12:10 AM, Laurent wrote:
>> Yes, it would be. The fact is that makes a zero byte size HeapAlloc.
>> I'm not really sure how and why it is supposed to work in this case,
>
> It works fine, HeapReAlloc handles it ok, too.
>
On Sun, Nov 29, 2009 at 12:10 AM, Laurent wrote:
> Yes, it would be. The fact is that makes a zero byte size HeapAlloc.
> I'm not really sure how and why it is supposed to work in this case,
It works fine, HeapReAlloc handles it ok, too.
On Windows, it actually returns a heap block.
(On Posix, it
Laurent wrote:
On Sun, Nov 29, 2009 at 2:32 AM, Dan Kegel wrote:
On Sat, Nov 28, 2009 at 5:04 PM, Laurent Vromman wrote:
-pStrokes = HeapAlloc(GetProcessHeap(), 0, numStrokes *
sizeof(GdiPath*));
-pStrokes[0] = HeapAlloc(GetProcessHeap(), 0, sizeof(GdiPath));
-PATH_InitGdi
On Sun, Nov 29, 2009 at 2:32 AM, Dan Kegel wrote:
> On Sat, Nov 28, 2009 at 5:04 PM, Laurent Vromman wrote:
>> - pStrokes = HeapAlloc(GetProcessHeap(), 0, numStrokes *
>> sizeof(GdiPath*));
>> - pStrokes[0] = HeapAlloc(GetProcessHeap(), 0, sizeof(GdiPath));
>> - PATH_InitGdiPath(pStrokes
On Sat, Nov 28, 2009 at 5:04 PM, Laurent Vromman wrote:
> - pStrokes = HeapAlloc(GetProcessHeap(), 0, numStrokes *
> sizeof(GdiPath*));
> - pStrokes[0] = HeapAlloc(GetProcessHeap(), 0, sizeof(GdiPath));
> - PATH_InitGdiPath(pStrokes[0]);
> - pStrokes[0]->pFlags = HeapAlloc(GetProcessHe
