2024-08-03 17:45:20 <user51      > http://0x0.st/XOI6.c
2024-08-03 17:47:29 <user51      > Forth in progress.  Probably lots of unusual stuff going on.  For example, in a colon definition the pointer to the word's dictionary pointer is compiled, rather than an xt.  Colon definitions are terminated by 0.  No use of the return stack, and only a few words.  But colon definitions and execution work, so I'm happy with it so far.
2024-08-03 17:48:06 <vms14       > :0 in c
2024-08-03 17:48:22 <vms14       > this is cool because you can add ffi to C to any library you want
2024-08-03 17:48:38 <vms14       > I'm making an abomination in js, but is not a forth, just a concat lang
2024-08-03 17:48:39 <vms14       > https://termbin.com/e19z
2024-08-03 23:34:10 <veltas      > C's a better choice than JS
2024-08-03 23:34:32 <veltas      > Assembly's the easiest way to write a Forth, believe it or not
2024-08-03 23:34:38 <unjust      > veltas: still working on new B?
2024-08-03 23:34:46 <veltas      > Nope
2024-08-03 23:35:07 <veltas      > I'm happy to talk about the design and share ideas, as I have with zelgomer recently
2024-08-03 23:38:29 <unjust      > ah, i was curious because i noticed the repo had disappeared and wondered if the project got shelved or discarded altogether
2024-08-03 23:38:48 <veltas      > Shelved
2024-08-03 23:39:56 <veltas      > Personally I think C and C++ are good alternatives, with types.  Less clean/pure to write but they have a lot of usage/support
2024-08-03 23:40:15 <veltas      > Types are useful
2024-08-03 23:41:24 <veltas      > C's ecosystem is much better than C++'s, C++ is probably a better language but it's very hard to write good code with it
2024-08-03 23:41:34 <veltas      > From my biased embedded perspective
2024-08-03 23:41:57 <veltas      > You need to throw away most of C++'s features and most of standard library to get a good language hidden away inside
2024-08-03 23:42:19 <unjust      > no reason you can't use it as C (for the most part) and take advantage of classes and templates, and avoid the STL entirely
2024-08-03 23:42:32 <veltas      > Exactly
2024-08-03 23:43:13 <veltas      > And avoid the broken stuff like arguably multiple inheritance, virtual methods, most of exception handling, ...
2024-08-03 23:45:09 <unjust      > pure virtual methods excluded as well?
2024-08-03 23:45:40 <unjust      > iirc, they can be sort of useful for defining something like java's interfaces if that's all a class contains
2024-08-03 23:45:50 <unjust      > but i haven't written anything in C++ for a while
2024-08-03 23:46:17 <veltas      > If it needs vtables then I'd avoid it
2024-08-03 23:49:09 <veltas      > Basically use it as C on steroids
2024-08-03 23:50:21 <veltas      > Not "C with classes", that's actually a real bad thing
2024-08-03 23:51:21 <unjust      > what's bad about it?
2024-08-03 23:52:47 <veltas      > I've just seen people write very old-school C++ a lot, and refuse to use any of the modern features or styles at all
2024-08-03 23:53:03 <veltas      > And it's just error-prone C code with extra ways to shoot yourself in the foot
2024-08-03 23:58:17 <veltas      > This is one of the issues with C++ in the wild, people already write C enough exotic ways, C++ just gives them more ways to be crazy