00:00:00 --- log: started forth/17.09.02 00:04:01 --- quit: reepca (Ping timeout: 240 seconds) 00:07:54 --- join: reepca (~user@208.89.170.250) joined #forth 00:24:24 --- quit: mnemnion (Remote host closed the connection) 00:24:49 --- join: mnemnion (~mnemnion@c-73-223-86-196.hsd1.ca.comcast.net) joined #forth 00:26:18 --- quit: mnemnion (Remote host closed the connection) 00:26:24 --- join: mnemnion (~mnemnion@c-73-223-86-196.hsd1.ca.comcast.net) joined #forth 00:26:34 --- quit: mnemnion (Remote host closed the connection) 00:27:00 --- join: mnemnion (~mnemnion@c-73-223-86-196.hsd1.ca.comcast.net) joined #forth 00:31:02 --- quit: mnemnion (Ping timeout: 240 seconds) 00:35:30 --- join: mnemnion (~mnemnion@c-73-223-86-196.hsd1.ca.comcast.net) joined #forth 00:37:14 --- quit: gravicappa (Ping timeout: 260 seconds) 00:37:35 --- join: proteus-guy (~proteusgu@180.183.140.175) joined #forth 00:41:48 --- quit: mnemnion (Remote host closed the connection) 00:44:01 --- join: proteusguy (~proteus-g@180.183.140.175) joined #forth 00:44:01 --- mode: ChanServ set +v proteusguy 00:45:05 --- quit: proteusguy (Max SendQ exceeded) 00:51:47 --- join: dys (~dys@x5f71dada.dyn.telefonica.de) joined #forth 01:05:34 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 01:09:51 --- quit: mnemnion (Ping timeout: 252 seconds) 01:14:39 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 02:15:14 --- quit: mnemnion (Remote host closed the connection) 02:30:46 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 02:35:57 --- quit: mnemnion (Ping timeout: 240 seconds) 02:45:57 --- quit: ZombieChicken (Remote host closed the connection) 02:46:25 --- join: ZombieChicken (~weechat@gateway/tor-sasl/forgottenwizard) joined #forth 03:03:06 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 03:07:01 --- quit: mnemnion (Ping timeout: 240 seconds) 03:39:56 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 03:44:31 --- quit: mnemnion (Ping timeout: 264 seconds) 03:47:47 --- quit: proteus-guy (Remote host closed the connection) 04:21:20 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 04:26:22 --- quit: mnemnion (Ping timeout: 240 seconds) 05:03:03 --- quit: leaverite (Remote host closed the connection) 05:03:03 --- quit: wa5qjh (Remote host closed the connection) 05:03:53 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 05:08:01 --- quit: mnemnion (Ping timeout: 240 seconds) 05:44:51 --- quit: bedah (Ping timeout: 252 seconds) 05:57:21 --- join: bedah (~bedah@2a02:810d:243f:f584:e99d:9345:63e:8f90) joined #forth 06:13:21 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 06:14:19 --- quit: Labu (Remote host closed the connection) 06:19:50 --- quit: mnemnion (Ping timeout: 248 seconds) 06:52:06 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 06:53:23 --- join: gravicappa (~gravicapp@ppp83-237-164-35.pppoe.mtu-net.ru) joined #forth 06:56:38 --- quit: mnemnion (Ping timeout: 248 seconds) 07:28:37 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 07:34:19 --- quit: mnemnion (Ping timeout: 260 seconds) 07:35:45 --- quit: gravicappa (Ping timeout: 255 seconds) 08:07:25 --- join: Chef_Gromboli (~Chef_Grom@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 08:50:09 --- quit: Zarutian_PI (Ping timeout: 260 seconds) 08:52:15 --- join: Zarutian_PI (~3.1415@89.17.133.173) joined #forth 09:14:13 It occurs to me that stack shuffling before DO...LOOP constructs could be made easier if we split DO into two parts: the part that sets up the indices and the part that provides a backwards branch. That way we can get two stack items out of the way for free. Otherwise we have to choose between in some cases doing extra shuffling in the loop and in others having really complex loop setups. 09:45:42 --- quit: rtmanpages (Ping timeout: 248 seconds) 10:05:59 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 10:37:40 --- join: mnemnia (~mnemnion@2601:643:8102:7c95:dcc0:747f:20ff:2870) joined #forth 10:41:02 --- quit: mnemnion (Ping timeout: 240 seconds) 11:53:34 --- join: rtmanpages (~rtmanpage@98.sub-174-204-17.myvzw.com) joined #forth 11:56:46 --- join: karswell (~user@194.91.199.146.dyn.plus.net) joined #forth 12:22:23 --- join: gravicappa (~gravicapp@ppp83-237-172-71.pppoe.mtu-net.ru) joined #forth 12:42:02 --- quit: gravicappa (Ping timeout: 240 seconds) 13:00:59 --- join: fiddlerwoaroof (~fiddlerwo@unaffiliated/fiddlerwoaroof) joined #forth 14:29:59 --- quit: mnemnia (Ping timeout: 246 seconds) 14:35:48 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 14:42:39 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:28:51 --- quit: rtmanpages (Ping timeout: 240 seconds) 16:16:22 --- join: leaverite (~quassel@175.158.225.194) joined #forth 16:16:22 --- quit: leaverite (Changing host) 16:16:22 --- join: leaverite (~quassel@freebsd/user/wa5qjh) joined #forth 16:28:02 --- quit: dys (Ping timeout: 240 seconds) 17:12:09 --- join: mnemnia (~mnemnion@71.198.73.193) joined #forth 17:12:11 --- quit: mnemnion (Read error: Connection reset by peer) 17:13:34 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:486e:d75f:e3c9:607) joined #forth 17:16:22 --- quit: mnemnia (Ping timeout: 240 seconds) 17:37:42 --- join: rtmanpages (~rtmanpage@98.sub-174-204-17.myvzw.com) joined #forth 17:52:29 : nop 1 drop ; 17:53:06 : nop ; 17:53:12 : nop ; immediate 17:53:19 even better! 17:53:39 what is immediate 17:54:08 runs regardless of compile or interpret state 17:54:41 ok 17:55:22 good to know 17:56:41 nop shouldn't be immediate 17:57:40 depends on what your goal with nop is. If you want it to take up space in a definition, then it shouldn't be immediate. 17:58:13 what would be the point otherwise? 18:00:01 I dunno. Take up space in the source? I always think of a noop as being useful for its xt, not as something you directly use. 18:01:13 it doesn't take up space if it isn't compiled into words 18:01:24 Aye, I know. 18:01:48 the two big uses I see are 1. something you'd alias an immediate word to if you don't want it to do anything 18:02:10 and b) a placeholder for runtime patching 18:11:43 I see nop as a time delay. 18:16:06 I guess a do loop is time delay 18:19:34 gforth -e "time&date . . . . . . bye" 18:23:17 yeah you can use it for busy loops, but I would imagine for something like that it would be better to drop into native code because you can more easily predict clock cycles 18:27:20 ok 18:27:29 I also see utime and cputime 18:28:20 but yes nop is more like clock cycle timing. 18:38:26 forth : nop ; 18:39:04 oops wrong stream. 19:11:27 --- quit: Zarutian_PI (Ping timeout: 240 seconds) 19:14:06 --- join: Zarutian_PI (~3.1415@89.17.133.173) joined #forth 20:12:56 --- quit: Bunny351 (Ping timeout: 240 seconds) 20:13:27 --- join: Bunny351 (~Bunny351@p4FD2DD28.dip0.t-ipconnect.de) joined #forth 20:15:18 --- quit: adyer (Quit: leaving) 20:35:55 --- quit: Chef_Gromboli (Quit: Leaving) 21:30:18 --- quit: APic (Ping timeout: 246 seconds) 21:39:16 --- join: APic (~apic@apic.name) joined #forth 23:59:59 --- log: ended forth/17.09.02