00:00:00 --- log: started forth/17.09.07 00:14:19 --- join: proteusguy (~proteus-g@180.183.124.127) joined #forth 00:14:19 --- mode: ChanServ set +v proteusguy 00:48:18 --- join: igstan (~igstan@109.99.96.16) joined #forth 00:48:35 --- quit: igstan (Client Quit) 00:48:36 --- quit: dys (Ping timeout: 248 seconds) 00:59:38 --- join: dys (~dys@2003:5b:203b:100:6af7:28ff:fe06:801) joined #forth 01:23:12 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 03:48:44 --- join: igstan (~igstan@89.36.15.98) joined #forth 03:48:58 --- quit: igstan (Client Quit) 04:11:53 --- quit: nighty- (Quit: Disappears in a puff of smoke) 04:17:53 --- join: DKordic (~user@93-86-148-2.dynamic.isp.telekom.rs) joined #forth 04:27:39 --- quit: wa5qjh (Remote host closed the connection) 04:39:42 --- quit: mnemnion (Remote host closed the connection) 05:49:47 --- quit: proteusguy (Remote host closed the connection) 06:17:54 --- join: nighty- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 06:20:08 --- join: proteusguy (~proteus-g@2405:9800:bc00:58cf:a8f8:216:1483:b331) joined #forth 06:20:08 --- mode: ChanServ set +v proteusguy 07:41:54 --- join: impomatic (~impomatic@host109-149-159-12.range109-149.btcentralplus.com) joined #forth 09:40:35 --- quit: DGASAU (Read error: Connection reset by peer) 10:04:31 --- quit: dys (Ping timeout: 246 seconds) 10:06:50 --- join: DGASAU (~user@lmpc.drb.insel.de) joined #forth 10:25:02 --- quit: karswell (Remote host closed the connection) 10:26:20 --- join: karswell (~user@194.91.199.146.dyn.plus.net) joined #forth 10:52:38 --- join: mykespb (~myke@213.141.133.133) joined #forth 11:46:04 --- join: dys (~dys@tmo-113-110.customers.d1-online.com) joined #forth 12:20:20 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:88b9:c625:31fd:3f8f) joined #forth 12:32:12 --- quit: mykespb (Quit: Leaving) 14:11:18 --- quit: impomatic (Ping timeout: 248 seconds) 14:59:45 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:09:23 --- quit: dys (Ping timeout: 260 seconds) 16:13:45 --- quit: nighty- (Remote host closed the connection) 16:27:53 --- quit: mnemnion (Remote host closed the connection) 16:54:33 --- join: the_count (ac014251@gateway/web/freenode/ip.172.1.66.81) joined #forth 16:55:03 --- join: mnemnion (~mnemnion@c-73-223-86-196.hsd1.ca.comcast.net) joined #forth 16:56:52 Hello! Is there a good ic that has a forth built for it? I was looking at this: https://jeelabs.org/2015/07/22/forth-on-a-dip/ but the chip is discontinued. I'm looking for something that can stand alone on a breadboard, or something similar if nothing else is availible 16:59:48 --- quit: mnemnion (Ping timeout: 248 seconds) 17:02:58 Is anyone around? 17:06:18 --- quit: wa5qjh (Remote host closed the connection) 17:06:35 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 17:06:50 --- join: mnemnion (~mnemnion@c-73-223-86-196.hsd1.ca.comcast.net) joined #forth 17:07:19 it's a slow channel 17:07:39 not unlike your mother 17:07:52 i'm not aware of any ICs other than the greenarrays stuff that are modern and forthy 17:08:20 but others might be 17:08:28 Does greenarrays have a dev board? 17:09:03 i think so 17:10:00 it's not cheap though - 450 USD 17:10:11 It doesn't look very small either 17:10:53 What do you use around here? 17:10:56 the dev board has a spot for a small breadboard. it's not just the ic 17:11:14 zy]x[yz: so that where the name of mole-assess come from! Yer slow mother! 17:12:24 --- quit: mnemnion (Remote host closed the connection) 17:13:04 haha 17:22:08 So, no other ideas? 17:24:40 if you just want the ga144 ic you can get those too. but the eval board isn't "small" 17:29:48 --- join: nighty- (~nighty@kyotolabs.asahinet.com) joined #forth 17:34:42 --- join: mnemnion (~mnemnion@c-73-223-86-196.hsd1.ca.comcast.net) joined #forth 17:35:13 --- quit: wa5qjh (Remote host closed the connection) 17:37:39 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 17:53:58 the_count: you could put mecrisp forth on bbc:microbit 18:23:58 --- quit: mnemnion (Remote host closed the connection) 18:31:38 --- join: mnemnion (~mnemnion@c-73-223-86-196.hsd1.ca.comcast.net) joined #forth 18:36:20 --- quit: mnemnion (Ping timeout: 248 seconds) 18:38:10 Zarutian_PI: I'll look into that 18:38:53 It looks pretty basic, but it does look like you could do some pretty neat things on it, just learning 18:43:12 --- join: leaverite (~quassel@175.158.225.200) joined #forth 18:43:12 --- quit: leaverite (Changing host) 18:43:12 --- join: leaverite (~quassel@freebsd/user/wa5qjh) joined #forth 18:43:28 --- quit: the_count (Quit: Page closed) 18:50:38 --- nick: leaverite -> wa5qjh_ 19:11:05 --- join: mnemnion (~mnemnion@c-73-223-86-196.hsd1.ca.comcast.net) joined #forth 19:23:04 --- quit: mnemnion (Remote host closed the connection) 19:53:19 --- join: mnemnion (~mnemnion@c-73-223-86-196.hsd1.ca.comcast.net) joined #forth 19:57:56 --- quit: mnemnion (Ping timeout: 248 seconds) 20:03:01 --- join: mnemnion (~mnemnion@c-73-223-86-196.hsd1.ca.comcast.net) joined #forth 20:07:09 --- quit: Bunny351 (Ping timeout: 240 seconds) 20:08:03 --- quit: mnemnion (Ping timeout: 260 seconds) 20:12:20 --- quit: nighty- (Ping timeout: 248 seconds) 20:23:32 --- join: Bunny351 (~Bunny351@p4FD2D351.dip0.t-ipconnect.de) joined #forth 20:24:33 --- join: dys (~dys@tmo-107-143.customers.d1-online.com) joined #forth 20:26:14 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 20:26:31 --- join: nighty- (~nighty@210.253.246.113) joined #forth 20:39:22 --- quit: proteusguy (Remote host closed the connection) 21:00:12 --- join: proteus-guy (~proteusgu@180.183.110.36) joined #forth 21:10:20 --- quit: wa5qjh (Remote host closed the connection) 21:10:20 --- quit: wa5qjh_ (Remote host closed the connection) 21:12:25 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:25:16 --- quit: wa5qjh (Remote host closed the connection) 21:40:02 --- quit: reepca (Ping timeout: 240 seconds) 21:49:09 --- join: FatalNIX (~FatalNIX@unaffiliated/fatalnix) joined #forth 21:50:40 Hey guys! If I am tasked to create a lexical analyzer and recursive descending parser in Forth, should I be worried? 21:58:57 --- quit: ZombieChicken (Remote host closed the connection) 21:59:10 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:59:26 --- join: ZombieChicken (~weechat@gateway/tor-sasl/forgottenwizard) joined #forth 22:02:59 FatalNIX: there's a article named "let's build a compiler" and it has a forth version 22:03:02 --- join: leaverite (~quassel@175.158.225.200) joined #forth 22:03:02 --- quit: leaverite (Changing host) 22:03:02 --- join: leaverite (~quassel@freebsd/user/wa5qjh) joined #forth 22:05:48 --- nick: wa5qjh -> wa5qjh_ 22:06:19 --- nick: leaverite -> wa5qjh 22:10:46 --- join: reepca (~user@208.89.170.250) joined #forth 22:11:21 FatalNIX: I use parser combinators in forth. I can even use the unmodified boolean AND, OR, etc words to do it. The forth dictionary is one big multiway OR parser combinator and the word matching are AND parser combinators. The hyperstatic scoping of the forth dictionary is effectively the same thing as OR short circuit evaluation, etc. 22:21:32 --- quit: wa5qjh (Remote host closed the connection) 22:21:56 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 22:28:57 --- join: tartal (~tartal@109.87.232.207) joined #forth 23:12:21 --- quit: tartal (Quit: My MacBook has gone to sleep. ZZZzzz…) 23:24:42 --- quit: wa5qjh (Remote host closed the connection) 23:24:42 --- quit: wa5qjh_ (Remote host closed the connection) 23:34:05 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:39:21 --- quit: wa5qjh (Remote host closed the connection) 23:42:26 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:59:59 --- log: ended forth/17.09.07