4tH compiler

Robert Ackerman and I are working forth source code that will send an HTML file to chrome which then opens a window suitable for entering things like 2 2 + . That line of code gets sent back to forth for execution. The answer is then reported back In the chrome window. 4 Do you have any

That's why you do things like this: uBasic has about 60 keywords and with every single token they are checked. So I applied my binary search patch. About 80 opcodes, clean replace, worked first time, 1.6 times faster (about 40% increase). BAM! Hans Bezemer

Hi Ron, My build environment?! You'll laugh! https://www.linkedin.com/pulse/polishing-turd-hans-bezemer/ Yes, this is it. Ubuntu 16.x, 8 ARM cores, 2 gigs RAM, 32GB SDcard. Note it is more powerful than my first Linux computer and there are no problems whatsoever working on it. It's got Lyx,

When you have time would you describe your new build environment? What OS are you using? Etc etc. Best regards Ron K Jeffries On Sun, Aug 4, 2019, 7:51 AM The Beez

Hi 4tH-ers! If you keep an eye on SVN, you'll see I made some final changes here. I've integrated David Johnsons excellent graphics contributions into the mainline and that tell you we're DONE! It took me a while to catch up after all calamities, but we're here. The manual is the only thing

Hi 4tH-ers! Normally, the 4tH preprocessor is speedy enough, but sometimes, there is a noticeable delay. Not enough to irritate you, but still. So I wondered if I could speed things up by applying binary search with some lookup tables. But would it do enough? Well, I decided to test the thing,

BTW, I've committed the code. It's in SVN. Hans Bezemer

Hi 4tH-ers! Don't be alarmed. There are several versions which never saw the light of day - especially before v3.5a. It's just that when the bytecode changes, the version changes. And I've decided to change the bytecode - AGAIN. After the discussion on DO..LOOP, I decided not to go that far. As

Hi 4tHers! My brand new Lyx installation was refusing to display images in preview. I'd already visited several fora, but I couldn't find the problem. The solution was to edit ImageMagick's policy.xml file. Even though it was a PDF that I supplied to LyX, and LyX ends up with a PNG, it was

Of course, this should be DO: DO compiles to: FOR LITERAL (0)