00:00:00 --- log: started forth/16.07.08 00:29:01 --- quit: ASau (Ping timeout: 264 seconds) 00:38:41 --- quit: neceve (Quit: Leaving) 00:41:24 --- join: neceve (~neceve@unaffiliated/neceve) joined #forth 00:47:31 --- join: true-grue (~true-grue@176.14.216.104) joined #forth 00:58:42 --- join: real-grue (~true-grue@176.14.216.104) joined #forth 01:02:44 --- quit: true-grue (Ping timeout: 260 seconds) 01:03:51 --- quit: the_cuckoo (Ping timeout: 272 seconds) 01:12:36 --- quit: real-grue (Read error: Connection reset by peer) 01:13:01 --- join: real-grue (~true-grue@176.14.216.104) joined #forth 01:43:51 --- join: the_cuckoo (~charlie@213-132-145-246.access.telenet.be) joined #forth 01:52:25 --- quit: the_cuckoo (Ping timeout: 240 seconds) 02:25:43 --- join: the_cuckoo (~charlie@213-132-145-246.access.telenet.be) joined #forth 03:19:26 --- quit: wa5qjh (Read error: Connection reset by peer) 03:20:21 --- join: wa5qjh (~Thunderbi@203.111.224.35) joined #forth 03:26:36 --- join: leaverite (~Thunderbi@203.111.224.60) joined #forth 03:28:08 --- quit: wa5qjh (Ping timeout: 252 seconds) 03:28:08 --- nick: leaverite -> wa5qjh 03:48:38 --- quit: nighty (Quit: Disappears in a puff of smoke) 04:18:15 --- join: the_cuckoo1 (~charlie@d51a50ae9.access.telenet.be) joined #forth 04:21:25 --- quit: the_cuckoo (Ping timeout: 240 seconds) 04:35:56 --- quit: neceve (Remote host closed the connection) 04:37:27 --- join: nighty (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 05:32:07 --- quit: wa5qjh (Remote host closed the connection) 05:32:36 --- join: wa5qjh (~Thunderbi@203.111.224.60) joined #forth 08:00:06 --- join: opollen (~opollen@50.246.37.211) joined #forth 08:11:45 --- quit: dram (Quit: dram) 08:14:41 --- quit: opollen (Read error: Connection reset by peer) 08:26:47 --- join: karswell (~user@100.29.90.146.dyn.plus.net) joined #forth 08:40:52 --- join: neceve (~quassel@unaffiliated/neceve) joined #forth 08:41:26 --- quit: neceve (Client Quit) 08:42:31 --- join: neceve (~quassel@unaffiliated/neceve) joined #forth 08:51:07 --- join: dys` (~user@2003:5b:203b:100:6af7:28ff:fe06:801) joined #forth 10:16:45 --- quit: dys` (Ping timeout: 272 seconds) 10:16:46 --- join: bedah (~bedah@dyndsl-091-248-008-101.ewe-ip-backbone.de) joined #forth 10:25:43 --- join: actual-grue (~true-grue@176.14.216.104) joined #forth 10:29:22 --- quit: real-grue (Ping timeout: 276 seconds) 11:29:17 --- join: DKordic` (~user@178-221-28-197.dynamic.isp.telekom.rs) joined #forth 11:29:50 --- quit: DKordic (Remote host closed the connection) 11:39:43 --- nick: DKordic` -> DKordic 12:09:42 --- quit: wa5qjh (Remote host closed the connection) 12:21:39 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 12:32:28 --- join: Kumool (~kumool@adsl-64-237-237-178.prtc.net) joined #forth 12:33:09 --- quit: Kumool (Read error: Connection reset by peer) 12:37:40 --- join: ASau (~user@netbsd/developers/asau) joined #forth 12:46:07 --- join: true-grue (~true-grue@176.14.216.104) joined #forth 12:49:07 --- quit: actual-grue (Ping timeout: 276 seconds) 13:00:16 --- join: Kumool (~kumool@adsl-64-237-232-172.prtc.net) joined #forth 13:05:17 --- quit: neceve (Ping timeout: 258 seconds) 13:10:04 haha. lulz. i'm going to grab some popcorn and watch :) 13:10:27 @here - has anyone managed to snag a CHIP and install a bare metal forth on it yet? 13:10:56 i'm still holding on to my dream of getting to play with a small embedded forth on modern hardware 13:11:32 Me too. 13:11:56 Install which implementation? 13:12:56 ideally a custom-made one. default CHIP ships with Linux but i want to touch the actual hardware and twiddle bits and IO pins 13:13:19 i think the most likely path to success for me is amforth or whatever the other Atmel based one was 13:13:33 alas, have not had time to re-flash my arduino yet to try it out 13:25:40 :) I plan to do 3 Instruction Forth for AVR as a first step. 13:32:42 --- quit: bedah (Quit: Ex-Chat) 13:34:45 in theory i guess it's a neat idea but it doesn't seem "forthy" enough for me. that's just my pref. i guess hosted forth has been a thing for a while. 13:34:58 just doesn't match my mental image of what a "true" forth is 13:35:21 or maybe you're talking about something else? 13:36:37 I am not following. As if some messages are lost. What is not forthy enough? Hosted Forth? 13:37:11 yeah. to me it doesn't "seem" like a true forth. though i know it's been (?) a mainstay for a while 13:37:36 I agree. 13:37:38 i'll backup - what do you mean by a 3 instruction forth? 13:38:10 http://utoh.org/3ins4th.html 13:38:32 `@', `!' and `execute'. 13:39:45 To best of my knowledge it is the simplest Tethered Forth. 13:40:09 that's the word i was looking for - tethered 13:40:23 i love simple things. i guess i should give this a try first. 13:41:01 especially since my attempts at asm programming tend to break down or get buggy before i get to a working double-interpreter system 13:57:46 oh. colorforth website is a "under construction" page now. CM may finally be calling it quits? 16:03:30 --- quit: true-grue (Read error: Connection reset by peer) 16:21:41 --- quit: Zarutian (Quit: Zarutian) 16:23:29 --- quit: karswell (Remote host closed the connection) 17:50:32 --- quit: groovy2shoes (Ping timeout: 250 seconds) 18:21:42 --- join: dram (~Thunderbi@112.65.46.78) joined #forth 19:04:27 --- quit: APic (Ping timeout: 246 seconds) 19:07:39 --- quit: ASau (Read error: Connection reset by peer) 19:13:42 --- quit: Kumool (Read error: Connection reset by peer) 19:33:23 --- quit: reepca (Read error: No route to host) 19:34:32 --- join: reepca (~user@184.52.15.40) joined #forth 21:06:23 --- join: nal (~nal@adsl-64-237-232-172.prtc.net) joined #forth 22:18:44 --- quit: nal (Remote host closed the connection) 22:28:33 --- join: nal (~nal@adsl-64-237-232-172.prtc.net) joined #forth 22:31:01 --- join: neceve (~quassel@unaffiliated/neceve) joined #forth 22:51:00 --- quit: neceve (Remote host closed the connection) 23:00:50 --- join: neceve (~neceve@unaffiliated/neceve) joined #forth 23:59:59 --- log: ended forth/16.07.08