On Oct 29, 2009, at 11:24 PM, Kwankyu Lee wrote:
> Hi,
>
> verbose() may be quite useful for user programs, but it seems right
> now only oriented for developers. If I place some verbose("...",
> level=1) statements in my Sage program, and the verbose level is set
> to 1 by set_verbose(1), then the verbose statements of internal Sage
> functions are printed, cluttering my own verbose prints.
>
> So I suggest to introduce "flag" parameter to verbose commands like in
> Magma. Then
>
> verbose("...", 1, flag="user")
>
> is triggered when the "user" verbosity flag is set by
>
> set_verbose(1, flag="user")
>
> Of course, flag should be defaulted to "system" (or "internal" or
> something else)
>
> How about this?
I'm +1 to this idea. Even when developing sage, verbose has a
different meaning whether you're working on low-level linear algebra
or higher-level modular forms algorithms.
What about
sage: set_verbose(component=level)
sage: verbose("...", component=level)
Where component could be anything (defaulting to, say "user"), and
unspecified components would have a verbosity of 2 (say), or even
infinity. The only concern would be performance--we'd have to
benchmark this to see how much of a hit it actually is.
- Robert
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
