<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Le 24/02/2013 07:07, Max TenEyck
Woodbury a écrit :<br>
</div>
<blockquote cite="mid:5129AE3B.2090803@mtew.isa-geek.net"
type="cite">On 02/23/2013 02:54 AM, Eric Pouech wrote:
<br>
<blockquote type="cite">Le 21/02/2013 14:33, Max TenEyck Woodbury
a écrit :
<br>
<blockquote type="cite">Would it be appropriate to add a test to
the name demangler that:
<br>
<br>
1) Scans all '.dll' and '.spec' files for mangled names, and
<br>
<br>
2) Tries to decode those names.
<br>
<br>
3) Prints the mangled and decoded names and where they occur.
<br>
<br>
Success would be that all names decode without the decoder
blowing up
<br>
or failing.
<br>
<br>
<br>
<br>
</blockquote>
adding tests for demangler is good
<br>
but you just need to have a set of mangled/unmangled strings for
the test
<br>
as core demangler in msvcrt, test should be added here...
<br>
(but grabbing the mangled strings shall be left out of the test
itself)
<br>
A+
<br>
<br>
</blockquote>
One of the important aspects of name demangling is that it should
work
<br>
on _all_ the names in the current system. The current test does
<br>
demangle a list of known strings, but that list was incomplete
with
<br>
respect to all the features used in real names the last time I dug
into
<br>
the details (which was none too recently).
<br>
<br>
Scanning for all the real mangled names not only makes sure that
the
<br>
demangler is working properly, it also assures that all the names
used
<br>
are properly formed and decode to their intended values.
<br>
<br>
<br>
<br>
</blockquote>
<font face="Helvetica, Arial, sans-serif">I'm just saying that the
test shouldn't embed the way to grab the mangled names<br>
it should be made outside of the test<br>
A+<br>
</font>
</body>
</html>