Alexandre Julliard wrote:
> Michael Stefaniuc <[EMAIL PROTECTED]> writes:
>
>> I therefor propose to standardize all the internal HeapAlloc wrappers to
>> a common name and form, Something along the lines of:
>> walloc()
>> wzalloc()
>> wrealloc()
>> wzrealloc()
>> wfree()
>> It's short and concis
Michael Stefaniuc <[EMAIL PROTECTED]> writes:
> I therefor propose to standardize all the internal HeapAlloc wrappers to
> a common name and form, Something along the lines of:
> walloc()
> wzalloc()
> wrealloc()
> wzrealloc()
> wfree()
> It's short and concise and doesn't conflict with the Win32
Hi,
> In Wine HeapAlloc gets wrapped in different places, each using a
> different name and even a different naming convention. This makes the
> code harder to understand for people that browse the code (people doing
> janitorial work) as they have to check every time if the function is yet
> anot
Hello!
(Jacek, this is not directed at you but a general rant).
HeapAlloc is an awful API and even its creators wrap it in a couple of
DLLs. In Wine HeapAlloc gets wrapped in different places, each using a
different name and even a different naming convention. This makes the
code harder to underst
