On Tue, 2009-12-01 at 09:18 +0100, Øyvind Harboe wrote: > On Tue, Dec 1, 2009 at 9:03 AM, Zach Welch <z...@superlucidity.net> wrote: > > On Tue, 2009-12-01 at 08:52 +0100, Øyvind Harboe wrote: > >> > How about a warning when it's _not_ explicitly enabled or disabled by > >> > the user? Specifically, tell the users to try enabling those features > >> > or to add explicit commands to stop the warnings. Scripts for boards > >> > where that feature will be safe by default could add the required > >> > commands, and users for others will be able to read the documentation > >> > for those commands decide for themselves. > >> > > >> > This keeps the default safe while giving users the nudge in the > >> > direction that you feel they will want to be headed -- eventually. > >> > >> I think this is a good way to go forward. > >> > >> Here is a though on implementation: each target defines a default > >> post-reset script, there is some suitable event that exists currently > >> I'm sure. This post reset script does checks and prints out > >> hints and warnings. > > > > Anything that requires defining a new default gets a frown of > > disapproval from me. That breaks backwards-compatibility, which is > > another reason not to change the default without more consideration and > > wide-spread testing. A warning in the C code should be enough to induce > > that desired outcome, if you also tell users to report their results in > > order to help us decide whether to enable it by default. > > You misunderstand. I would like to see a default tcl handler added > that can be overridden. This tcl handler would not change anything, > just do checks and print warnings. > > No change in defaults.
That does not seem like the right approach for this particular problem, though a handler might be useful to have in other contexts. If it checks for more than one error, then overriding that method eliminates them all. The technique I propose lets the user eliminate one warning at a time through explicit actions. If you want a 'go_fast' wrapper that does all of them at once, that's your policy to decide. --Z _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
