2026-08-11 00:20:01 <xentrac     > congratulations \o/
2026-08-11 07:38:54 <lisbeths    > so here is the static language im working on https://dpaste.com/EUZ2CKENS.txt
2026-08-11 07:39:05 <lisbeths    > and it is a portable subset of standard c
2026-08-11 07:39:46 <lisbeths    > this is the rough draft of the dynamic interpreter im building inside of that subset of c https://dpaste.com/3CCYTEJV6.txt
2026-08-11 07:40:44 <lisbeths    > so the usefulness of this is that if you can write a forth mostly in this subset of c it becomes very portable across unix-like and windows systems such as mac, pc, linux, ios, and android
2026-08-11 07:41:08 <lisbeths    > and that makes it alot easier to develop high level apps in the cloud as opposed to low level microcontrollers
2026-08-11 08:55:54 <veltas      > Interesting lisbeths, I've thought of doing similar things myself
2026-08-11 08:56:22 <veltas      > I might recommend 'end' instead of '}' as it makes your syntax feel more consistent, although would be less close to C then
2026-08-11 08:56:34 <veltas      > Also maybe allow indents and use them
2026-08-11 08:57:12 <veltas      > Also 'let' might be better than 'assign', that's what BASIC and probably others used
2026-08-11 09:10:10 <veltas      > I'll be honest I had no clue what you were talking about but now I can see this example it makes some sense
2026-08-11 09:17:55 <lisbeths    > so there is a reason why I define } as }
2026-08-11 09:18:53 <lisbeths    > if you look how I define free, I define it roughlas f("free",a)
2026-08-11 09:19:03 <lisbeths    > a is defined as $1
2026-08-11 09:20:31 <lisbeths    > or sorry f("free",a"("b");")
2026-08-11 09:20:35 <veltas      > Well it's your lang you can do what you want with it
2026-08-11 09:20:48 <lisbeths    > yeah
2026-08-11 09:20:50 <veltas      > I'm back to not understanding but I'll keep reading what you're putting out, it's interesting
2026-08-11 09:21:13 <lisbeths    > well the short story is making it be } saves characters
2026-08-11 09:21:29 <lisbeths    > the language is golfed in its implementatiom
2026-08-11 09:22:07 <lisbeths    > im just trying to restrict the user to a narrow assembler-like subset of c
2026-08-11 09:22:33 <lisbeths    > and the reason is to make it easier to compile to c instead of compiling to asm
2026-08-11 09:22:53 <lisbeths    > compiling c yields portability and arguably a less bug prone compiler
2026-08-11 09:23:29 <lisbeths    > it wouldnt make as much sense to do it on a microcontroller but it makes sense in app development
2026-08-11 09:30:17 <veltas      > Dunno might make sense on microcontroller too but either way the proof is in the pudding
2026-08-11 09:30:41 <veltas      > Maybe 'let' then instead of assign?
2026-08-11 15:12:28 <cleobuline  > hello world
2026-08-11 15:12:55 <cleobuline  > the very first prerelease of the HC thing https://github.com/cleobuline/hc/releases/tag/HCbeta-0.1
2026-08-11 20:46:28 <xentrac     > I prefer Perl's `my` to `let` because it's shorter
2026-08-11 20:46:45 <xentrac     > speaking of golfing
2026-08-11 20:47:56 <xentrac     > in http://canonical.org/~kragen/sw/dev3/server.s I defined a macro `my` for initialized variables (.data) and `var` for zero-initialized variables (.bss)
2026-08-11 20:48:25 <xentrac     > this may be a helpful thing to look at or it may not
2026-08-11 23:29:18 <xentrac     > it occurs to me that the head-final word order in Japanese is almost RPN
2026-08-11 23:29:41 <xentrac     > but where Japanese has watashi no namae wa xentrac desu
2026-08-11 23:29:56 <xentrac     > you would want something more like namae watashi no wa xentrac desu
2026-08-11 23:31:12 <xentrac     > you could imagine "no" pushing things onto a separate context stack consulted by "wa" and such things, although that obviously isn't a good description of how people speak Japanese
2026-08-11 23:31:33 <xentrac     > watashi no haha no namae wa, etc.