00:00:00 --- log: started forth/20.06.06 00:11:58 --- join: gravicappa joined #forth 00:13:31 --- join: xek_ joined #forth 00:16:42 --- join: xek__ joined #forth 00:18:57 --- quit: xek_ (Ping timeout: 246 seconds) 00:20:36 --- quit: gravicappa (Ping timeout: 260 seconds) 00:25:44 --- quit: jedb (Ping timeout: 260 seconds) 00:32:27 --- quit: karswell (Remote host closed the connection) 00:33:52 --- join: karswell joined #forth 00:42:45 --- quit: jsoft (Ping timeout: 246 seconds) 00:59:28 --- quit: karswell (Remote host closed the connection) 00:59:38 --- join: karswell_ joined #forth 02:07:08 --- join: gravicappa joined #forth 02:14:00 --- join: TCZ joined #forth 02:16:54 --- quit: xek__ (Ping timeout: 246 seconds) 02:19:36 --- quit: gravicappa (Ping timeout: 272 seconds) 02:23:58 --- join: dddddd joined #forth 02:27:28 --- join: jsoft joined #forth 03:09:29 --- quit: TCZ (Quit: Leaving) 03:46:58 --- join: dys joined #forth 03:57:42 --- join: jedb_ joined #forth 04:27:03 --- quit: karswell_ (Remote host closed the connection) 04:28:16 --- join: karswell_ joined #forth 05:14:13 --- join: TCZ joined #forth 05:24:54 --- nick: TCZ -> LegendaryJetpack 05:48:18 --- join: xek joined #forth 06:02:20 --- nick: LegendaryJetpack -> DalekoJeszcze 06:02:25 --- quit: xek (Ping timeout: 265 seconds) 06:18:35 --- quit: DalekoJeszcze (Quit: Leaving) 07:14:03 --- quit: dave0 (Quit: dave's not here) 07:14:35 --- nick: Zarutian_HTC| -> Zarutian_HTC 07:35:26 --- join: TCZ joined #forth 07:39:23 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in) 07:40:00 --- join: iyzsong joined #forth 07:54:19 --- quit: TCZ (Quit: Leaving) 07:55:17 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in) 09:02:49 --- quit: dddddd (Ping timeout: 260 seconds) 09:12:22 --- quit: Zarutian_HTC (Ping timeout: 246 seconds) 09:51:54 --- quit: dys (Ping timeout: 246 seconds) 09:53:22 --- join: cox joined #forth 09:53:27 --- nick: cox -> mark4 10:32:50 --- join: Zarutian_HTC joined #forth 10:39:30 --- quit: jedb_ (Ping timeout: 246 seconds) 11:05:15 --- join: andrei-n joined #forth 11:11:36 --- join: dys joined #forth 12:01:35 --- join: dddddd joined #forth 12:21:41 --- join: gravicappa joined #forth 12:24:01 --- join: xek joined #forth 12:36:07 --- join: xek_ joined #forth 12:38:30 --- quit: xek (Ping timeout: 246 seconds) 13:42:37 --- quit: gravicappa (Ping timeout: 272 seconds) 13:46:28 --- join: TCZ joined #forth 13:52:00 --- quit: jsoft (Ping timeout: 260 seconds) 14:47:54 --- quit: andrei-n (Quit: Leaving) 15:28:36 --- quit: xek_ (Ping timeout: 246 seconds) 15:50:01 --- join: dave0 joined #forth 16:05:51 --- join: X-Scale` joined #forth 16:06:54 --- quit: X-Scale (Ping timeout: 260 seconds) 16:06:55 --- nick: X-Scale` -> X-Scale 16:11:14 --- quit: TCZ (Quit: Leaving) 17:05:25 --- join: nisco joined #forth 17:15:24 --- quit: _whitelogger (Read error: Connection reset by peer) 17:18:25 --- join: _whitelogger joined #forth 17:36:43 --- join: jsoft joined #forth 17:47:53 --- join: Zarutian_HTC| joined #forth 17:48:03 --- quit: Zarutian_HTC (Read error: Connection reset by peer) 18:03:34 --- join: boru` joined #forth 18:03:37 --- quit: boru (Disconnected by services) 18:03:40 --- nick: boru` -> boru 18:15:55 --- quit: dave0 (Quit: dave's not here) 18:51:45 --- join: iyzsong joined #forth 19:19:00 --- nick: Zarutian_HTC| -> Zarutian_HTC 19:26:54 hey guys 19:36:16 --- quit: nisco (Quit: nisco) 19:48:27 hey tabemann 19:50:37 been trying to work out some very strange bugs introduced somehow by adding wordlists 19:51:01 aha 19:53:52 it's really strange 19:54:03 like after I load basic.fs, . stops working 19:54:11 it doesn't crash, it just doesn't display anything 19:54:27 and it does find it, because if I enter an invalid word's name it does indicate it's invalid 19:57:05 okay, that's really strange 19:57:12 it's broken if I just load basic.fs 19:57:17 but it works if I load everything 20:00:07 odd 20:00:16 time for GDB ? 20:05:02 I'm wondering if I should, but the matter is that gdb doesn't play nice with compiled Forth code 20:05:23 it gets confused quickly when it's presented with code outside the provided ELF file 20:05:49 understandable 20:05:52 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in) 20:06:30 thats one advantage of transposing everything to assembly ? 20:07:24 the weird part is that when I load everything, the problem goes away 20:07:42 so this might not be related to the changes I made today 20:08:07 but rather might be an older problem that just happened to surface today because I, for once, didn't load everything 20:08:43 true 20:12:43 --- join: routeveg joined #forth 20:12:48 Hi all 20:13:31 Im a bit of a newcomer to the specifics of FORTH things, could someone confirm for me, POSTPONE appends the XT associated with the proceeding word, to the currently-compiled definition, right? 20:13:39 g'day routeveg 20:13:42 --- join: remexre joined #forth 20:13:44 (ignoring the immediateness of the word) 20:14:03 *currently-compiling, I guess I mean. 20:18:33 Reason I ask is that the docs I'm reading (on the forth website) are a teeny bit unclear on this point, but from what I gather, this is the generally-true statement 20:20:58 back 20:22:32 postpone appends the xt associated with the following token to the word being compiled if it is immediate, and appends code to compile the xt associated with the following token to the word being compiled if it is not immediate 20:33:35 tabemann: Okay, so your last point I am unclear on. There's a word being compiled - if the given token is not immediate, we append code to compile the token, into the currently-being-compiled word 20:34:11 So the currently-being-compiled word then compiles the token into whatever word is being compiled when that word is being 'run'. 20:34:48 : my-compile-word postpone token ; 20:35:06 yes 20:35:30 oop, *immediate after that . then if I go : my-fn my-compile-word ; , that will put a 'call' to token in my-fn ? 20:36:05 if you had written : my-compile-word postpone token ; immediate 20:36:30 Right yeah. cool, okay. 20:36:53 In that case I wonder why the two functionalities of postpone are in the same function. 20:38:25 it's because some people to some it's less confusing, even though some people think it's more confusing 20:38:29 cuz if the following token is immediate, the call to execute the token is compiled into the current definition. Which seems like a pretty different operation to me. I was concerned that I was missing some way in which both of those things are actually the same undernesath 20:38:36 But I can't see the similarity 20:38:57 Ah okay; it's validating that some find it more confusing :) 20:39:51 *some people think it's less confusingg 20:45:00 --- join: iyzsong joined #forth 20:54:24 --- quit: _whitelogger (Remote host closed the connection) 20:55:43 --- join: crab1 joined #forth 20:55:53 what's up forth hackers? 20:57:25 --- join: _whitelogger joined #forth 20:58:59 been trying to implement wordlists in zeptoforth 20:58:59 --- quit: reepca (Read error: Connection reset by peer) 20:59:13 --- join: reepca joined #forth 20:59:21 but I keep running into bugs 20:59:38 what are wordlists? 20:59:51 lists of words - lol 21:00:23 right, but for what purpose, for you to be running into bugs they must not be the same as regular lists 21:00:36 no, they're not ordinary lists 21:01:38 they're a way to organize how words are searched for 21:01:52 --- quit: Zarutian_HTC (Read error: Connection reset by peer) 21:01:53 ah okay 21:02:05 --- join: Zarutian_HTC joined #forth 21:02:36 a data structure to optimize word searching 21:04:34 it's not really an optimization per se 21:04:57 it's a way to select which words are searched for 21:06:15 I've gotten a PineBook Pro just this last week, and I want to see if I can turn it into a forth machine 21:07:44 doesn't selecting which words are searched for increase the efficiency of word searching? by reducing the domain of a search 21:08:57 well, not necessarily, because, e.g., in zeptoforth it has to search through the dictionary for each individual wordlist in the wordlist order 21:09:41 I had to implement it that way due to limitations imposed by compilation to flash which made it difficult to do it the traditional forthy way 21:09:49 so then it is purely for organization, gotcha 21:21:56 hm PBP has 3 processors 21:22:28 or 4 21:24:32 Cortex A72 + Cortex A53 + Cortex M0 * 2 + Mali T864 GPU 21:32:32 what's the PBP? 21:32:58 Pinebook Pro 21:33:04 ah 21:33:10 my new toy 21:33:34 5 processing units sounds like a lot to manage though 21:34:00 I've been sticking to Cortex-M4 (or, in the case of the Numworks calculator, Cortex-M7) processors 21:34:24 with my x86-64 laptop serving as a terminal and an editor 21:34:29 4 of them are combined in big.LITTLE architecture though, which seems to be pretty standard 21:36:38 all those processors seem kind of unwieldy architecture-wise 21:37:14 why so? 21:37:27 well how asymmetric the processors are 21:38:47 that's the whole point of it though, isn't it 21:39:46 okay, I'm gonna go to bed because I'm falling asleep right now 21:39:51 g'night 21:40:56 toodles 22:00:24 --- quit: _whitelogger (Remote host closed the connection) 22:03:25 --- join: _whitelogger joined #forth 22:04:10 --- quit: crab1 (Quit: Connection closed) 22:19:21 --- join: iyzsong- joined #forth 22:19:53 --- quit: iyzsong (Ping timeout: 260 seconds) 22:23:26 --- quit: reepca (Ping timeout: 246 seconds) 22:51:04 --- quit: va (Read error: Connection reset by peer) 23:20:51 --- join: crab1 joined #forth 23:59:59 --- log: ended forth/20.06.06