Omega-TI Posted July 8, 2015 Author Share Posted July 8, 2015 Okay, I found >PART< of the problem, some of the dates did not have the leading space in the quotes that fbForth seems to require... I will not be forgetting that. The syntax is new to me... to say the least. Now I get what is in the attached photo below... I still have to take line 8 out and reset before I can go in a edit block 62! Quote Link to comment Share on other sites More sharing options...
+Lee Stewart Posted July 8, 2015 Share Posted July 8, 2015 ... What am I missing here? I think I did exactly what you said... Yeah, that's the problem: doing exactly what I said! Sorry. The problem is a broken BASE->R – R->BASE pair. There should never be a LOAD or CLOAD between them! Change the line to DECIMAL 62 R->BASE CLOAD TIME and remove the R->BASE at the end of line 9. From the above code, you can see that we don't need HEX after TIME because nothing in the rest of the block needs it.. ...lee 1 Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted July 8, 2015 Author Share Posted July 8, 2015 Okay, I changed line 8 to DECIMAL 62 R->BASE CLOAD TIME I still get conditionals not paired. I'll go back in (again) remove the line, reset and see what's up with block 62. Quote Link to comment Share on other sites More sharing options...
+Lee Stewart Posted July 8, 2015 Share Posted July 8, 2015 Okay, I found >PART< of the problem, some of the dates did not have the leading space in the quotes that fbForth seems to require... I will not be forgetting that. The syntax is new to me... to say the least. Forth does not require a leading space, as such. It requires separation between words. ." is a word that means “print string”. If you follow it with something other than a space, the interpreter will keep merrily reading until a space occurs, at which point it will try to find that space-delimited word in the dictionary—usually, not finding it, of course. Now I get what is in the attached photo below... I still have to take line 8 out and reset before I can go in a edit block 62! You could have merely typed DECIMAL ahead of 62 EDIT —not something you should have to do; but, in this case, the bad code I gave you for block #1 likely left you in HEX . ...lee 1 Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted July 8, 2015 Author Share Posted July 8, 2015 You could have merely typed DECIMAL ahead of 62 EDIT —not something you should have to do; but.., I'll try that next time, it'll save me a cr*p load of re-editing block #1 and resetting. Now what the problem is in block 62... I dunno, I'm a newb trying to read Greek here! Quote Link to comment Share on other sites More sharing options...
+Lee Stewart Posted July 8, 2015 Share Posted July 8, 2015 I'll try that next time, it'll save me a cr*p load of re-editing block #1 and resetting. Now what the problem is in block 62... I dunno, I'm a newb trying to read Greek here! You missed an OF after the 4 in line #7. ...lee 1 Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted July 8, 2015 Author Share Posted July 8, 2015 I'll go in and take care of that! Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted July 8, 2015 Author Share Posted July 8, 2015 Ahhh, that would have been too simple! Now I get... Quote Link to comment Share on other sites More sharing options...
+Lee Stewart Posted July 8, 2015 Share Posted July 8, 2015 Ahhh, that would have been too simple! Now I get... This is called the “one more bug syndrome”. The definition of fixCLOK is missing an opening : in line #12 and a terminating ; in line #13. ...lee Quote Link to comment Share on other sites More sharing options...
Opry99er Posted July 8, 2015 Share Posted July 8, 2015 Ohm, you read through any of the Brodie book yet? : READING ." NOW " ; : START CLS CR CR ; : MSG START READING ; And don't for forget to FLUSH... 2 Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted July 8, 2015 Author Share Posted July 8, 2015 This is called the “one more bug syndrome”. The definition of fixCLOK is missing an opening : in line #12 and a terminating ; in line #13. ...lee Ahhhh soooo! I'll go check the printout and make the appropriate changes and get back to ya! Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted July 8, 2015 Author Share Posted July 8, 2015 Ohm, you read through any of the Brodie book yet? : READING ." NOW " ; : START CLS CR CR ; : MSG START READING ; And don't for forget to FLUSH... 'Fraid not. Actually I should be doing more important things right NOW instead of playing around on A.A., but figured I can shoe-horn them in tomorrow morning before I leave. I'm doing a lot of FLUSHing, that's for sure! Quote Link to comment Share on other sites More sharing options...
Opry99er Posted July 8, 2015 Share Posted July 8, 2015 Most of what Lee is showing you is described and illustrated in the first few chapters of Starting Forth... All the colon definition details, how WORDS are used, and not syntax... When you have time (and believe me, I KNOW about time constraints) sit down with fbForth in the slot, Starting Forth pn the desk, and go line by lije, example by example in the first 4 chapters of the book... I promise you will soil yourself. Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted July 8, 2015 Author Share Posted July 8, 2015 Oh CRAP! Is there a way to ABORT block one from processing on startup? I cannot do ANYTHING now. All I get now is what you see below and it locks up tight... Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted July 8, 2015 Author Share Posted July 8, 2015 Most of what Lee is showing you is described and illustrated in the first few chapters of Starting Forth... All the colon definition details, how WORDS are used, and not syntax... When you have time (and believe me, I KNOW about time constraints) sit down with fbForth in the slot, Starting Forth pn the desk, and go line by lije, example by example in the first 4 chapters of the book... I promise you will soil yourself. Well, I plan to take his expert course due to start in about a week AND get his excellent manual printed off at the Office Despot near where I work in about a week too. I hopefully will have more time in the next few weeks as well. This is kind of like dropping me in the deep end of the pool, but I am getting something out of it (other than frustration). Quote Link to comment Share on other sites More sharing options...
Opry99er Posted July 8, 2015 Share Posted July 8, 2015 Check out section 3 of the fbForth manual (starting on pg. 22) Using a Disk Manager, you can copy the BLOCKS file to another disk under a different name if you want to. You can use the USEBFL command to load the selected block for editing. Still though... Never had anything set up to auto-launch in fbForth, so I'm not 100% sure if this will work for you. Might auto-process anyway. 1 Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted July 8, 2015 Author Share Posted July 8, 2015 ThanX, but speaking of FLUSHing, I don't have any more time to flush on it tonight. I was looking for a quick fix like FCTN 4 or an equivalent. One step forward, two steps backward. Quote Link to comment Share on other sites More sharing options...
+Lee Stewart Posted July 8, 2015 Share Posted July 8, 2015 Oh CRAP! Is there a way to ABORT block one from processing on startup? I cannot do ANYTHING now. All I get now is what you see below and it locks up tight... Yes—Rename FBLOCKS or change DSK1 to a disk that does not have FBLOCKS. fbForth will complain and MENU will not be defined; but, you can then edit the file. Let's say FBLOCKS is now on DSK2. Do the following to edit block #1: USEBFL DSK2.FBLOCKS 1 EDIT Also, send me the file so I can have a look. ...lee 1 Quote Link to comment Share on other sites More sharing options...
Omega-TI Posted July 8, 2015 Author Share Posted July 8, 2015 Sweet SUCCESS! https://www.youtube.com/watch?v=_A_a_nEy0TY&feature=youtu.be Thank you so much Lee! 2 Quote Link to comment Share on other sites More sharing options...
+Lee Stewart Posted July 8, 2015 Share Posted July 8, 2015 Nice! ...lee 1 Quote Link to comment Share on other sites More sharing options...
Tursi Posted July 8, 2015 Share Posted July 8, 2015 Congratulations Ohm! 1 Quote Link to comment Share on other sites More sharing options...
Willsy Posted July 8, 2015 Share Posted July 8, 2015 By the way, you can do this in TurboForth too. Hope nobody minds me mentioning it here. And here's the source. There's more comments than code! 2 Quote Link to comment Share on other sites More sharing options...
Willsy Posted July 8, 2015 Share Posted July 8, 2015 Well, I plan to take his expert course due to start in about a week AND get his excellent manual printed off at the Office Despot near where I work in about a week too. I hopefully will have more time in the next few weeks as well. This is kind of like dropping me in the deep end of the pool, but I am getting something out of it (other than frustration). Look here: http://turboforth.net/tutorials/tutorials.html The first few chapters will work with fbForth. 2 Quote Link to comment Share on other sites More sharing options...
+Lee Stewart Posted July 8, 2015 Share Posted July 8, 2015 By the way, you can do this in TurboForth too. Hope nobody minds me mentioning it here. Surely not! And here's the source. There's more comments than code! I have often envied your (TurboForth's) file-processing code. While I think more flexible, fbForth's is harder to use. Even I keep the manual handy! This is entirely TI Forth's fault because my primary goal, while developing fbForth, was, as much as I could manage, to maintain compatibility with TI Forth. After all, the subtitle of the fbForth 2.0 Manual is “A File-Based Cartridge Implementation of TI Forth”. ...lee Quote Link to comment Share on other sites More sharing options...
Willsy Posted July 8, 2015 Share Posted July 8, 2015 I have often envied your (TurboForth's) file-processing code. While I think more flexible, fbForth's is harder to use. Even I keep the manual handy! This is entirely TI Forth's fault because my primary goal, while developing fbForth, was, as much as I could manage, to maintain compatibility with TI Forth. After all, the subtitle of the fbForth 2.0 Manual is “A File-Based Cartridge Implementation of TI Forth”. ...lee Yeah, I didn't do a bad job on that, even if I say so myself. There's one area that could be improved (oh the benefit of hindsight) but it's robust and reliable, as far as I can tell :-) Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.