A type definition in ML-like languages can be described as: (EBNF)

type-definition = "type" typedef {"and" typedef}

When writing the following SDF3, the "and" separator is not recognised as a keyword:

template options
  keyword -/- [A-Za-z0-9]

templates
  TypeDefinition.TypeDefinition = [type [TypeDef+; separator="and"]]

I was expecting it to be recognised… Is this an error, or am I abusing the separator syntax?

Submitted by Jeff Smits on 6 October 2013 at 11:06

It probably doesn’t look for keywords in separators, so an error.