>> I personally would like some functions to print output at the
>> relevant stage:
>> #(ly:warning_parser (_ "blah"))
>> #(ly:warning_translator (_ "blah"))
>> #(ly:warning_event_class (_ "blah"))
>> #(ly:warning_engraver (_ "blah"))
>> #(ly:warning_performer (_ "blah"))
>> #(ly:warning_whatever_else_we_have (_ "blah"))
>>
>> (or not necessarily "warning"; just a "print_during" -- it would
>> actually be useful for one of my research projects!)
>>
>> I'd feel better about decorating regtests if we could truly target
>> the message to the warning. (I still think that most regtests
>> should produce no warnings, and any exception should be in a
>> different directory)
>
> I'd rather we just use
> #(regtest:expext_warning (_ "Some particular warning"))
>
> before the line being the eventual cause of some expected warning,
> and ly:warning get hijacked, matching the expected warnings to the
> given warnings, and complaining at the end of the run in case any
> expected warnings did not turn up.
+1
Werner
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
