[nem-en] Debugging macros again

[Kamil Skalski]

>
> The most sexiest feature of Nemerle for me is it's macro subsystem. And
> having such great VS add-in in place I'm near  applying my first Nemerle
> solution to the production world.
>
> BUT: A situation with debugging macros (speaking more precisely the main
> problem is  the code generated by them) is terrible for now.
>

Did you try the feature of generating the source code of generated
method as a side-effect of generation?
I usually just inspect the generated code with .NET inspector when it
doesn't work as I expected.

>
>
> My feeling about this is that may be it make sense to introduce some hints
> (like these are using in LISP:
> http://www.slac.stanford.edu/comp/unix/gnu-info/elisp_16.html#SEC181)
> to make the code generated by macros more adopted for the human beings? :-)
>

Could you summarize how it could be done in our scenario? Isn't
"stacktrace" from failed compilation a good approximation of this
feature  (a very useful feature here is command line option
-throw-on-error, which gives you the exact stack trace in
macro/compiler when you signal error.

>
>
> Because it seems not so trivial to support correct error messages by
> compiler without introducing new ones in the macro itself as well.  Vlad for
> instance also had such an experience.
>

Could you elaborate? This is the one thing I had never problems with
(if I understand correctly what you mean)


-- 
Kamil Skalski
http://nazgul.omega.pl