<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<p>Gentlemen,</p>
<p><br>
</p>
<p> *Years* ago I used to use yacc, but I quit before bison
became the _de-facto_ standard. Thus, upon reading its man page I
was surprised and pleased to see the following command-line
options available:<br>
<br>
--debug</p>
<p> --report=THINGS</p>
<p>THINGS comes from the set of 'state', 'itemset', 'lookahead',
'solved' (shift/reduce conflicts), or 'all' <br>
</p>
<p><br>
</p>
<p> Does any of this help?<br>
</p>
<p><br>
</p>
<p><br>
</p>
<p> - <font color="#000099"><b><font face="Brush Script MT"
size="+3">John D. Bell</font></b></font></p>
<br>
<br>
<div class="moz-cite-prefix">On 06/22/2018 02:24 PM, Eric S. Raymond
via devel wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20180622182454.GC30796@thyrsus.com">
<pre wrap="">Hal Murray <a class="moz-txt-link-rfc2396E" href="mailto:hmurray@megapathdsl.net"><hmurray@megapathdsl.net></a>:
</pre>
<blockquote type="cite">
<pre wrap="">
<a class="moz-txt-link-abbreviated" href="mailto:esr@thyrsus.com">esr@thyrsus.com</a> said:
</pre>
<blockquote type="cite">
<pre wrap="">If we had introspection in the target language we would automatically get the
entire parse structure when we dumped each syntax tree, rather than an ad-hoc
representation that's mostly leaf nodes. We would also get things like
dumping the composed filter blocks from multiple restrictions rather than
each partial specification.
</pre>
</blockquote>
<pre wrap="">
I'm not on the right wavelength.
Do you want to test the parser, or the restriction setup/lookup routines?
</pre>
</blockquote>
<pre wrap="">
My goal was a visualization of the control structures the rest of the daemon
sees - so, as far inside and as digested as possible (this is what the code
I deleted was aiming at, I think).
</pre>
<blockquote type="cite">
<pre wrap="">My proposal of "just" print out the info from the leaf node callout routines
only checks the parser. It's not hard to implement. If you were working in
that area, it would be reassuring that you hadn't broken anything.
</pre>
</blockquote>
<pre wrap="">
It...never actually occurred to me that we might be worried about the parsing
*itself.* Duh. Blind spot on my part, I guess I'm just too used to Yacc/Lex
parsers Just Working.
I think, though, that if we did the "deep" visualization we'd get a
check on almost all of the parser as a side effect. Restriction
blocks might be the only exception.
</pre>
</blockquote>
<br>
<div class="moz-signature"><br>
</div>
</body>
</html>