On Tue, Jan 15, 2013 at 9:15 PM, Damjan Jovanovic wrote:
> On Tue, Jan 15, 2013 at 9:06 PM, André Hentschel wrote:
>> Am 15.01.2013 18:51, schrieb Damjan Jovanovic:
>>> Hi
>>>
>>> I've hacked together a simple tool for analyzing Wine code. Currently
>>> it can do the following:
>>> 1. Find BOOL f
On Tue, Jan 15, 2013 at 9:06 PM, André Hentschel wrote:
> Am 15.01.2013 18:51, schrieb Damjan Jovanovic:
>> Hi
>>
>> I've hacked together a simple tool for analyzing Wine code. Currently
>> it can do the following:
>> 1. Find BOOL functions returning non-BOOL.
>> 2. Find HRESULT functions returnin
Am 15.01.2013 18:51, schrieb Damjan Jovanovic:
> Hi
>
> I've hacked together a simple tool for analyzing Wine code. Currently
> it can do the following:
> 1. Find BOOL functions returning non-BOOL.
> 2. Find HRESULT functions returning non-HRESULTs.
> 3. Generate a TRACE() for each function showin
Damjan Jovanovic writes:
> I'd like to add the following features at some stage:
> * Populate all functions with a TRACE() of their arguments, if they
> don't already have it.
Please don't do that. There are many functions that we don't need to
trace, or that already have traces in sub-functions
