[nem-en] IntelliSense support of macro
Kamil Skalski
kamil.skalski at gmail.com
Mon Jan 22 18:10:05 CET 2007
BTW. Vlad, do you need Typer2 to be run for any purpose in completion
mode? Because I think it would be a good idea to also provide subtype
of Typer, which could just skip any typing stage after 1.
Also, Michal suggested some time ago, that Typer in completion mode
could start from "error mode" (normal/error mode is a heuristic to
make compilation of valid programs faster), since in completion mode
you process only single function, which is going to have errors in
most cases. For details we need some Michal's insight though.
2007/1/22, vc <vc at rsdn.ru>:
> > Looks very helpful. This is because location of generated method has
> > the location of macro invocation, which generated it?
>
> The Completion because macro generate real methods. :)
> If you say about goto - yes. Macro set location to attribute location.
> If try goto in this situation:
> def ff = CompilerComponentsFactory();
> ff.CreateMethodBuilder(null, null);
> goto will be navigate to root factory.
>
> > So if we had the "jump to definition" feature, we could point to
> > invocation of generated method, jump to place where the macro is used
> > and them maybe even see the method body...
>
> Potentially - yes.
>
> > at least if this is in
> > current compilation, completion engine has this body in memory, isn't
> > it?
>
> For factories defined in current project - yes. For externally defined
> factories we have only location, but it is not so small.
>
>
> _______________________________________________
> https://nemerle.org/mailman/listinfo/devel-en
>
--
Kamil Skalski
http://nazgul.omega.pl
More information about the devel-en
mailing list