00:00:00 --- log: started forth/10.06.24 00:04:44 --- join: ASau (~user@77.246.230.155) joined #forth 00:08:29 --- quit: malyn (Quit: Disconnecting from stoned server.) 00:08:43 --- join: malyn (~malyn@unaffiliated/malyn) joined #forth 01:45:38 --- join: H4ns (~Hans@p579F87EE.dip.t-dialin.net) joined #forth 01:45:56 --- part: H4ns left #forth 01:53:40 --- join: sanjoyd (~sanjoyd@unaffiliated/sanjoyd) joined #forth 02:58:48 --- quit: gnomon (Ping timeout: 240 seconds) 02:59:08 --- join: gnomon (~gnomon@CPE0022158a8221-CM000f9f776f96.cpe.net.cable.rogers.com) joined #forth 04:52:16 --- quit: sanjoyd (Ping timeout: 252 seconds) 05:18:57 --- join: kar8nga (~kar8nga@91-114-230-185.adsl.highway.telekom.at) joined #forth 05:25:15 --- quit: gnomon (Ping timeout: 240 seconds) 05:25:30 --- join: gnomon (~gnomon@CPE0022158a8221-CM000f9f776f96.cpe.net.cable.rogers.com) joined #forth 05:29:00 --- join: nighty^ (~nighty@x122091.ppp.asahi-net.or.jp) joined #forth 05:53:54 --- quit: gnomon (Ping timeout: 258 seconds) 05:54:11 --- join: gnomon (~gnomon@CPE0022158a8221-CM000f9f776f96.cpe.net.cable.rogers.com) joined #forth 06:53:16 --- quit: gnomon (Ping timeout: 252 seconds) 06:53:35 --- join: gnomon (~gnomon@CPE0022158a8221-CM000f9f776f96.cpe.net.cable.rogers.com) joined #forth 06:57:36 --- quit: kar8nga (Read error: Connection reset by peer) 06:57:47 --- join: kar8nga (~kar8nga@93-82-74-186.adsl.highway.telekom.at) joined #forth 07:08:15 --- quit: kar8nga (Ping timeout: 260 seconds) 08:23:03 --- quit: gnomon (Ping timeout: 260 seconds) 08:23:22 --- join: gnomon (~gnomon@CPE0022158a8221-CM000f9f776f96.cpe.net.cable.rogers.com) joined #forth 08:43:19 --- quit: ASau (Quit: ERC Version 5.3 (IRC client for Emacs)) 09:11:25 --- join: kar8nga (~kar8nga@91-115-218-127.adsl.highway.telekom.at) joined #forth 09:13:02 --- quit: nighty^ (Ping timeout: 245 seconds) 09:14:24 --- join: nighty^ (~nighty@x122091.ppp.asahi-net.or.jp) joined #forth 09:25:31 --- quit: nighty^ (Ping timeout: 272 seconds) 09:26:13 --- join: nighty^ (~nighty@x122091.ppp.asahi-net.or.jp) joined #forth 10:03:43 --- quit: nighty^ (Ping timeout: 260 seconds) 10:04:57 --- join: nighty^ (~nighty@x122091.ppp.asahi-net.or.jp) joined #forth 10:09:35 --- quit: gnomon (Ping timeout: 240 seconds) 10:10:20 --- join: gnomon (~gnomon@CPE0022158a8221-CM000f9f776f96.cpe.net.cable.rogers.com) joined #forth 10:17:15 --- quit: nighty^ (Ping timeout: 260 seconds) 10:18:25 --- join: nighty^ (~nighty@x122091.ppp.asahi-net.or.jp) joined #forth 10:25:12 --- join: qFox (~C00K13S@5356B263.cable.casema.nl) joined #forth 10:32:35 --- join: ASau (~user@83.69.227.32) joined #forth 11:06:35 --- quit: nighty^ (Ping timeout: 248 seconds) 11:07:52 --- join: nighty^ (~nighty@x122091.ppp.asahi-net.or.jp) joined #forth 12:47:28 --- quit: kar8nga (Remote host closed the connection) 13:12:02 --- quit: segher (Quit: This computer has gone to sleep) 13:24:26 --- join: segher (~segher@84-105-60-153.cable.quicknet.nl) joined #forth 13:42:28 --- join: Judofyr (~judofyr@cC694BF51.dhcp.bluecom.no) joined #forth 13:42:48 anyone online tonight? 13:43:15 I'm wondering how you would write a Forth for a micro-controller… 13:58:27 --- quit: gnomon (Ping timeout: 260 seconds) 13:58:51 --- join: gnomon (~gnomon@CPE0022158a8221-CM000f9f776f96.cpe.net.cable.rogers.com) joined #forth 14:08:22 --- quit: nighty^ (Ping timeout: 260 seconds) 14:09:21 --- join: nighty^ (~nighty@x122091.ppp.asahi-net.or.jp) joined #forth 14:14:32 Judofyr: as usual. 14:14:35 Why? 14:15:44 I'm just used to the "compile file at host and then transfer it to the controller" 14:15:56 but Forth seems very focused on the REPL idea 14:16:25 Well... 14:16:28 Not at all. 14:16:41 Nothing stops you from sending source or even preparsed source. 14:17:24 like, sending them over serial connection? 14:17:30 Yes. 14:18:05 But nothing stops you from doing the same compilation step as usual. 14:18:15 but wouldn't that mean I would have to do it every time I (re)boot the machine? 14:19:36 well, I've just read through some implementing Forth guides, and wondered how writing a Forth compiler works with IMMEDIATE code 14:20:05 Well... 14:20:19 That's tricky. 14:20:49 One way is to maintain host words that do the job. 14:21:07 E.g. you maintain COMPILER wordlist and TARGET wordlist. 14:21:57 it just feels so … non-Forth 14:22:10 but I don't even know Forth, so what do I know? :P 14:23:23 Cross-building is advanced topic. 14:23:39 Well... Writing cross-compiler is advanced topic. 14:23:55 More advanced than writing compiler which is advanced topic either. 14:26:09 --- quit: qFox (Read error: Connection reset by peer) 14:26:28 Forth seems very interesting for embedded programming (since it's so low level), so I think it's a little weird that compiling should such a big deal 14:26:43 It isn't big deal. 14:27:36 well, it's certainly not as elegant as the rest of Forth 14:28:11 (in my opinion) 14:28:13 It isn't. 14:29:00 --- quit: nighty^ (Ping timeout: 265 seconds) 14:30:09 --- join: nighty^ (~nighty@x122091.ppp.asahi-net.or.jp) joined #forth 14:30:18 I'm goind off-line. 14:30:21 Good night. 14:30:52 good night! 14:30:55 and thanks for the help :) 16:00:20 --- quit: nighty^ (Ping timeout: 258 seconds) 17:50:58 --- quit: Judofyr (*.net *.split) 17:52:12 --- join: Judofyr (~judofyr@cC694BF51.dhcp.bluecom.no) joined #forth 17:52:15 --- quit: yiyus (Ping timeout: 240 seconds) 18:14:29 --- join: yiyus (~124271242@je.je.je) joined #forth 18:29:46 --- quit: gnomon (Ping timeout: 240 seconds) 18:30:02 --- join: gnomon (~gnomon@CPE0022158a8221-CM000f9f776f96.cpe.net.cable.rogers.com) joined #forth 19:49:53 --- join: codemonsta (~codemonst@99-4-177-176.lightspeed.gnvlsc.sbcglobal.net) joined #forth 19:50:07 is forth homoiconic? 19:56:22 codemonsta, no. The data structure with which Forth is most often associated is the stack, whereas programs are stereotypically represented as linked lists of interleaved execution tokens and machine code (though almost every real Forth system uses a more efficient program representation internally). 19:57:07 codemonsta, there are homoiconic concatenative languages, but they tend to be either research oriented or toys, like Joy, Stevan Apter's XY, and so on. 19:58:04 Also doublec's CF, which I believe is a more pragmatic derivative of XY. 19:59:48 I would send you a link to the mailing list, but I'm failing at digging up a link. Let me check some actual message bodies, there might be something in the footers. 20:33:52 --- quit: yiyus (Ping timeout: 252 seconds) 20:35:59 --- join: yiyus (~124271242@je.je.je) joined #forth 21:16:20 --- join: kar8nga (~kar8nga@91-114-224-77.adsl.highway.telekom.at) joined #forth 21:19:17 --- quit: gogonkt (Ping timeout: 240 seconds) 21:20:35 --- join: gogonkt (~info@113.69.44.38) joined #forth 21:35:25 --- quit: crc (Ping timeout: 240 seconds) 21:36:37 --- join: crc (~charlesch@184.77.185.20) joined #forth 23:00:40 --- join: bjorkintosh (48d582f0@gateway/web/freenode/ip.72.213.130.240) joined #forth 23:01:06 --- part: bjorkintosh left #forth 23:03:01 --- quit: ASau (Quit: off) 23:05:24 Judofyr: you might look at amforth for an example of a microcontroller forth that has a repl. as you define words they are written to flash storage & so persist through reboots 23:06:41 Judofyr: the core system is assembled on a host& then transferred to the embedded device & then further development can happen "in system" 23:11:46 --- quit: Judofyr (Remote host closed the connection) 23:54:39 --- join: ASau (~user@77.246.230.77) joined #forth 23:59:59 --- log: ended forth/10.06.24