[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re: Hierarchical namespace for tests
From:       Ferenc Wagner <wferi () tba ! elte ! hu>
Date:       2005-04-27 8:24:36
Message-ID: 3o64y8fwzf.fsf () tba ! elte ! hu
[Download RAW message or body]

Paul Millar <p.millar@physics.gla.ac.uk> writes:

> On Monday 25 April 2005 16:18, Alexandre Julliard wrote:
>
>> Paul Millar <p.millar@physics.gla.ac.uk> writes:
>>
>>> Hopefully not a controversial one [...]
>>
>> The problem with this is that the result is not a valid path, which
>> breaks tools that parse the output to let you jump to the error,
>> like emacs compile mode.
>
> OK, I didn't realise people were automatically passing these strings.
>
> In principle, one can reconstruct the path from the test-name by 
> sticking "dlls" and "tests" in the right places.
>
> Presumably emacs (or whatever) can be taught these tricks, so one 
> could display the tests as "ole32%moniker.c:123" (just to avoid the 
> "/" character) and have emacs link to 
> "dlls/ole32/tests/moniker.c:123"
>
> Alternatively, we can store the full path and have the test name-space 
> coincident with the filesystem, which is the simplest but (slightly 
> wasteful) solution.
>
> What would people prefer?

I'd prefer you don't break tools/winetest/dissect, which
matches on the closing line. :)  The change is trivial but
essential for the winetest web summaries.
-- 
Thanks,
Feri.

[prev in list] [next in list] [prev in thread] [next in thread]