2022-09-29 16:15:46 <vms14       > can't find a forth that suits my needs and always end wanting to write my own abomination :/
2022-09-29 16:17:39 <vms14       > but my abomination is always wrong in a lot of ways
2022-09-29 16:18:38 <vms14       > no return stack, no @ and !, no memory allocation, words can be overwritten at any time and old definitions using those redefined words will be affected by the changes, etc
2022-09-29 16:19:08 <vms14       > the @ and ! wasn't a problem, but I saw the apples example in starting forth
2022-09-29 16:19:50 <vms14       > the example started with a variable for apples that was just a counter, but then a change was requested, to count red and green apples
2022-09-29 16:20:47 <vms14       > the example instead of changing the existing code just made apples to point to the green or the red counter, so setting the value of apples would set the reds or the greens depending on what was pointing to
2022-09-29 16:21:25 <vms14       > I think it's a good example to show some unknown advantage of @ and !, and the fact they're just a memory address
2022-09-29 16:22:13 <vms14       > btw I kinda like the complete forth book
2022-09-29 16:22:51 <vms14       > https://www.amazon.com/Complete-FORTH-General-Trade/dp/0471882356
2022-09-29 16:22:55 <thrig       > using @ when you need c@ causes glorious bugs
2022-09-29 16:23:07 <thrig       > err, or so I've been told
2022-09-29 16:23:42 <vms14       > thrig: have to do with alignment issues?
2022-09-29 16:28:52 <vms14       > I should complete a forth book before attempting to do my toy lang I suppose
2022-09-29 16:29:26 <vms14       > still I can't make a real forth with a high level language, maybe except C
2022-09-29 16:47:38 <KipIngram   > You can definitely do it in gcc.  I've actually done that.  I wrote the primitives in C, but they "worked" the way Forth primitives should, with a proper NEXT and so on.
2022-09-29 16:47:55 <eris[m]1    > an interesting idea that came to m while reading an article
2022-09-29 16:48:00 <KipIngram   > Mine was indirect threaded, but you could do direct as well.
2022-09-29 16:48:22 <KipIngram   > But it used a non-standard extension gcc offers.
2022-09-29 16:48:23 <eris[m]1    > in a system with @+ and an address register, could a variable be a word that just deposits directly into said register?
2022-09-29 16:49:47 <KipIngram   > Oh, you mean loads the address into that reg instead of putting it on the stack?
2022-09-29 16:50:12 <KipIngram   > I guess then @ and ! would use that register?
2022-09-29 16:59:02 <eris[m]1    > indeed
2022-09-29 16:59:23 <eris[m]1    > generally, the set of operations is:
2022-09-29 17:00:04 <eris[m]1    > acutlaly there's symbol conflict
2022-09-29 17:00:10 <eris[m]1    > it's a debate over the neccessity of a
2022-09-29 17:03:09 <vms14       > I suppose I won't stop until I make my own toy lang
2022-09-29 17:03:40 <vms14       > but it has a lot of design flaws :/
2022-09-29 17:03:50 <eris[m]1    > an interesting interpretation was that you don't actually need HERE in such a system
2022-09-29 17:04:04 <eris[m]1    > since you can just use @+
2022-09-29 19:12:26 <MrMobius    > vms14 is always gone by the time I get here
2022-09-29 19:12:49 <MrMobius    > poor guy should make his forth in javascript or Python until he figures it out
2022-09-29 19:15:29 <MrMobius    > vms14, I just mentioned you. how about making your forth in Python or javascript?
2022-09-29 22:00:11 <Zarutian_iPad> idea of an input device on an mcu: a phototranistor or ldr with an mask with a smallhole. This reads code128 barcodes which basically encodes ascii