&IF, &THEN, &ELSEIF, &ELSE, and &ENDIF preprocessor directives get parsed as errors

[gustason]

For example,

&IF LOOKUP("{&OPSYS}","MSDOS,WIN32":U) > 0 &THEN
    &SCOPED-DEFINE SLASH ~~~\
&ELSE
    &SCOPED-DEFINE SLASH /
&ENDIF

Gets parsed as this:

Another example:

&if '{&name}' = '' &then
    &scoped-define name ttTable
&endif

define {&visibility} temp-table {&name} no-undo
  field something as int
  field something2 as char
  index something as primary unique something
.

[gustason]

Same thing for &GLOBAL and &GLOBAL-DEFINE:

&GLOBAL Main_index 49153
&GLOBAL-DEFINE MAX-EXPENSE 5000

both get parsed as errors.

[eglekaz]

Registered: usagi-coffee/tree-sitter-abl#88

[ccecvb]

I noticed
&then
changes to

&
then

That is probably related to this

[PauliusKu]

@ccecvb yes, currently, the parser we use incorrectly understands preprocessor directives, so we are waiting for the fix on it.