Hierarchical namespace for tests
Paul Millar
p.millar at physics.gla.ac.uk
Tue Apr 26 03:11:43 CDT 2005
On Monday 25 April 2005 16:18, Alexandre Julliard wrote:
> Paul Millar <p.millar at 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?
Paul.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20050426/30e741c0/attachment.pgp
More information about the wine-devel
mailing list