 | | Re: Finally able to add asm forth words (long)
|
|
(...) Yep. But if I have two choices I will always steal from working code over documentation. I will always write code in C first and see what assembler the compiler creates, especialy on a new machine. Trust what already works. -- (...) (24 years ago, 22-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Taking the plunge
|
|
OK I'm about to nervously take the plunge. My code assembles and I'm about to push it off the cliff and see if it flies. If any one feels bored please feel free to review the following and make comments. Finding bugs by inspection is always easier. (...) (24 years ago, 22-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Finally able to add asm forth words (long)
|
|
(...) Steve, You ARE using Kekoa's Internals document, right? Here's the part that describes the interrupt vector redirection. In fact, that's what I do for grabbing the OC1B interrupt for the servo control words... remember intercepting the (...) (24 years ago, 22-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Finally able to add asm forth words.
|
|
(...) It puzzled me for quite a while until I realized that the output was in pbforth.s. Once I saw the results it was much easier. (...) I agree. I have no interest in supporting a varient. I'll hack until it seems to work and then pass it to you (...) (24 years ago, 22-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Finally able to add asm forth words.
|
|
(...) As they say (with a striaght face in the original C library) "Use the fork, Luke" I hope you didn't find the M4 stuff too much of a brain-bender. I'd be hard pressed to tell you how it works anymore... (...) Ummm, because the original hForth (...) (24 years ago, 22-May-00, to lugnet.robotics.rcx.pbforth)
|
