Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with files in common and j1a #41

Open
bmentink opened this issue Oct 1, 2016 · 1 comment
Open

Issues with files in common and j1a #41

bmentink opened this issue Oct 1, 2016 · 1 comment

Comments

@bmentink
Copy link

bmentink commented Oct 1, 2016

I have been trying to use the mini-oof.fs module out of common. It doesn't want to work for the j1a processor ..

I have identified two problems with it, so far.

  1. There is no "noop" baseword which makes "end-class" not compile.
    My base words are as follows .. no "noop" in sight ...
>words
 init .s tasksel quit evaluate refill accept char postpone literal ' abort chars char+ cells r@ r> >r depth io@ nip over drop dup swap u< < = invert or and xor - + 2/ 2* decimal unloop j i +loop loop ?do leave do recurse does> until again then begin if ahead ; exit :noname : [ ] immediate sliteral s, compile, c, , allot parse parse-name \ source 2! 2@ cmove> cmove fill >number sfind align um/mod m* * um* d2* d0= m+ s>d dabs dnegate d+ aligned /string here abs words forth tth >in state base type bounds count c! c@ max min 2over 2swap +! 2dup ?dup 2drop tuck -rot rot true false @ execute .x .x2 bl cr space emit key key? rshift lshift io! ! u> 0> 0< > 0<> <> cell+ 0= 1- negate 1+  ok

  1. the word "var" doesn't seem to work, I try:
1 cells var test
10 test !
test @ .

and I get rubbish result, it can even lock up quit ... and have to CTRL-C to get prompt ..
I notice that a lot of files in "common" are used in the j2a processor examples, have they been tested for j1a?

@bmentink
Copy link
Author

HI,

I havn't had a reply to this, but would really like to see if I can use the mini-oof module ...
I notice that it is used in the FT900 code, but not for the j1a, is there a way to get it going for the j1a?

Maybe a review of the "common" code is due if code in there is no longer "common" to all processors ..
Comments?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant