That definitely helps, the mistake I made was separating the keyword TRIGGERS from the associated actions in the brackets.

BEO “judge” {

OK “approved” {
OK “event ok” STOP
}

NOK “rejected” {
NOK “event nok” STOP
}

DIR “judgement management necessary” {
DIR “event to management” TRIGGERS { DIR }
}
}

DIR “judgement by management” {}

It’s easy with your suggestion

public static Parser Event =
from code in Identifier.Named(“[Event Identifier]“)
from name in QuotedText.Named(“[Event QuotedText]“)
from actiecodes in ActionCodes.XOr(NoActionCodes)
select new WorkflowEvent(code, name, actiecodes);

public static Parser<List> NoActionCodes =
from stopKeyword in Parse.String(“STOP”).Named(“[STOP keyword]“)
select new List(); // empty list

public static Parser<List> ActionCodes =
from triggersKeyword in Parse.String(“TRIGGERS”).Named(“[TRIGGERS keyword]“)
from lbracket in Parse.Char(‘{‘).Token().Named(“[Left bracket action codes triggered by action code]“)
from actionCodes in ActionCode.Many().Named(“[Action codes triggered by action code]“)
from rbracket in Parse.Char(‘}’).Token().Named(“[Right bracket action codes triggered by action code]“)
select new List(actionCodes);

Now I really like the way in can work both top down and bottom up with the parser methods.

It’s easy to build from small parts and let tests drive the extension of the grammar incrementally.

/Mike

BracketedItems.XOr(Parse.Return(…))

Where the … is a default value when the brackets are absent.

Hope this helps.

I’m writing a simple workflow grammar and have a question.

[INPUT]

BEO “judge” {
OK “approved” {
OK “event ok” STOP {}
}
NOK “rejected” {
NOK “event nok” STOP {}
}
DIR “judgement management necessary” {
DIR “event to management” TRIGGERS { DIR }
}
}

DIR “judgement by management” {}

[/INPUT]

How can I make the brackets after the STOP keyword optional?

DIR “event to management” TRIGGERS { DIR }

NOK “event nok” STOP {}

I would like it to be either
TRIGGERS {DIR1 DIR2}
or just
STOP

Kind regards,
Mike