|Force relinking of XAbstractFeatureCall [message #1830043]
||Thu, 16 July 2020 07:26
|| Lorenzo Bettini
Registered: July 2009
Location: Firenze, Italy
Premise: In one of my Xbase DSLs I'm using the XbaseInterpreter to collect on-the-fly runtime information to help the compiler (mainly for the type system and scoping). When something changes during the interpretation I clear the OnChangeEvictingCache so that computed types are discarded (and so are information about unresolved references) so that the scope provider is queried again to resolve proxies and the type computer is invoked again to compute types, using the new information collected during the interpretation.
Everything works as expected, the only problem is with XAbstractFeatureCall, in particular member feature calls, e.g., something like
With the above architecture, the type of exp is correctly computed again, and it might be completely different from the previously computed type (thanks to the new information collected by the interpreter), however, if "meth" has previously been linked during a previous type computation, it is not attempted to be linked/typed again. Thus, something that could now be unresolved (after typing again exp) is not detected.
Long story short: is there a mechanism to force feature scopes information to be recomputed during type computation?
thanks in advance
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
Powered by FUDForum
. Page generated in 0.01517 seconds