00:00:00 --- log: started forth/17.08.04 00:38:18 --- quit: roboguy` (Remote host closed the connection) 00:38:52 --- join: roboguy` (~roboguy_@24-143-53-151-static.midco.net) joined #forth 00:43:19 --- quit: roboguy` (Ping timeout: 240 seconds) 01:01:31 --- quit: dys (Ping timeout: 240 seconds) 01:04:33 --- join: http_GK1wmSU (~deep-book@61-68.furanet.com) joined #forth 01:04:47 --- part: http_GK1wmSU left #forth 01:24:48 --- quit: djinni (Quit: Leaving) 01:25:32 --- join: dys (~dys@2003:5b:203b:100:6af7:28ff:fe06:801) joined #forth 01:32:30 --- join: djinni (~djinni@68.ip-149-56-14.net) joined #forth 01:47:20 Apparently not. 02:13:15 larsb: what are you trying to do? 02:23:07 Have GDB understand the Forth dictionary. 02:23:35 yes, bug why gdb? a subroutine-threaded forth? 02:23:45 s/bug/but/ 02:25:34 --- quit: nighty-- (Quit: Disappears in a puff of smoke) 02:27:14 I' 02:27:44 I sometimes use GDB to debug low-level Forth code during bringup on new hardware. 02:28:07 I see. 02:28:38 It's useful for both CODE word in ITC/DTC, and even more so in subroutine threaded/native code. 02:29:19 all low-level tools more or less assume the world speaks only C ... 02:31:07 Maybe we should use a DDT-style debugger instead. It certainly doesn't assume C! 02:31:47 But no one knows about DDT (the real one from ITS) any more. 03:03:06 --- join: GeDaMo (~GeDaMo@212.225.125.110) joined #forth 03:22:48 --- quit: nighty-__ (Remote host closed the connection) 03:35:33 --- quit: rtmanpages (Ping timeout: 240 seconds) 05:37:20 --- join: ricky_ricardo (~quassel@2602:306:328f:79f0:860f:ba6a:cf34:d8de) joined #forth 05:38:44 --- part: ricky_ricardo left #forth 05:41:21 --- join: GITIB (~GiL@2a01:e0a:2a:f760:dc7b:baea:47d:57d9) joined #forth 05:42:15 hi all 05:43:42 --- join: rtmanpages (~rtmanpage@16.sub-174-204-3.myvzw.com) joined #forth 05:49:15 Hello GITIB. How's your Forth coming along? 06:06:46 I'm a bit on a break now, thing comes nicely along 06:11:03 I'm making a javascript VM, I just implemented the return stack, whitch was a huge pain, now I'm working on how to implement different running states. I am a hobbyist so I understand if it is not much interesting :) 06:14:11 --- quit: dys (Ping timeout: 240 seconds) 06:22:54 I've got few words PUSHINT, EXIT, DEFINE, ECHO, READ, OK, I can allready interpret some forth words even if, for now, I need to build them by hand in the memory, that is the next step, a compile mode 06:27:14 and I'm running TF83 on DosBox ... 06:27:30 --- join: dys (~dys@tmo-107-64.customers.d1-online.com) joined #forth 06:28:24 GITIB: Cool. Have fun! 06:29:38 I do larbs, thanks 06:33:52 I'm a bit proud I only have one if-else in all my code, which was a kind of a chalenge 06:39:31 --- quit: leaverite (Remote host closed the connection) 06:43:22 --- quit: wa5qjh (Quit: No Ping reply in 180 seconds.) 06:49:06 I expect to get some flack for this, but I find myself really missing automatic local storage from c 06:49:46 it is really, really convenient to be able to declare a local structure, populate it, and then pass its address off to a subroutine 06:50:15 and then have it cleaned up by the compiler when the function returns 06:50:38 --- join: wa5qjh (~Thunderbi@175.158.225.192) joined #forth 06:52:11 --- join: leaverite (~quassel@175.158.225.192) joined #forth 06:57:34 I'm thinking of a locals-style syntax where instead of naming input arguments, you would give it sizes and names (kind of like the structure syntax I've seen around), and when you use it then it also sets some flag so that exit and ; know to compile a cleanup call 06:58:59 : foo | 8 cells is my-local-array | ... ( or something like that ) 06:59:41 it's too bad "for" is already a word 06:59:58 "8 cells for buf" would be nice 07:00:07 and I hate to overload words in special contexts 07:09:36 : foo here x , y , z , do-stuff -12 allot ; 07:10:04 Sorry, -3 cells allot 07:10:37 Just a suggestions, not a panacea 07:15:19 --- quit: leaverite (Remote host closed the connection) 07:15:19 --- quit: wa5qjh (Remote host closed the connection) 07:34:39 yeah, that would be sufficient in very specific circumstances 07:34:49 I'm looking for something more widely usable 07:42:06 wait, for isn't used already. why did I think it was? 07:42:17 did I forget to implement some of the control flow words? 07:54:44 --- join: muzgo (~iru@200.186.58.146) joined #forth 08:42:21 It's not standardized, but I think it's well known as the FOR ... NEXT looping construct. 08:50:32 --- quit: muzgo (Ping timeout: 276 seconds) 09:01:37 --- join: muzgo (~iru@200.186.58.146) joined #forth 09:01:49 --- join: gravicappa (~gravicapp@h62-133-162-156.dyn.bashtel.ru) joined #forth 10:09:40 --- join: karswell (~user@207.91.199.146.dyn.plus.net) joined #forth 11:00:22 --- nick: iWolf -> DKordic 11:26:56 --- quit: malyn (Ping timeout: 240 seconds) 11:30:23 --- join: malyn (~malyn@unaffiliated/malyn) joined #forth 11:44:48 --- part: GITIB left #forth 11:46:04 --- quit: gravicappa (Ping timeout: 260 seconds) 11:46:46 --- quit: phadthai (Ping timeout: 248 seconds) 12:14:19 --- quit: muzgo (Ping timeout: 240 seconds) 12:14:54 --- join: muzgo (~iru@200.186.58.146) joined #forth 12:15:51 --- join: mtsd (~mtsd@h-158-174-23-206.NA.cust.bahnhof.se) joined #forth 12:24:40 --- join: phadthai (mmondor@ginseng.pulsar-zone.net) joined #forth 12:29:35 --- quit: muzgo (Ping timeout: 258 seconds) 12:49:32 --- quit: mtsd (Quit: leaving) 13:25:11 --- quit: GeDaMo (Remote host closed the connection) 13:27:05 --- quit: dys (Ping timeout: 258 seconds) 14:08:22 --- join: dys (~dys@tmo-108-210.customers.d1-online.com) joined #forth 15:07:55 --- join: wa5qjh (~Thunderbi@175.158.225.192) joined #forth 15:16:03 --- quit: rtmanpages (Ping timeout: 240 seconds) 15:25:06 --- join: mark4 (~mark4@99.30.241.51) joined #forth 15:36:01 --- join: roboguy` (~roboguy_@cpe-98-156-12-59.kc.res.rr.com) joined #forth 15:50:41 --- quit: roboguy` () 16:34:15 --- quit: Keshl_ (Quit: Konversation terminated!) 16:47:07 --- join: Keshl (~Purple@24.115.185.149.res-cmts.gld.ptd.net) joined #forth 17:23:02 --- join: rtmanpages (~rtmanpage@16.sub-174-204-3.myvzw.com) joined #forth 17:45:50 --- quit: reepca (Read error: Connection reset by peer) 17:45:59 --- join: reepca (~user@208.89.170.250) joined #forth 18:07:05 --- quit: wa5qjh (Ping timeout: 260 seconds) 18:09:22 --- join: wa5qjh (~Thunderbi@175.158.225.192) joined #forth 19:44:42 --- quit: wa5qjh (Remote host closed the connection) 20:40:09 --- quit: Bunny351 (Ping timeout: 260 seconds) 20:56:10 --- join: wa5qjh (~quassel@175.158.225.192) joined #forth 21:14:14 --- quit: reepca (Ping timeout: 260 seconds) 21:15:13 --- join: reepca (~user@208.89.170.250) joined #forth 21:30:42 --- quit: reepca (Ping timeout: 268 seconds) 21:33:29 --- join: Bunny351 (~Bunny351@p4FD2DBCA.dip0.t-ipconnect.de) joined #forth 23:51:23 --- quit: proteusguy (Quit: Leaving) 23:59:59 --- log: ended forth/17.08.04