Re: dumpdef a pushdef'd stack
"Gary V. Vaughan" <[email protected]>
| Newsgroups | gmane.comp.gnu.m4.patches |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Eric, On 27 Sep 2006, at 14:20, Eric Blake wrote: > [[...]] now that --arglength can affect dumpdef output as well as > trace > output, we should be able to tweak it on the fly. I'm thinking a > macro > named debuglen is the best fit here (fitting in with the naming of > other > debug* builtins), but I could also be persuaded to name the macro > arglength to match the command-line option. Or maybe name it > debuglen, > deprecate --arglength (as that name isn't quite descriptive of what is > really being length-limited), and introduce --debuglen as a synonym > to -l. > Thoughts? I think the latter is more in keeping with my notional 2.0 theme of clean and complete integration between command line options and run time control of the same. Cheers, Gary - -- Gary V. Vaughan ())_. [email protected] Research Scientist ( '/ http://blog.azazil.net GNU Hacker / )= http://www.gnu.org/software/{libtool,m4} Technical Author `(_~)_ http://sources.redhat.com/autobook -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFJL2gFRMICSmD1gYRApr8AKC7+fo4qSYqqXKFE0s16BO8y1YJsACeNStz iiNzUHKC2SZV1bOwMYGMAUs= =QCOu -----END PGP SIGNATURE-----