Remove separate token types from lexer and parser. #5

Closed
opened 2018-03-17 18:34:45 -07:00 by DanilaFe · 2 comments
Owner

With the new update to accommodate operators that are both infix and prefix, the need for a separate "prefix" and "postfix" token grows smaller. They should be replaced by a single "operator" token, and their distinction be stored in another enum, like libab_operator_variant.

With the new update to accommodate operators that are both infix and prefix, the need for a separate "prefix" and "postfix" token grows smaller. They should be replaced by a single "operator" token, and their distinction be stored in another enum, like `libab_operator_variant`.
Author
Owner

On second thought, the parser still needs to make that distinction. Perhaps this requires more thought, or maybe operators need to be made specific during parsing.

On second thought, the parser still needs to make that distinction. Perhaps this requires more thought, or maybe operators need to be made specific during parsing.
Author
Owner

Tokens are now assigned a type after they're parsed. They all start as "TOKEN_OP".

Tokens are now assigned a type after they're parsed. They all start as "TOKEN_OP".
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Experiments/libabacus#5
No description provided.