Community
Participate
Working Groups
The fix of bug 310435 causes the serializer to fail when the value for a terminal-, datatype-, or enum-rule is invalid. Before the fix, the value was just written to the output stream without any complaints. Since the ConcreteSyntaxValidator is in a position to compose much more meaningful error messages for this kind of errors, it should do so.
this is proposed to be handled bug 333976.
In the new serializer - ValueSerializer.serializeAssignedValue() raises errors for invalid values of Terminal/Datatype-Rules. - EnumLiteralSerializer.serializeAssignedEnumLiteral() raises error is an invalid enum rule literal is used. In contrast to the old serializer, this error will be propagated back to whoever invoked the serializer and *not* cause another iteration in backtracking (at least when no backtracking-decision depends on it).
Closing all bugs that were set to RESOLVED before Neon.0