00:00:00 --- log: started forth/20.08.27 02:09:48 --- join: proteus-guy joined #forth 02:56:42 --- quit: gravicappa (Ping timeout: 258 seconds) 03:04:46 --- join: gravicappa joined #forth 03:12:53 --- quit: Zarutian_HTC1 (Read error: Connection reset by peer) 03:13:07 --- join: Zarutian_HTC joined #forth 03:24:55 --- join: xek joined #forth 04:15:46 --- join: dave0 joined #forth 05:00:21 --- join: kori joined #forth 05:14:27 --- quit: jsoft (Ping timeout: 256 seconds) 05:36:59 --- quit: kori (Ping timeout: 260 seconds) 05:58:53 --- quit: mtsd (Quit: Leaving) 06:43:22 --- quit: Zarutian_HTC (Read error: Connection reset by peer) 06:44:01 --- join: Zarutian_HTC joined #forth 07:41:59 --- quit: Zarutian_HTC (Ping timeout: 264 seconds) 08:19:46 --- quit: phadthai (Remote host closed the connection) 08:36:03 --- quit: dave0 (Quit: dave's not here) 08:36:57 --- join: Zarutian_HTC joined #forth 08:38:40 --- part: lisbeths left #forth 08:47:41 --- join: phadthai joined #forth 08:58:03 --- join: kori joined #forth 09:36:43 --- join: lisbeths joined #forth 09:45:28 I am working on my tokenized forth in c still. I am not ready to move it over into asm. 09:49:09 A big Problem of Forths is Stack Overflow 😉 09:49:16 My three biggest problems: c doesn't want to work in words of memory, it is hard to make a syntax where every feature of forth is one letter, and also the runtime to c on my system is 16 kilobytes but the rest of my code is only 360 bytes 09:49:38 Good Luck 09:54:58 I wish there was something a bit more minimal than c in order to put my forth in. I have considered fortran which might be faster but it isn't any smaller. I want something that is portable. 10:00:25 You could try one of https://esolangs.org/ 😉 10:04:05 The way I am handling my stack is that it is a character array and if I pop an int I pop sizeof(int) bytes and if I push a void* I push sizeof(void*) bytes. Although this means I can not use swap. 10:07:38 ☹ 10:08:35 Probably You need a union? 10:10:13 I have been told unions are slower under the hood. 10:13:50 You cannot say that generally. Just get Your Project to work, then profile, then optimize 10:16:57 --- quit: elioat (Quit: The Lounge - https://thelounge.chat) 10:18:21 I find character array to be more elegant than using some piece of code I don't understand. 10:25:14 lol 10:29:02 --- join: elioat joined #forth 10:29:55 --- join: WickedShell joined #forth 11:10:52 --- join: brainfunnel joined #forth 12:19:19 --- quit: brainfunnel (Quit: whoops) 12:19:51 re runtime size: just write in assembly and/or write your own libc and startup code... 12:20:10 --- join: mtsd joined #forth 12:22:51 what systems do you plan to run your forth on? is the ~16k overhead significant on them? 13:04:28 --- quit: mtsd (Quit: leaving) 13:08:47 --- quit: xek (Ping timeout: 240 seconds) 13:20:34 --- nick: kelton -> a0123456789 13:30:24 --- nick: a0123456789 -> kelton 13:45:14 --- quit: gravicappa (Ping timeout: 265 seconds) 14:41:23 --- join: dave0 joined #forth 14:57:24 --- quit: tabemann (Remote host closed the connection) 14:57:39 --- join: tabemann joined #forth 17:00:23 Modern machines could handle megabytes of code and not flinch, but as an exercise I would like my code to fit on the roms of the lunar landar. 17:00:51 learn to walk before you run 17:03:26 Well my code is already pretty smol I think it fits. its' just not useful yet. 17:05:02 My end goal is to fit into a boot sector. I am considering really crazy ideas like that krivine machine that fellow used to talk about two years ago. 17:05:37 I really really really have had trouble learning asm. 17:50:27 --- join: proteus-person joined #forth 17:51:44 --- quit: proteus-guy (Ping timeout: 240 seconds) 18:23:00 --- join: boru` joined #forth 18:23:03 --- quit: boru (Disconnected by services) 18:23:05 --- nick: boru` -> boru 18:57:49 lisbeths: what kind of asm are you targeting? 19:22:51 --- quit: Zarutian_HTC (Read error: Connection reset by peer) 19:23:11 --- join: Zarutian_HTC joined #forth 19:53:24 I don't know it seems kind of meaningless to me for my code not to be portable. That's the one thing where I have always butted heads with other forth programmers. 20:07:22 my first two forths were portable, but slow; my most recent forth, zeptoforth, is not portable, but fast (it's written in Thumb-2 assembly) 20:31:52 I guess I should care more about porting code between forths rather than porting the forth itself. 20:32:19 can anyone tell me what the nanometer scale is of the green arrays chip with 144 cores is, and how many cores you could reasonably fit on a 5-10 nanometer intel chip? 21:04:29 --- join: gravicappa joined #forth 21:10:08 --- join: jsoft joined #forth 22:17:24 --- join: Lord_Nightmare2 joined #forth 22:17:34 --- quit: Lord_Nightmare (Ping timeout: 265 seconds) 22:18:32 --- nick: Lord_Nightmare2 -> Lord_Nightmare 23:40:33 --- join: mtsd joined #forth 23:42:06 --- quit: gravicappa (Ping timeout: 240 seconds) 23:59:59 --- log: ended forth/20.08.27