I wonder if find_recursionlimit.py shouldn't go in Tools and perhaps be run as a separate rule in the Makefile (with a corresponding cleanup of the inevitable core file, and a printing of the last reasonable value returned). Or you can write a simple Python wrapper around find_recursionlimit.py that did the parenthetical tasks.
-Barry
"BAW" == Barry A Warsaw bwarsaw@beopen.com writes:
BAW> I wonder if find_recursionlimit.py shouldn't go in Tools and BAW> perhaps be run as a separate rule in the Makefile (with a BAW> corresponding cleanup of the inevitable core file, and a BAW> printing of the last reasonable value returned). Or you can BAW> write a simple Python wrapper around find_recursionlimit.py BAW> that did the parenthetical tasks.
Perhaps. It did not imagine we would use the results to change the recursion limit at compile time or run time automatically. It seemed a bit hackish, so I put it in Misc. Maybe Tools would be better, but that would require an SF admin request (right?).
Jeremy
"JH" == Jeremy Hylton jeremy@beopen.com writes:
JH> Perhaps. It did not imagine we would use the results to JH> change the recursion limit at compile time or run time JH> automatically. It seemed a bit hackish, so I put it in Misc. JH> Maybe Tools would be better, but that would require an SF JH> admin request (right?).
Yes, to move the ,v file, but there hasn't been enough revision history to worry about it. Just check it in someplace in Tools and cvsrm it from Misc.
-
bwarsaw＠beopen.com -
Jeremy Hylton