CallFailed error on parse

Question

I am a intern trying to write my first Syntax using Rascal.
While programming i ran into an error that my tutor, Riemer van Rozen, had never seen before. At the moment i am still trying to see if the problem is my code or a Rascal bug but i felt like i should report the error here.

The syntax used to parse normally and even after putting the code back the way it was before I added new stuff it still gives the same error.

My Syntax file

module Syntax

lexical Natural = [0-9]+ !>> [0-9] ;
lexical ID = [a-zA-Z][a-z0-9A-Z]* !>> [a-z0-9A-Z];
lexical String = "\"" ![\"]* "\"";
lexical Sym = [a-zA-Z.!@#$%^&*];
lexical Mp = Sym*;

layout WhiteSpace = [\t-\n \r]* ;

start syntax CreatorData
    = title: "title " ID title
    | author: "author " ID author
    | homepage: "homepage " ID homepage;

Parser

module Parser

import Syntax;
import AST;
import ParseTree;

public CreatorData load(str txt) = parse(#CreatorData, txt);

The Error

I hope someone can tell me where i am breaking my program or that i pointed out an unknown Rascal bug.

PLease avoid screenshots, copy-paste your code and use the edit tools. — nicolallias, May 17 '18 at 13:16
Sorry i am new to posting stuff in stackoverflow, i couldnt get the code to look readable so i just ended up making screenshots — Mauro, May 17 '18 at 13:45
Generally, prefix each line of code with 4 spaces (and an empty line) ; prefix each line of error with a `>` — nicolallias, May 17 '18 at 14:59

score 1 · Answer 1 · answered May 17 '18 at 13:22

Call failed means that the call of parse failed, since the arguments you supplied, did not match any of the possible overloads of parse.

For your code, it looks like you also have an ADT called CreatorData. This is overlapping with the CreatorData syntax definition. There is a pattern documented in the tutor how to work around this challenge.

Not sure about your case, but often you can skip the ADT form, and just work on the concrete trees, but that might be something to explore in the future.

I fixed the problem now, Thank you very much for your help! – Mauro May 17 '18 at 13:43 — Mauro, May 17 '18 at 13:43

CallFailed error on parse

1 Answers1