YellowGrass

Support multi-file reference resolving in the Stratego editor (1)

Would require a dynamic rule that stores the source file of each definition and reparsing of the source file for a particular definition. We should be able to inspect whether a term has an origin or not for this (i.e., Spoofax/11)

Submitted by Lennart Kats on 16 February 2010 at 16:04

Issue Log

On 1 April 2010 at 15:55 Nathan Bruning commented:

This can also be implemented without origin-introspection. I keep track of a definition -> source module mapping while parsing. The resolve strategy then parses the referenced module, desugars it and finds the referenced definition.

On 1 April 2010 at 17:34 Lennart Kats commented:

You’re absolutely right, I just figured it would be easier (or more efficient) to have this origin tracking API. I would be interested in seeing how you solved this one though; we still need a good general design pattern for this.

On 23 November 2011 at 13:01 Lennart Kats tagged 0.61
On 23 November 2011 at 13:02 Lennart Kats removed tag 0.7
On 23 November 2011 at 16:29 Lennart Kats removed tag 0.61
On 23 November 2011 at 16:29 Lennart Kats tagged 1.0
On 23 November 2011 at 16:29 Lennart Kats removed tag 1.0
On 23 November 2011 at 16:29 Lennart Kats tagged 1.1
On 16 December 2012 at 11:09 Guido Wachsmuth commented:

Nowadays, this only requires a NBL definition for Stratego.

On 16 December 2012 at 11:09 Guido Wachsmuth tagged name-binding
On 16 December 2012 at 11:10 Guido Wachsmuth tagged @guwac
On 16 December 2012 at 11:10 Guido Wachsmuth tagged @gohla
On 16 December 2012 at 11:10 Guido Wachsmuth removed tag @lennartkats
On 18 December 2012 at 14:12 Gabriël Konat closed this issue.

Log in to post comments