NaBL2 started giving errors on origins.
(From: https://github.com/metaborg/nabl/blob/master/org.metaborg.meta.nabl2.shared/trans/nabl2/shared/ast.str#L44)

My ast has origins, I'm checking that with at the end of my desugaring:

  warning-on-missing-origin: term -> <id>
    with
      terms-missing-origin;filter(not(?[]));map(debug(|"Warning: Term missing origin"))
  
  terms-missing-origin = collect-all(not(origin-offset))

Errors in console:

16:37 | INFO  | stderr                         - [ identity crisis | warning ] Cannot copy origin from 
16:37 | INFO  | stderr                         -           "NodeParentRelation"
16:37 | INFO  | stderr                         - [ identity crisis | warning ] Cannot copy origin from 
16:37 | INFO  | stderr                         -           "parentRelation"
16:37 | INFO  | stderr                         - [ identity crisis | warning ] Cannot copy origin from 
16:37 | INFO  | stderr                         -           "childrenRelation"
16:37 | INFO  | stderr                         - [ identity crisis | warning ] Cannot copy origin from 
16:37 | INFO  | stderr                         -           "parent"
16:37 | INFO  | stderr                         - [ identity crisis | warning ] Cannot copy origin from 
16:37 | INFO  | stderr                         -           "children"
16:37 | INFO  | stderr                         - [ identity crisis | warning ] Cannot copy origin from 
16:37 | INFO  | stderr                         -           "children"
16:37 | INFO  | stderr                         - [ identity crisis | warning ] Cannot copy origin from 
16:37 | INFO  | stderr                         -           "parent"

(This causes various further errors, such as names not resolving.)

Spoofax version:

Eclipse: org.eclipse.platform.ide 4.6.2.M20161124-1400
Spoofax: org.metaborg.spoofax.eclipse 2.2.0.20170201-122621-master
System: Mac OS X x86_64 10.12.2

Spoofax version that did not have this error:
Jan 31 16:23

Submitted by Daco Harkes on 1 February 2017 at 16:41


On 13 February 2017 at 15:32 Hendrik van Antwerpen commented:

This has been resolved since, if I am correct.


On 13 February 2017 at 15:32 Hendrik van Antwerpen closed this issue.

Log in to post comments