00:00:00 --- log: started forth/12.04.20 01:33:32 --- quit: MrBusiness (Quit: Leaving) 01:51:34 --- join: mrout (~miles.rou@203-97-127-101.cable.telstraclear.net) joined #forth 01:51:34 --- mode: ChanServ set +v mrout 01:51:40 THIS LANGUAGE IS FUCKING AMAZING 01:51:58 I just thought I should put that out there 02:04:42 --- join: ttmrichter (~ttmrichte@58.55.124.246) joined #forth 02:04:42 --- mode: ChanServ set +v ttmrichter 02:05:45 --- nick: mrout -> mrout|brb 02:06:46 --- nick: mrout|brb -> mrout 02:41:52 mrout: indeed it is 02:44:27 It is just amazing 02:44:41 Everything's a word 02:44:43 I love it 02:45:11 I'm reading Thinking Forth by Leo Brodie and I just finished Starting Forth by Leo Brodie. Great books, great language, just absolutely awesome 02:45:16 Anyone got any tips? 04:21:38 --- quit: impomatic (Quit: impomatic) 04:35:25 Anyone at all got tips? 04:35:28 DocPlatypus? 04:35:57 those are both good reads 04:36:51 Tips on using forth? 04:41:11 --- quit: karswell (Ping timeout: 260 seconds) 05:02:04 --- nick: mrout -> mrout|away 05:33:05 --- nick: mrout|away -> mrout 05:35:32 --- nick: mrout -> mrout|away 05:38:22 --- quit: mrout|away () 05:38:46 --- join: karswell (~coat@93-97-29-243.zone5.bethere.co.uk) joined #forth 05:38:46 --- mode: ChanServ set +v karswell 06:05:26 ahh, young love 06:35:00 Isn't that generally called "infatuation" kulp? 06:47:50 --- join: nighty- (~nighty@static-68-179-124-161.ptr.terago.net) joined #forth 06:47:50 --- mode: ChanServ set +v nighty- 06:52:04 usually, but when you are seeing it in others it is kinder to call it young love, i think ;) 06:53:38 --- quit: segher (Ping timeout: 265 seconds) 07:00:44 --- join: segher (~segher@5ED3C8DF.cm-7-4d.dynamic.ziggo.nl) joined #forth 07:00:44 --- mode: ChanServ set +v segher 07:00:45 Heh. OK, good point, kulp. 07:01:10 Still, the first time people see a non-standard paradigm is usually a love affair. 07:01:18 (Sometimes a very brief one, mind, but still...) 07:05:28 true. in fact that's what i meant to imply, more than that it was properly "love" 07:06:32 i myself am really rather new to forth, so i must watch myself for unwarranted snootiness :) 07:10:05 --- quit: DGASAU (Ping timeout: 264 seconds) 07:14:01 --- quit: kulp (Quit: Ping timeout (-2147483648 seconds)) 07:14:28 --- join: kulp (~kulp@rox.li) joined #forth 07:14:28 --- mode: ChanServ set +v kulp 07:14:36 --- nick: kulp -> Guest11896 07:15:21 --- quit: Guest11896 (Changing host) 07:15:22 --- join: Guest11896 (~kulp@unaffiliated/kulp) joined #forth 07:15:22 --- mode: asimov.freenode.net set +v Guest11896 07:15:41 --- nick: Guest11896 -> kulp 07:41:43 kulp: I've got too many years and languages under my belt to be snooty about any one of them. 07:42:43 ttmrichter: good :) i'm still a young whippersnapper, but i try to remind myself of that fact at least. 07:43:05 --- join: impomatic (~digital_w@87.114.80.238) joined #forth 07:43:05 --- mode: ChanServ set +v impomatic 07:43:25 What experience have you got, if you don't mind? 07:46:02 i started with QBASIC back in about 1993 ; fortunately i didn't completely poison my mind. worked through very basic x86 assembly and C ; worked with C#.NET in an internship, Java in uni ; but almost all of my full-time professional experience has been in C and x86-64 asm 07:47:17 i'm interested in forth specifically to bring up a CPU i've designed and am implementing in a spartan6. have an interpreter (ITC) written, but not a compiler. 07:54:56 (have to mend my linker before i can finish the forth compiler) 07:55:44 (also when i say full-time professional, that amounts to a little over three years now) 07:55:50 you ? 08:02:01 --- join: DGASAU (~user@91.218.144.129) joined #forth 08:02:01 --- mode: ChanServ set +v DGASAU 08:17:06 --- quit: DGASAU (Remote host closed the connection) 08:18:04 --- join: DGASAU (~user@91.218.144.129) joined #forth 08:18:05 --- mode: ChanServ set +v DGASAU 08:23:25 kulp: First "professional" programming gig in '82 writing a program that tracked cheque bouncers. 08:23:49 Started on Commodore 8032s and a TRS-80 Model II. 08:24:13 Quickly moved to "Big Iron" (not really, but PDP-11s and PDP-8s) in university. 08:24:27 Then a chequered career ranging from embedded systems to PKI. 08:32:33 ttmrichter: aha. have you used forth in a professional context primarily, or hobbyist ? 08:38:24 kulp: Primarily as a hobbyist. Peripherally in an embedded system. A telephony card with multiple DSPs used an HC11 for switching and that was done in Forth. A minor program, though. 08:40:28 interesting. i like forth conceptually, but unlike our enthusiastic friend, i don't think i would have pursued it for its own sake if not for the ease of implementation on this new platform 08:40:41 --- quit: impomatic (Ping timeout: 264 seconds) 08:40:44 i'm already becoming too lazy to learn new tools unless i can see significant advantage :P 08:44:24 --- join: impomatic (~digital_w@87.113.136.141) joined #forth 08:44:24 --- mode: ChanServ set +v impomatic 08:49:21 kulp: I'm somewhat of a language junkie myself. I like learning them for the different perspectives on programming they give. 08:49:29 * ttmrichter is learning Mercury right now. 08:49:45 The things I like Forth best for are: 08:50:20 1. Ease of implementation. If you've written a decently-portable (albeit not very performant) Forth, moving it to a new platform is a weekend's work. 08:50:53 2. When dealing with new hardware (like a new processor or development board or the like) nothing I've found beats Forth for exploratory programming down to the metal. 08:51:08 3. Compactness. 08:51:49 it's certainly a lot easier to implement than the C compiler i started years ago :P 08:52:15 maybe i could implement my C compiler in forth ;) 08:55:53 That would be funny at some level. 08:56:08 Especially if the C compiler generated Forth code. :) 08:56:42 i don't think in forth yet, so i think that would be even more of a disaster than my current compiler :) 09:01:51 --- join: Kumul (~Kumul@adsl-72-50-64-45.prtc.net) joined #forth 09:01:51 --- mode: ChanServ set +v Kumul 09:10:32 --- quit: ttmrichter (Quit: Leaving) 09:14:21 There is LCC port to SP-Forth. 09:14:29 Not that it is much useful. 09:15:20 As for the ease of implementation, counter machine is even easier to implement. 09:15:39 counter machine ? 09:15:44 but is it at all pleasant to use ? 09:16:10 If you find Forth pleasant to use, you may find it pleasant too. 09:17:11 well it seems a counter machine's ability to abstract complexity would be rather more limited than forth's 09:17:45 So what? 09:17:52 It is easy to implement! 09:18:20 i think the point is that there is a balance, and that ease of implementation is important 09:18:24 not that it is all-important. 09:18:47 it is easy to implement a one-instruction-set computer, too 09:19:06 however this is not an interesting platform for application development. 09:37:43 --- quit: nighty- (Remote host closed the connection) 09:39:05 --- join: nighty^ (~nighty@static-68-179-124-161.ptr.terago.net) joined #forth 09:39:05 --- mode: ChanServ set +v nighty^ 09:58:17 --- quit: nighty^ (Remote host closed the connection) 09:58:44 --- quit: segher (Quit: This computer has gone to sleep) 10:01:36 --- join: nighty^ (~nighty@static-68-179-124-161.ptr.terago.net) joined #forth 10:01:36 --- mode: ChanServ set +v nighty^ 10:03:08 --- join: segher (~segher@5ED3C8DF.cm-7-4d.dynamic.ziggo.nl) joined #forth 10:03:09 --- mode: ChanServ set +v segher 10:06:29 --- quit: segher (Client Quit) 10:10:04 --- join: segher (~segher@5ED3C8DF.cm-7-4d.dynamic.ziggo.nl) joined #forth 10:10:05 --- mode: ChanServ set +v segher 10:20:33 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 10:20:33 --- mode: ChanServ set +v MayDaniel 13:26:09 --- join: MrBusiness (~MrBusines@184.99.7.19) joined #forth 13:26:09 --- mode: ChanServ set +v MrBusiness 13:34:40 Are the Forth-77 / Forth-78 standards available anywhere online? 14:24:54 --- quit: MayDaniel (Read error: Connection reset by peer) 15:05:11 --- quit: nighty^ (Ping timeout: 276 seconds) 15:07:23 --- join: nighty^ (~nighty@static-68-179-124-161.ptr.terago.net) joined #forth 15:07:23 --- mode: ChanServ set +v nighty^ 15:20:15 No. 15:46:36 :-( 16:01:52 --- part: impomatic left #forth 16:10:03 --- quit: nighty^ (Remote host closed the connection) 17:00:29 --- join: ttmrichter (~ttmrichte@61.184.206.142) joined #forth 17:00:39 --- mode: ChanServ set +v ttmrichter 17:04:10 trust ASau, he has read the entire internet 17:59:17 --- join: nighty^ (~nighty@69-165-220-105.dsl.teksavvy.com) joined #forth 17:59:17 --- mode: ChanServ set +v nighty^ 19:12:50 --- quit: Kumul (Ping timeout: 276 seconds) 19:31:34 --- join: Kumul (~Kumul@cvx-ppp-66-50-147-89.coqui.net) joined #forth 19:31:35 --- mode: ChanServ set +v Kumul 21:50:48 --- quit: ttmrichter (Ping timeout: 252 seconds) 22:09:24 --- join: ttmrichter (~ttmrichte@58.55.124.247) joined #forth 22:09:25 --- mode: ChanServ set +v ttmrichter 23:36:00 --- quit: Kumul (Quit: gone) 23:59:59 --- log: ended forth/12.04.20