00:00:00 --- log: started forth/20.04.28 00:05:33 --- join: mtsd joined #forth 00:32:20 --- quit: jsoft (Remote host closed the connection) 00:42:29 --- quit: mtsd (Quit: mtsd) 00:44:57 --- join: mtsd joined #forth 00:50:41 --- join: dys joined #forth 01:14:40 --- quit: reepca (Read error: Connection reset by peer) 01:14:50 --- join: reepca joined #forth 01:21:07 --- quit: reepca (Read error: Connection reset by peer) 01:21:29 --- join: reepca joined #forth 01:41:38 --- join: mtsd1 joined #forth 01:42:08 --- quit: mtsd1 (Client Quit) 01:47:38 --- quit: reepca (Read error: Connection reset by peer) 01:48:04 --- join: reepca joined #forth 01:57:09 --- quit: mtsd (Quit: Leaving) 01:57:40 --- join: mtsd joined #forth 01:58:48 --- quit: mtsd (Client Quit) 01:59:22 --- join: xek joined #forth 01:59:28 --- join: mtsd joined #forth 02:19:53 --- part: mtsd left #forth 02:31:31 --- join: mtsd joined #forth 02:41:59 tabemann: I've read that a good way to write a forth is to solve a problem and only write words as soon as they are needed 02:44:35 And that is roughly what I have been doing, my first aim is to write a game, but I know at least I want a good portion of standard forth's core, so that is probably a bit of bloat in there 02:44:57 Still not sure if I'll trim it later or go full standard so I can advertise it under that trademark 02:59:27 --- quit: C-Keen (Ping timeout: 250 seconds) 02:59:51 --- join: C-Keen joined #forth 03:00:08 --- nick: C-Keen -> Guest18165 03:41:03 --- quit: Guest18165 (Changing host) 03:41:03 --- join: Guest18165 joined #forth 03:41:06 --- nick: Guest18165 -> C-Keen 03:54:10 --- join: dave0 joined #forth 05:00:09 --- join: dddddd joined #forth 06:11:25 --- quit: rdrop-exit (Read error: Connection reset by peer) 06:14:08 --- join: rdrop-exit joined #forth 06:18:59 --- join: TCZ joined #forth 06:29:42 --- join: mtsd_ joined #forth 06:29:45 --- quit: mtsd_ (Remote host closed the connection) 06:31:09 --- quit: mtsd (Ping timeout: 246 seconds) 06:36:09 --- quit: rdrop-exit (Ping timeout: 260 seconds) 06:46:49 --- quit: TCZ (Quit: Leaving) 07:05:12 --- quit: iyzsong (Ping timeout: 244 seconds) 07:08:21 --- quit: Zarutian_HTC (Ping timeout: 260 seconds) 07:32:40 --- join: Zarutian_HTC joined #forth 07:38:09 --- join: TCZ joined #forth 07:39:58 --- join: proteus-guy joined #forth 07:46:23 --- quit: Zarutian_HTC (Ping timeout: 256 seconds) 08:13:35 --- join: Zarutian_HTC joined #forth 08:50:16 --- quit: Zarutian_HTC (Remote host closed the connection) 08:52:34 --- quit: TCZ (Quit: Leaving) 08:58:26 --- join: TCZ joined #forth 08:59:00 --- quit: TCZ (Remote host closed the connection) 11:31:54 --- join: mtsd joined #forth 11:34:50 --- quit: mtsd (Client Quit) 11:35:14 --- join: mtsd joined #forth 11:56:45 --- quit: cheater (Ping timeout: 260 seconds) 11:57:25 --- quit: dys (Ping timeout: 256 seconds) 12:09:53 --- join: cheater joined #forth 12:14:01 --- quit: xek (Ping timeout: 260 seconds) 12:26:03 --- join: mtsd_ joined #forth 12:27:36 --- quit: mtsd (Ping timeout: 264 seconds) 12:32:54 --- join: TCZ joined #forth 12:53:31 --- quit: mtsd_ (Quit: mtsd_) 13:24:36 --- join: xek joined #forth 13:55:40 --- quit: xek (Ping timeout: 265 seconds) 14:39:38 --- quit: gravicappa (Ping timeout: 240 seconds) 14:44:30 --- quit: TCZ (Quit: Leaving) 15:31:33 --- quit: X-Scale (Ping timeout: 258 seconds) 15:31:59 --- join: X-Scale` joined #forth 15:32:27 --- nick: X-Scale` -> X-Scale 15:33:47 --- join: jn___ joined #forth 15:33:47 --- quit: jn__ (Ping timeout: 265 seconds) 16:06:10 --- quit: X-Scale (Ping timeout: 265 seconds) 16:06:13 --- join: X-Scale` joined #forth 16:06:48 --- nick: X-Scale` -> X-Scale 16:40:17 --- quit: tabemann (Remote host closed the connection) 16:40:31 --- join: tabemann joined #forth 17:26:51 --- join: TCZ joined #forth 17:35:50 --- quit: Keshl (Read error: Connection reset by peer) 17:35:56 --- join: Keshl_ joined #forth 18:05:21 tp: I have realized that writing a disassembler for zeptoforth is going to be an absolutely huge task 18:43:06 tabemann, so is that a problem ? 18:43:30 tabemann, I mean youre a absolutely huge task killing programmer /// 18:44:14 it just means that work on the rest of zeptoforth will have to be put on hold for a while 18:44:20 right now I'm on ADD 18:44:37 Im sorry to hear that youre A.D.D. 18:44:52 lol 18:44:56 :) 18:47:31 --- join: boru` joined #forth 18:47:34 --- quit: boru (Disconnected by services) 18:47:36 --- nick: boru` -> boru 18:48:31 aaagggh 18:48:37 as a minimally competent programmer, if I ever was to write my own Forth, I think I'd create the minimum useful dictionary then make a assembler and dissasembler to help me with the rest 18:49:23 there's an "add register to SP" in addition to an "add immediate to SP" 18:49:40 just ADD alone is kicking my ass 18:50:15 i think writing the dissambler woul be really useful for you and Zeptoforth 18:50:20 and then there's ADR, which is essentially "add immediate to PC" 18:52:06 --- join: jsoft joined #forth 18:53:45 it'll be useful for certain; it'll also be a pain to write 18:54:07 of course I will probably know the Thumb-2 instruction set through and through by the time I am done 18:54:50 and a lot of your Forth words may soon be in assembly once you do 18:55:25 you really need an assembler also :) 18:56:15 my assembler is gas 18:56:48 i know 18:57:39 but ask youself, why does matthias write an assembler for every one of his forths ? 18:57:44 he also has GAS 18:59:59 I suppose I will - once the disassembler is done 19:00:22 you may need to do them in tandem ? 19:00:32 theyre kinda interconnected ? 19:01:19 I think matthias does them very early on to assist creating all the rest of his dictionary, and trust me, Matthias HATES cortex-m assembly 19:01:49 he hates cortex-m is why 19:02:12 matthias only loves msp430 and risc-v assembly afaik 19:03:41 I'm quickly learning how insane cortex-m assembly is 19:03:59 these addressing modes are ridiculous 19:04:44 something like MIPS would be so much easier to write a disassembler for 19:06:56 i guess matthias feels the same 19:07:04 take thumb1 19:07:29 looks like one of his first words was registerliteral, 19:08:08 once he found out that thumb1 cant do a 32 bit cond jump, he wrote registerliteral, ... end of problem 19:08:55 oops 19:09:11 once he found out that thumb1 cant do a 32 bit register load, he wrote registerliteral, ... end of problem 19:09:48 Mecrisp-Stellaris for cortex.m0 still has the limited cond jump problem 19:09:55 back 19:10:07 he could have fixed it he said, but it's too wasteful 19:10:52 zeptoforth has the same problem 19:12:04 the limited cond jump problem is easly user fixed tho 19:16:05 i.e. break out the code into a separate word 19:16:36 yes 19:17:24 I've done that a few times, in reality not many, in fact so few that when I see the 'jump too far' message, i'm usually WTF ? 19:17:49 it's usually associated with hardware 19:18:35 unlike when I see 'stack underflow' i'm like "what did I do this time?" 19:22:54 practically the only times I get that are when I've corrupted the compile-time data stack 19:23:25 I've never, as far as I can recall, gotten that from too long of an actual branch 19:23:51 in actual projects I get it a bit as I often pass parameters on, such as error flags etc 19:24:15 not good practice I know but I prefer the stack to register use 19:36:05 --- quit: TCZ (Quit: Leaving) 20:05:54 --- quit: tp (Read error: Connection reset by peer) 20:36:55 --- join: rdrop-exit joined #forth 20:37:11 good morning fellow Forthians c[] 20:38:54 --- join: tp joined #forth 20:38:54 --- quit: tp (Changing host) 20:38:54 --- join: tp joined #forth 20:45:46 https://marked.js.org/demo/ <-- interesting browser hosted markdown editor and viewer 21:34:23 --- join: corn joined #forth 21:34:57 What's up forth folks (corn = crab1) 21:36:16 hi crab1, morning reading while waiting for lunch 21:36:24 fun fun 21:36:31 you? 21:37:00 --- quit: dave0 (Quit: dave's not here) 21:44:46 trying to find new approaches to programming, as per usual 21:44:58 cool 21:46:20 Also have an Ensoniq EPS 16+ (sampling keyboard from the 90's) that I bought recently and I want to figure out how easy it would be to write a custom OS for it 21:49:09 wow 21:49:44 hm? 21:50:36 I'm totally clueless when it comes to electronic music tech 21:52:54 me too 21:52:58 but I'd love to learn 22:09:33 this might interest you 22:09:34 https://en.wikipedia.org/wiki/Hierarchical_Music_Specification_Language 22:12:14 interesting 22:13:36 I remembered there were some papers/articles related to it in Forth publications 22:14:39 Someone recently posted about one of Phil Burk's Forths in this chat 22:23:35 lunch is ready, catch you later, stay healthy 22:23:41 --- quit: rdrop-exit (Quit: Lost terminal) 22:35:31 --- quit: dddddd (Ping timeout: 258 seconds) 22:59:36 --- join: gravicappa joined #forth 23:00:53 --- quit: reepca (Read error: Connection reset by peer) 23:01:14 --- join: reepca joined #forth 23:20:46 --- join: mtsd joined #forth 23:30:22 --- quit: mtsd (Quit: mtsd) 23:59:59 --- log: ended forth/20.04.28