<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 6, 2014 at 3:16 PM, Bill Schottstaedt <span dir="ltr"><<a href="mailto:bil@ccrma.stanford.edu" target="_blank">bil@ccrma.stanford.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Do you mean why they started to give<br>
>these warnings in the first place?<br>
<br>
</span>yes -- after googling around for awhile, I think this was introduced<br>
in guile 2.0, and is not universally popular -- for example gnucash:<br>
<br>
;; Turn off the scheme compiler's "possibly unbound variable" warnings.<br>
;; In guile 2.0 we get nearly 7500 of them loading the scheme files.<br>
;; This is the default value for auto-compilation-options without "unbound-variable".<br>
(if (>= (string->number (major-version)) 2)<br>
(set! %auto-compilation-options<br>
'(#:warnings (arity-mismatch format duplicate-case-datum bad-case-datum))))<br>
<br>
I still haven't found any rationale from the guile developers. Anyway,<br>
it's probably easy to add a switch.<br><br></blockquote><div><br></div><div>That would be much appreciated. I guess the usefulness of this varies among programmers. At least I often write the wrong name of a variable, or do a typo, and that quite often too. And getting a message about these minor typos and wrong-namings during compile time is not only a time saver (by not having to run the program in order to discover the error plus spend time figuring out where and why things went wrong), but I guess it can also prevent more long-living bugs. Anyway, I was very thankful to the guile developers for this feature when I made that software package earlier this year, since it saved me a lot of time.</div></div><br></div></div>