On Oct 3, 5:57 am, dben...@[EMAIL PROTECTED]
wrote:
> ...
> I am interested! Tell me in greater detail what you expect to be error-
> highlighted. (I think I follow but I want to be certain.)
>
> Why an 'error message parser'?
My thinking is this: I'd like to quickly see what I did wrong instead
of manually performing a term-by-term comparison on a pair of type
signatures. I'd see three obvious solutions (though there are
certainly more):
1) make the compiler message more useful, pointing out the DECL_INFO
list vs DECL_INFO as the source of the problem immediately, then
showing the full mismatch message. I had assumed that this would be
difficult, although on reflection, it might not be. It would also be
compiler-specific.
2) integrate a full type error slicer with sml-mode. This seems very
difficult because you would have to make sure the slicer was fully
synchronized with the emacs comint shell and the state of the inferior
sml-process.
3) quickly hack up an emacs extension that (maybe on request, maybe
always) would parse the buffer for [tycon mismatch] error indications,
then do the same term-by term comparison (or more generally,
unification) that I do, then highlight the words "DECL_INFO list" and
"DECL_INFO" in the error message. Of course, showing me the problem in
the original source would be even better, but I think this implies
solution (2). Clearly, this is not a general solution and will not
necessarily provide useful feedback in all cases, but it seems like
the easiest way to get the most return for the effort.
Regards,
- Kenn
|
