00:00:00 --- log: started forth/18.03.19 00:41:35 --- quit: jn__ (Ping timeout: 240 seconds) 00:53:59 --- join: jn__ (~nope@aftr-88-153-6-235.unity-media.net) joined #forth 00:59:42 --- join: Mat4 (~yaaic@x59cc8a8a.dyn.telefonica.de) joined #forth 01:01:18 --- part: Mat4 left #forth 01:15:31 --- quit: jn__ (Ping timeout: 256 seconds) 01:20:19 --- quit: dys (Ping timeout: 240 seconds) 01:21:44 --- join: dys (~dys@tmo-098-108.customers.d1-online.com) joined #forth 01:31:17 forth!! 01:31:21 getn the job done! 01:32:19 --- join: jn__ (~nope@aftr-88-153-6-235.unity-media.net) joined #forth 01:38:11 --- quit: jn__ (Ping timeout: 256 seconds) 01:43:20 --- join: jn__ (~nope@aftr-88-153-6-235.unity-media.net) joined #forth 01:59:56 --- quit: dys (Ping timeout: 260 seconds) 02:07:23 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 02:26:03 --- join: proteusguy (~proteusgu@14.207.104.95) joined #forth 02:26:03 --- mode: ChanServ set +v proteusguy 02:26:59 --- join: mtsd (~mtsd@77.110.61.100) joined #forth 02:28:49 --- quit: proteusguuy (Ping timeout: 256 seconds) 02:35:11 --- quit: dograt_ (Quit: No Ping reply in 180 seconds.) 02:36:20 --- join: dograt (~dograt@unaffiliated/dograt) joined #forth 02:40:14 --- join: ITBC2Sericnoan (~yqrwo@46.8.126.237) joined #forth 02:40:15 --- quit: ITBC2Sericnoan (Client Quit) 03:35:29 --- quit: Darksecond (Read error: Connection reset by peer) 03:38:42 --- join: Darksecond (~darksecon@a82-94-53-70.adsl.xs4all.nl) joined #forth 04:03:15 --- quit: dddddd (Ping timeout: 256 seconds) 04:03:51 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 04:10:30 --- quit: nighty- (Quit: Disappears in a puff of smoke) 04:15:12 forth makes me think 04:15:17 dangerous 04:29:24 --- quit: wa5qjh (Remote host closed the connection) 05:41:21 --- quit: mtsd (Quit: Leaving) 07:11:20 --- join: ncv (~neceve@unaffiliated/neceve) joined #forth 08:14:19 --- quit: dddddd (Ping timeout: 240 seconds) 08:15:08 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 10:37:11 anyone here a bit familiar with DCPU? If so do you know of any real MCU that has similiar discoverability or runtime enumeration of I/O devices/ports? 10:56:17 --- join: dys (~dys@tmo-103-30.customers.d1-online.com) joined #forth 11:10:31 --- quit: dddddd (Ping timeout: 256 seconds) 11:11:10 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 11:57:18 --- quit: ncv (Ping timeout: 256 seconds) 12:01:03 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 12:47:22 --- quit: whisky (Quit: WeeChat 2.0.1) 13:09:43 --- quit: Gromboli (Quit: Leaving) 13:10:04 --- join: gravicappa (~gravicapp@ppp83-237-169-136.pppoe.mtu-net.ru) joined #forth 13:30:19 --- quit: gravicappa (Ping timeout: 240 seconds) 14:55:21 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 14:56:56 --- join: wa5qjh (~quassel@175.158.225.221) joined #forth 14:56:56 --- quit: wa5qjh (Changing host) 14:56:56 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 15:22:57 Someone asked for some more substantial examples of fifo based forth. Here's some sixel graphics in mecrisp-stellaris forth: https://hub.darcs.net/pointfree/mecrisp-fifos/browse/sixels.txt 15:25:02 All I need to convert stack based words to fifo based words is : >q depth 1- -roll ; \ https://hub.darcs.net/pointfree/mecrisp-fifos/browse/fifos.txt 15:27:20 How about a little sixel oscope display from an mcu adc? 15:29:44 yeah, I would like to see that 15:50:46 is "over over" probably the most efficient 2dup implementation in any given forth 16:00:23 WilhelmVonWeiner: depends if the datastack is in the same memory as the rest of the program and data or not. 16:09:44 --- quit: EvanCarroll (Ping timeout: 264 seconds) 16:35:14 WilhelmVonWeiner: if it is say on 386 using BP and SP for data and return stack pointers then a code word that just copied the top two cells of the data stack into the next two cells above then that would be more efficient 16:36:08 WilhelmVonWeiner: but if you are keeping the code words to absolute minium, say for just 32 primitives then : 2dup over over ; is indeed the most efficient. 17:13:27 --- join: EvanCarroll (~ecarroll@rrcs-71-41-192-130.sw.biz.rr.com) joined #forth 17:25:49 --- quit: EvanCarroll (Ping timeout: 240 seconds) 17:42:37 --- join: uknanooq (~cxotp@36.72.61.6) joined #forth 17:42:39 --- quit: uknanooq (Client Quit) 17:44:06 --- join: nighty- (~nighty@kyotolabs.asahinet.com) joined #forth 18:52:43 pointfree: I guess I'm a bit confused still - is the idea to sometimes treat it like a fifo and sometimes like a stack? sixels.txt also doesn't seem to use any of the fifo functionality... 19:50:31 --- quit: dys (Ping timeout: 248 seconds) 20:49:04 --- join: smokeink (~spkp@185.134.120.54) joined #forth 21:03:54 --- quit: Gromboli (Quit: Leaving) 21:18:07 how ez is it to get environmental vars through cgi to forth? 21:18:19 how hard to store data to disk? 21:18:23 or better to leave in ram? 21:18:25 hmm 21:18:46 or can you divide the data in to like ram stuff which is static and then some disk stuff for what really need sto be saved 22:06:48 --- quit: dddddd (Remote host closed the connection) 22:07:55 --- quit: smokeink (Remote host closed the connection) 22:13:48 --- join: smokeink (~smokeink@59-125-28-152.HINET-IP.hinet.net) joined #forth 23:11:54 --- quit: smokeink (Remote host closed the connection) 23:34:18 --- join: dys (~dys@tmo-112-186.customers.d1-online.com) joined #forth 23:39:04 --- join: smokeink (~smokeink@59-125-75-78.HINET-IP.hinet.net) joined #forth 23:59:59 --- log: ended forth/18.03.19