Paul Millar p.millar@physics.gla.ac.uk writes:
Hopefully not a controversial one. I think it will prove useful to separate the different tests' namespace. This would allow identical filenames to appear in different DLL tests directories without confusion (c.f. "generated.c" currently).
The proposed namespace would be simply <dllname> "/" <filename> ":" <lineno> Examples are: user/sysparams:186 winspool/info:128
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.
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?
Paul.
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.
-
Alexandre Julliard -
Ferenc Wagner -
Paul Millar