@loganfsmyth Is it somewhere described in the specification?

it is described by the grammar ecma-international.org/ecma-262/9.0/#sec-grammar-summary

ecma-international.org/ecma-262/9.0/#prod-ObjectLiteral for instance means that the item after the opening curly of an ObjectLiteral is either a closing curly or the a token that is the start of a PropertyDefinitionList

and an exclamation is not that

@loganfsmyth I understand that the exclamation point is not included in the grammar of parsing ObjectLiteral. Well, should the standard errors be described somewhere in the specification or not? What can you say about this?

Such as not valid characters.

The exact error text of errors isn't really included in the spec

@loganfsmyth I understand correctly that the processing of incorrect sequences (like the text of their errors) is determined by the implementation

ecma-international.org/ecma-262/9.0/#sec-parse-script is the core piece

@loganfsmyth this:"...representing the parsing errors...", right?

@loganfsmyth This is the only thing that describes how to handle parsing errors, right?

Speech on your link above

that's the root logic that runs the parsing process and triggers all the early errors and syntax errors and such, yeah

@loganfsmyth alright, I am very grateful to you for your help.

no problem

are you working on a JS parser or just exploring to learn?

@loganfsmyth So far, I'm not working on the parser, but I plan. In general, I like to learn something difficult