search

jkotlinski / durexforth

Modern C64 Forth
Other
233 stars 28 forks source link

Missing $ before a in format.fs? #264

Closed burnsauce closed 4 years ago

burnsauce commented 4 years ago

When building format.fs from source, the interpreter fails on this line:

https://github.com/jkotlinski/durexforth/blob/3d666f96954d474beaf06d1441ae4466ccb612c0/forth_src/format.fs#L13

not recognizing the word 'a'. I can only imagine that it's supposed to be a hex constant. Is that correct?

jkotlinski commented 4 years ago

Hi! You are right - the $ is missing!

On Tue, 6 Oct 2020 at 20:31, Poindexter Frink notifications@github.com wrote:

When building format.fs from source, the interpreter fails on this line:

https://github.com/jkotlinski/durexforth/blob/3d666f96954d474beaf06d1441ae4466ccb612c0/forth_src/format.fs#L13

not recognizing the word 'a'. I can only imagine that it's supposed to be a hex constant. Is that correct?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jkotlinski/durexforth/issues/264, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAY34O2BXBEEKDL77LULCFLSJNO6ZANCNFSM4SGMRBWQ .

burnsauce commented 4 years ago

This begs a question for me: how are the files successfully compiled into the base dictionary? I confess, I can't follow the build process.

Whammo commented 4 years ago

Something like this? compile.fs

---modules--- marker ---modules--- include labels include doloop include format include sys include debug include ls include require marker ---editor--- include v save-forth @0:durexforth

burnsauce commented 4 years ago

That's what I was looking for, thanks! Couldn't see the forest for the trees after a week of data entry :)

burnsauce commented 4 years ago

Now I see that format.fs is interpreted while hex is enforced, so this is not a bug.