STR-374: Logging should not always print the current term
When producing error messages it is annoying if the current term is printed if that does not convey any useful information
for the user, such as an XTC intermediate filename. For example, the following is produced by strc:compiling test06.str
error: cannot type Build(Op(““,[]))
inferred types of subterms:
typed Op(””,[]) as PreTerm
[ strc | critical ]
The result of packing your Stratego program resulted in a file
with a wrong format. This is probably caused by the use of a
.rtree file produced by an old version of Stratego, or by a
concrete syntax embedding using an old syntax of Stratego.
Recompile with the option ‘–format-check 1’ to discover which
module caused the problem.
FILE(“/tmp/StrategoXToJBXPW”)So we need versions of the log(|) strategies that do not print the current term.
Submitted on 28 July 2005 at 12:33
Issue Log
STR-374, rbvermaa:
log only prints current term when it is passed explicitly. please change these calls yourself when you encounter them, if you think the information is useless.
STR-374, visser:
but this does not hold for the abstractions such as fatal-err, which always do print the current term.
STR-374, visser:
Created -msg variants of the log abstractions such as fatal-err,
err, etc. that do not print the current term.
Log in to post comments