Eclipse Community Forums: Dynamic Languages Toolkit (DLTK) » Implement C/C++ style #include the DLTK way...

Home » Eclipse Projects » Dynamic Languages Toolkit (DLTK) » Implement C/C++ style #include the DLTK way...(Our script language has include '<path>' and include_once '<path>', how should these be implemented?)

Show: Today's Messages :: Show Polls :: Message Navigator

Implement C/C++ style #include the DLTK way... [message #646437]

Fri, 24 December 2010 07:51

Carl Knight

Messages: 13
Registered: December 2010

Junior Member

This is something of a request for advice before I roll my own mechanism for implementing include and include_once style behaviour. The statements simply take a string that is the path to another script file.

I've found things in the DLTK like ImportInfo. It can be populated and passed to the acceptImport method of the implementor of ISourceElementRequestor in SourceElementRequestVisitor.

However, the include/include_once behaviour is that the source or at least the resulting AST is available for the unit the include/include_once statement is found in. This is necessary for symbol lookup, etc.

I can't imagine I'm the first to have to do this. My question is what is the correct way using the DLTK before I go much further.

Searching for include on the forum yields oodles of hits, as does import which is not quite the same thing. If you know of a post that answers this question, I won't be insulted if you direct me there with a slap for not searching hard enough! Smile

Thanks.

- Carl.

Report message to a moderator

Re: Implement C/C++ style #include the DLTK way... [message #694579 is a reply to message #646437]

Fri, 08 July 2011 22:01

Timothy Wall

Messages: 21
Registered: July 2009

Junior Member

My target language has a similar construct, where the "import" results in population of the AST. For the moment, I'm putting the stuff in a TypeDeclaration with the module modifier set so the code outline will display them, but ideally they'd go in their own box, perhaps within the "interpreter libraries" folder or a custom folder at the project level.

Report message to a moderator

Previous Topic:	Debugging JRuby in Java container with dltk
Next Topic:	From ASTNode to IModelElement

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Apr 20 13:15:37 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter