lmh symbols will become an increasingly important management tool. It currently generates symbols from language bindings xxx.*.tex to the signature files xxx.tex.
But we also need (and that may be a different lmh command, let's call it lmh symcheck for the moment) to make sure that the set of symbols defined in language and logic bindings are the same (whatever that means).
to take care of orphaned symbols (#139) (maybe this is still lmh symbols).
take mmt into account (see #291)
generally take over the symbols part of syntax checking (see #138)
fix the remaining bugs in lmh symbols (see #166, #288, #287)
more to come I guess
I imagine that lmh symcheck is applied to a module name as in lmh symcheck foo and then it checks the symbol consistency between foo.*.tex. Unlike lmh symbols it should only report problems, not try to fix them.
lmh symbolswill become an increasingly important management tool. It currently generates symbols from language bindingsxxx.*.texto the signature filesxxx.tex.But we also need (and that may be a different
lmhcommand, let's call itlmh symcheckfor the moment) to make sure that the set of symbols defined in language and logic bindings are the same (whatever that means).lmh symbols).lmh symbols(see #166, #288, #287)lmh symcheckis applied to a module name as inlmh symcheck fooand then it checks the symbol consistency betweenfoo.*.tex. Unlikelmh symbolsit should only report problems, not try to fix them.