 | | Re: Bug in HEX handling?
|
|
(...) Thanks. That helps. Case sensitivity is good but requiring upper case for hex is annoying. I suppose this is forth standard. That is one thing that I find annoying about forth, that most builtin words are upper case. It reveals the age of (...) (24 years ago, 23-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Bug in HEX handling?
|
|
(...) If you use U. (unsigned dot) you will get FFFF. The "." is for signed numbers. (...) Yes it is, but pbForth is case sensitive. Cheers, Ralph Hempel - P.Eng ---...--- Check out pbFORTH for LEGO Mindstorms at: (URL) ---...--- Reply to: rhempel (...) (24 years ago, 23-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Bug in HEX handling?
|
|
HEX is not working the way I think it should in 1.1.1. Is this wrong or do I not understand something. This is 1.1.1 pbmax.srec. ok DECIMAL ok 65536 DUP . -1 ok HEX . -1 Why isn't this ffff? ok 300b 300b ? undefined word Isn't 300b a legal hex (...) (24 years ago, 23-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | FW: pbForth Feedback
|
|
-----Original Message----- From: ian@dolphin.pst.cfmu...control.be [mailto:ian@dolphin....ontrol.be] On Behalf Of Ian Wild Sent: Monday, May 22, 2000 3:18 AM To: Ralph Hempel Subject: Re: pbForth Feedback (...) Indeed it did not. I've patched four (...) (24 years ago, 22-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | 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)
|
