[nem-en] Debugging macros again
Andrei Varanovich
dotnetby at gmail.com
Tue Jan 9 22:10:10 CET 2007
Hi,
Let's go through the issues one-by-one.
So what we have:
1. It's possible to let the compiler know if the error originated in macro generated code
or in original source. As Vlad said almost the same problem was solved in VS integration. Do we need Vlad to describe this solution more detailed?
2. We need to divide somehow the fake code for macro attributes and for macro expressions. And as wee agreed it's really inconvenient to generate all the code (even fake). That's why I was speaking about some hints allow developer to decide whether or not some parts of code should be generated.
But I also like the solution "To show the AST". Will it be a challenge in implementation?
Thanks,
Andrei
-----Original Message-----
From: devel-en-bounces at nemerle.org [mailto:devel-en-bounces at nemerle.org] On Behalf Of Kamil Skalski
Sent: Tuesday, January 09, 2007 10:04 PM
To: devel-en at nemerle.org
Subject: Re: [nem-en] Debugging macros again
>
> We talk about generating fake code for macros generated AST. Maybe time to
> return to this problem?
I implemented this some time ago? Is it not usable?
--
Kamil Skalski
http://nazgul.omega.pl
_______________________________________________
https://nemerle.org/mailman/listinfo/devel-en
More information about the devel-en
mailing list