On Wed, Mar 12, 2014 at 3:08 PM, Zach Beane xach@xach.com wrote:
Faré fahree@gmail.com writes:
On Wed, Mar 12, 2014 at 2:25 PM, Zach Beane xach@xach.com wrote:
Dave Cooper david.cooper@genworks.com writes:
On Wed, Mar 12, 2014 at 2:05 PM, Zach Beane xach@xach.com wrote:
I don't think I want to read loud announcements from ASDF. If it isn't
acting like I want, I'd rather read about how to make it do what I want in a tutorial or manual.
Loud announcement only in the initial ASDF release when the new default directory is first introduced. In subsequent ASDF releases the announcement would go away.
I don't think it's a suitable way to communicate with me, even if it only happens for a certain period of time.
I'm not sure what way of communicating you recommend, for changes in default behavior of ASDF or recommended practice in using it.
I'd like to see the behavior clearly documented in the manual and explained in a release announcement or blog post or tutorial or all of the above.
I don't want the software to print extra things out during some transition period.
Oh wait, you're right, I hadn't realized that Dave had proposed ASDF printing a message at runtime.
Indeed, it's a bug for ASDF to announce anything at runtime, unless verbosity is explicitly required and/or a warning or error happens. The test suite actually includes a test-clean-load target that fails if loading ASDF emits any information. A TODO item would be to also test that using ASDF produces no output.
I thought the "loud" announcement under discussion was to happen in the manual and release notes and while releasing the software — the usual procedure, just "louder" than usual due to major changes (yet still maintaining backward compatibility).
My apologies for the misunderstanding.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Every technique is first developed, then used, important, obsolete, normalized, and finally understood.