From: Puetz Kevin A <PuetzKevinA@JohnDeere.com>
Subject: RE: [PATCH] oleaut32: ITypeInfo_ReleaseFuncDesc_Proxy handle NULL parameter
Message-Id: <DM6PR05MB6858F49938285C4DB02DB802B53B0@DM6PR05MB6858.namprd05.prod.outlook.com>
Date: Tue, 22 Sep 2020 20:05:09 +0000
In-Reply-To: <30c52824-1fe2-01fa-c78d-375531219a13@codeweavers.com>
References: <PSXP216MB07926F4A35B64D02C594A66693520@PSXP216MB0792.KORP216.PROD.OUTLOOK.COM> <30c52824-1fe2-01fa-c78d-375531219a13@codeweavers.com>

> From: wine-devel <wine-devel-bounces@winehq.org> On Behalf Of Nikolay Sivov
> Sent: Wednesday, September 09, 2020 5:46 AM
> Subject: Re: [PATCH] oleaut32: ITypeInfo_ReleaseFuncDesc_Proxy handle NULL parameter
> 
> Is it possible to add a test for this? And ideally a bug reference too.

Agreed, this fix seems strange in isolation. Why only ReleaseFuncDesc
and not ReleaseVarDesc or ReleaseTypeAttr?
And why should the proxy tolerate NULL, but not direct (in-apartment) calls?

Not saying it's definitely  wrong, but it seems incomplete if freeing NULL is supposed to be OK.