Re: [PATCH] d3dx9: Correctly handle NULL constant state for objects on 64 bit arch.

[Matteo Bruni]

On Wed, Oct 30, 2019 at 11:22 AM Paul Gofman  wrote:
> On 10/30/19 13:04, Matteo Bruni wrote:
> > I had a sentence mentioning that idea at some point in the draft. I
> > guess that's preferable if it doesn't turn too ugly.
>
> I will do that, hope it will not be ugly. It just pulls another thing: I
> am probably supposed to use heap_alloc() / heap_free() now in the new
> code, but to do so all the existing allocations should be swithced to
> that first. I think I will have to do that first. Or do you think maybe
> it does not worth touching the whole d3dx9 code for that purpose now,
> and just use one more HeapReAlloc()? Or is it considered acceptable to
> mix helper and direct WINAPI allocations / frees?

I'm fine with mixing for the time being.