<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"><br>
On 12/03/2012 02:37 PM, Barry Warsaw wrote:<br>
</div>
<blockquote cite="mid:20121203173713.40ec5af2@resist.wooz.org"
type="cite">
<pre wrap="">The biggest question with generated code is always the effect on debugging.
How horrible will it be when I have to step through argument parsing to figure
out what's going wrong?
</pre>
</blockquote>
<br>
Right now, it's exactly like the existing solution. The generated
function looks more or less like the top paragraph of the old code
did; it declares variables, with defaults where appropriate, it
calls PyArg_ParseMumbleMumble, if that fails it returns NULL, and
otherwise it calls the impl function. There *was* an example of
generated code in my original email; I encourage you to go back and
take a look. For more you can look at the bitbucket repo; the
output of the DSL is checked in there, as would be policy if we went
with Clinic.<br>
<br>
TBH I think debuggability is one of the strengths of this approach.
Unlike C macros, here all the code is laid out in front of you,
formatted for easy reading. And it's not terribly complicated code.<br>
<br>
If we change the argument parsing code to use some new API, one
hopes we will have the wisdom to make it <i>easier</i> to read than
PyArg_*.<br>
<br>
<br>
<i>/arry</i><br>
</body>
</html>