George? Please call me Jakob! =)Currently erlide doesn't use any AST tools,
I think it would be a good idea to use the ones in wrangler. We have a very,
very simple partitioning on function level (which is used for the outline
and erlang navigator), but that is all. Although it's simple, it's not
useless, it could be used to select the parts needed to be rewritten, for
instance, pretty-printing only the affected functions.
BTW, a good pretty-printer is high on the wish-list for erlide.
How do you think we should integrate them? Should we share the same
repository, or keep them apart?
/Jakob
2008/6/25 <[EMAIL PROTECTED]>:
> Hi George,
>
> Thanks very much indeed for your information.
>
> > The way I see it there are two ways to do this, either a minimal
> approach,
> > where wrangler is provided as a plugin within the erlide feature, or a
> > more ambitious one, where the AST tools in wrangler is factorized out,
> > and used as tools throughout erlide.
>
> Wrangler is built on top of SyntaxTools. Does Erlide have its own parser,
> or
> does Erlide use SyntaxTools too?
>
> Replacing the AST tool used by Wrangler could be hard, but it also
> depends on how different the two AST tools are.
>
> > - It shouldn't really rewrite entire files, only the portions affected by
> > the refactoring
>
> That's a good suggestion. Because of the use of pretty-printing, rewriting
> the entire files seems unavoidable, but I will try to see whether there
> are any better solutions.
>
> Kind Regards,
> Huiqing
>
>
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Erlide-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/erlide-devel
