You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| : atom ( -- obj )
#number# comes-a?
IF do-numatom exit THEN
#id# comes-a?
IF do-idatom exit THEN
#string# comes-a?
IF drop compile$
do-stringatom exit THEN
." a value" expected error
0 do-numatom ;
in parser.fth, it seems I have forgotten to implement character literals.
The text was updated successfully, but these errors were encountered:
Turns out I decided to handle char constants already at the scanner level.
Still, could be worth to return a different token for char constants than for int constants, so they can be handled as 8 and not as 16 bit numbers.
pzembrod
changed the title
char literals probably missing
consider returning a different token for char than for int literals
Aug 30, 2020
Remains to be verified via a test, but looking at
| : atom ( -- obj )
#number# comes-a?
IF do-numatom exit THEN
#id# comes-a?
IF do-idatom exit THEN
#string# comes-a?
IF drop compile$
do-stringatom exit THEN
." a value" expected error
0 do-numatom ;
in parser.fth, it seems I have forgotten to implement character literals.
The text was updated successfully, but these errors were encountered: