<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div> In the --help mode you print all valid options, thus you can generate this list of all valid options. So at the conclusion of the run you could just take all the user provide options and make sure they are in that list?<div><br></div><div> Barry</div><div><br><div><div>On Sep 1, 2010, at 6:56 AM, Matthew Knepley wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Wed, Sep 1, 2010 at 12:55 PM, Jed Brown <span dir="ltr"><<a href="mailto:jed@59a2.org">jed@59a2.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Two thoughts:<br>
<br>
1. Systematic deprecation system:<br>
<br>
--with-shared doesn't give any errors today, but the option goes<br>
unused (because it's now spelled --with-shared-libraries). I'd like<br>
to see either (a) recognize the old spelling but warn of deprecation,<br>
or (b) error giving the new spelling. This seems easy to do by<br>
updating help.addArgument.<br></blockquote><div><br></div><div>Good idea. Will do it.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
2. It's common to misspell options, difflib is part of the standard library<br>
(from 2.3)<br>
<br>
<a href="http://docs.python.org/library/difflib.html#difflib.get_close_matches" target="_blank">http://docs.python.org/library/difflib.html#difflib.get_close_matches</a><br>
<br>
and would enable a warning like<br>
<br>
The option "--with-shard-libaries" was not used, maybe you meant "--with-shared-libraries".<br>
<br>
Configure is imperative (as opposed to declarative, or with all<br>
options identified and available very early) so I don't think it's<br>
feasible to provide comprehensive misspelled options help immediately,<br>
but at least the unused options could be listed at the end. This<br>
ought to just be a matter of having argDB log accesses, then at the<br>
end, take all entries that were never accessed and compute Levenshtein<br>
distance to the options that were accessed used to give suggestions.<br></blockquote><div><br></div><div>The first part, putting in access logging, has been on the list for a long time.</div><div>We need to do it, but its a bit of programming.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I'm not sure what to do if configure errors out early, it might be<br>
hitting an error _because_ of an unused option, but there may be lots<br>
of unused options at this stage (that are valid and really will be<br>
used later).</blockquote><div><br></div><div>This is not really soluble now I think.</div><div><br></div><div> Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font color="#888888"><br>
Jed<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener<br>
</blockquote></div><br></div></body></html>