00:00:00 --- log: started forth/15.08.12 00:01:59 mornin+ 00:05:43 --- quit: atommann (Ping timeout: 265 seconds) 00:37:16 --- join: atommann (~atommann@58.251.2.94) joined #forth 00:43:17 --- quit: MrMobius (Ping timeout: 250 seconds) 00:55:48 afternoon++ :) 00:55:53 hi 00:56:41 Mother's Day here in Thailand. 00:56:58 ok 00:57:40 I've been re-learning Haskell (not that I was ever strong at it). Remarkable language. If you appreciate the advantages of strong static compile-time type systems and enjoy forth then it is something I highly recommend. 00:58:39 The language has also evolved quite a bit to make it more practical for real-world apps since I last played with it in the early 90s. 01:00:10 Pretty much all programs work around the key data type which they call a list but you are restricted to only being able to add or remove things from the front. Sound familiar? :P 01:00:33 ya 01:00:45 fifo 01:01:26 Yep - in haskell you program with stacks but call them lists. head is the top element and tail is the entire rest of the "list". 01:01:43 ah 01:01:52 It even has a strong interpreted environment. 01:02:11 how heavy is the main haskell bin? 01:02:22 lemme see.... 01:04:59 compiler is 1.6M. 01:05:35 But that includes a lot of stuff that isn't necessary. 01:06:24 what about the shell ui? 01:07:05 so is H more like gcc or forth in how it translated? combined like stdforth or no? 01:07:30 I'm trying to figure that out. Turns out that it's a lot of tiny shell scripts that call something else with a bunch of parameters. Hard to pin down what's the minimal runtime environment. 01:08:09 k 01:08:18 well; i'm stalled on my forth 01:08:30 too much mental interference allowed 01:08:31 My guess is it's closer to gcc with some extra stuff but much much smaller. The people behind it are academics who actually hit on something very innovative and useful. 01:08:44 i have to djust my environ here to get back into it 01:08:56 kool 01:09:04 adjust 01:09:15 Been there many times.... change your environment and redirect. Good luck. 01:09:21 thanks 01:09:36 right now my next subrs are for cold and warm 01:09:55 fasm shows no current errors expcet for missing cold label/def 01:10:34 i had a thought tho on how to define cold 01:11:01 strange idea; fcator it into words, abort and (abort). 01:11:08 or one of them 01:11:57 what do you think? 01:29:56 --- join: impomatic_ (~digital_w@31.185.136.135) joined #forth 01:42:27 --- join: nighty^ (~nighty@hokuriku.rural-networks.com) joined #forth 01:57:10 --- quit: atommann (Ping timeout: 264 seconds) 02:10:10 Since I don't like resetting the stack whenever an error occurs (I like it to be explicitly requested), my implementations are pretty much independent. 02:10:55 Just remember I deal with "forthish" languages which quickly diverge from anything resembling ANS forth 02:11:06 ok 02:11:24 i'm just tryin to figer out if its a salient idea 02:13:04 Would you implement one in terms of the other? Is warm reset a subset of cold reset. In that case my answer would be yes - split them like you suggest. 02:13:25 yes 02:13:36 i am much in favor of refactoring 02:13:43 aka code lifting 02:13:56 that's why i'm adiding lispy and fpy concepts 02:14:11 for better naming of refactored code 02:14:17 makes sense to me. :) 02:14:21 sure 02:14:37 my first rant here i think was about names and symbols 02:14:43 or maybe it was in ##asm 02:14:45 i forget. 02:15:05 well, more of a diatribe than a rant. 02:15:09 it was long heh 02:15:45 fpey 02:16:15 but what i'm tryin to figer out with abort et al and cold/warm 02:16:35 is default messages when there's no current error 02:16:47 how to get a default " ok" 02:16:56 --- join: true-grue (~grue@95-27-151-212.broadband.corbina.ru) joined #forth 02:17:12 i think using fig vocabularies with runtime searching up the voc-chain would do it 02:17:30 it's a OO concept i think 02:17:56 encapulsation i think 02:18:00 or parentage 02:18:37 or maybe more like virtual or concrete procedures, defined or not, in the chain of objects (vocs) 02:25:22 --- join: impomatic (~impomatic@31.185.136.135) joined #forth 02:25:23 I think the use of stacks of vocabularies but I'd be careful about implementing stateful polymorphism with that construct. 02:56:43 --- join: scoofy (~scoofy@catv-89-135-80-2.catv.broadband.hu) joined #forth 03:07:28 --- join: atommann (~atommann@58.251.2.94) joined #forth 03:17:04 --- quit: atommann (Quit: Leaving) 04:06:41 --- join: protist (~javery@63.239.69.111.dynamic.snap.net.nz) joined #forth 04:08:24 --- join: vsg1990 (~vsg1990@cpe-67-241-148-119.buffalo.res.rr.com) joined #forth 04:34:43 --- join: Mat4 (~claude@ip5b40b95e.dynamic.kabel-deutschland.de) joined #forth 04:39:20 --- quit: Mat4 (Client Quit) 04:49:21 --- quit: xyh (Remote host closed the connection) 05:26:12 --- join: xyh (~xyh@183.11.179.129) joined #forth 06:18:37 --- quit: xyh (Remote host closed the connection) 07:01:23 --- join: zhiayang (~zhiayang@bb219-74-68-213.singnet.com.sg) joined #forth 07:15:35 protist: i wouldnt use the term 'stack' to descr a voc-chain. 07:15:58 Quiznos: did you mean to message me? 07:16:15 it can be used to quite efficiently establish data and code hiding below and super-classing above 07:16:22 protist: oop 07:16:29 but yu can respond 07:17:05 proteusguy: i wouldnt use the term 'stack' to descr a voc-chain. 07:20:15 --- part: zhiayang left #forth 07:21:25 Quiznos: voc-chain? 07:21:31 Quiznos: like invocation chain? 07:21:44 Quiznos: or in other words, function call stack? 07:22:00 Quiznos: moving from one /stack/ frame to another? 07:23:42 no, voacularies 07:23:44 fig-style 07:24:06 fig's tree of vocabularies 07:24:12 --- join: kumul (~mool@adsl-72-50-86-201.prtc.net) joined #forth 07:25:42 protist: 07:25:58 idk FIG stuff 07:26:02 :p 07:26:04 ah 07:26:14 well; it's not difficult. 07:26:46 a tree of linked lists, vocabularies are branches off the trunk 07:26:51 and words are the leaves. 07:48:08 well if the vocabularies can't nest 07:48:10 AND 07:48:22 if the vocabularies are added to the head of the list each time 07:48:25 AND 07:48:36 they are either never removed, or removed from the head 07:48:47 then yes, you could consider it a stack of lists :p 07:49:08 those are sufficient conditions, not necessary conditions, mind you 07:49:30 but that's not the FIG model 07:49:45 that's either ans or f83; where a vector is used. 07:49:59 and if a vector, then a lilmitation arbitrary. 07:54:59 --- join: johnmark_ (~johnmark@24.1.223.32) joined #forth 07:55:21 --- nick: johnmark_ -> JohnMarkM 08:00:21 --- join: xyh (~xyh@119.139.89.31) joined #forth 08:24:00 afk ttyl 08:59:27 --- quit: protist (Ping timeout: 240 seconds) 09:01:45 --- join: MrMobius (~MrMobius@h217.17.29.71.dynamic.ip.windstream.net) joined #forth 09:23:31 --- quit: darkf (Quit: Leaving) 09:31:46 --- quit: MrMobius (Ping timeout: 246 seconds) 09:35:57 --- quit: FireFly (Ping timeout: 244 seconds) 09:49:14 --- join: MrMobius (~MrMobius@h217.17.29.71.dynamic.ip.windstream.net) joined #forth 09:58:08 --- quit: kumul (Quit: Leaving) 09:58:46 --- quit: MrMobius (Ping timeout: 265 seconds) 09:59:03 --- quit: xyh (Remote host closed the connection) 10:01:28 --- join: FireFly (~firefly@firefly.xen.prgmr.com) joined #forth 10:09:56 --- join: fantazo (~fantazo@089144194098.atnat0003.highway.a1.net) joined #forth 10:20:26 --- join: kumul (~mool@adsl-64-237-237-186.prtc.net) joined #forth 10:37:27 --- quit: kumul (Ping timeout: 245 seconds) 10:56:22 --- part: impomatic_ left #forth 11:04:08 --- join: ASau (~user@176.2.108.102) joined #forth 11:58:08 --- join: bedah (~bedah@host-091-097-168-138.ewe-ip-backbone.de) joined #forth 12:16:22 --- join: Mat4 (~claude@ip5b40b95e.dynamic.kabel-deutschland.de) joined #forth 12:16:24 hello 12:27:07 hey 12:29:06 hi bluekelp 12:29:10 what's new ? 12:29:30 not much. too busy at work to play with forth :( 12:29:57 i still haven't figured out the bug in introduced in jones porting from att to intel syntax. it's been months 12:33:07 well, I can a look at it after I'm back from holiday end of next week. Probably I find the reason 12:34:49 if you want 12:35:29 that'd be great. any excuse to make progress :) 12:36:33 ok 12:46:45 --- quit: vsg1990 (Quit: What's a Quit message?) 12:56:58 --- quit: fantazo (Quit: Verlassend) 13:27:52 --- quit: nighty^ (Quit: Disappears in a puff of smoke) 13:29:54 --- join: nighty^ (~nighty@hokuriku.rural-networks.com) joined #forth 13:45:55 --- join: nisstyre (~yourstrul@li611-52.members.linode.com) joined #forth 13:54:08 --- quit: nisstyre (Changing host) 13:54:08 --- join: nisstyre (~yourstrul@oftn/member/Nisstyre) joined #forth 13:58:36 --- quit: proteusguy (Read error: Connection reset by peer) 14:00:22 --- join: MrMobius (~MrMobius@h217.17.29.71.dynamic.ip.windstream.net) joined #forth 14:15:51 --- join: proteusguy (~proteusgu@ppp-110-168-229-252.revip5.asianet.co.th) joined #forth 14:15:51 --- mode: ChanServ set +v proteusguy 14:40:57 --- quit: Mat4 (Quit: Verlassend) 15:04:41 --- quit: bedah (Quit: Ex-Chat) 15:18:32 --- quit: MrMobius (Remote host closed the connection) 15:20:10 --- join: joey_ (~joey@h217.17.29.71.dynamic.ip.windstream.net) joined #forth 15:27:18 --- join: kumul (~mool@adsl-72-50-86-73.prtc.net) joined #forth 15:43:01 --- quit: true-grue (Read error: Connection reset by peer) 15:46:49 --- quit: nighty^ (Quit: Disappears in a puff of smoke) 16:20:14 --- nick: joey_ -> MrMobius 16:37:22 --- quit: MrMobius (Ping timeout: 264 seconds) 16:58:33 --- join: joey_ (~joey@h217.17.29.71.dynamic.ip.windstream.net) joined #forth 17:30:55 --- join: vsg1990 (~vsg1990@cpe-67-241-148-119.buffalo.res.rr.com) joined #forth 17:57:31 --- quit: dzho (Ping timeout: 246 seconds) 17:59:26 --- join: dzho (~dzho@unaffiliated/dzho) joined #forth 18:01:27 --- quit: joey_ (Ping timeout: 240 seconds) 18:26:13 --- quit: gnooth (Ping timeout: 246 seconds) 18:41:58 --- quit: vsg1990 (Quit: Leaving) 18:56:13 --- join: joey_ (~joey@h217.17.29.71.dynamic.ip.windstream.net) joined #forth 19:01:34 --- join: atommann (~atommann@210.3.149.230) joined #forth 19:25:43 --- join: kumool (~mool@adsl-72-50-86-73.prtc.net) joined #forth 19:26:46 --- quit: kumul (Ping timeout: 246 seconds) 19:27:29 --- nick: joey_ -> MrMobius 19:32:41 --- quit: IRIXuser (Killed (Sigyn (Spam is off topic on freenode.))) 19:32:48 --- join: IRIXUser (~IRIX@2001:41d0:8:791d::1) joined #forth 19:33:12 --- nick: IRIXUser -> Guest81187 19:34:06 --- quit: Guest81187 (Changing host) 19:34:06 --- join: Guest81187 (~IRIX@freebsd/user/kastengraeber) joined #forth 19:34:21 --- nick: Guest81187 -> IRIXuser 20:07:17 --- join: xyh (~xyh@183.11.179.129) joined #forth 20:16:00 --- join: atommann_ (~atommann@210.3.149.230) joined #forth 20:19:48 --- quit: atommann (Ping timeout: 272 seconds) 20:38:19 --- quit: MrMobius (Ping timeout: 244 seconds) 20:39:23 --- join: MrMobius (~MrMobius@h217.17.29.71.dynamic.ip.windstream.net) joined #forth 20:51:28 --- quit: MrMobius (Ping timeout: 272 seconds) 20:53:35 --- join: MrMobius (~MrMobius@h217.17.29.71.dynamic.ip.windstream.net) joined #forth 21:37:34 --- join: darkf (~darkf___@unaffiliated/darkf) joined #forth 22:09:55 --- join: atommann__ (~atommann@210.3.149.230) joined #forth 22:13:06 --- quit: atommann_ (Ping timeout: 256 seconds) 22:20:05 --- quit: ASau (Ping timeout: 244 seconds) 23:15:21 --- join: atommann_ (~atommann@58.251.2.94) joined #forth 23:18:53 --- quit: atommann__ (Ping timeout: 252 seconds) 23:26:08 --- join: kumul (~mool@adsl-72-50-86-73.prtc.net) joined #forth 23:29:10 --- quit: kumool (Ping timeout: 272 seconds) 23:59:59 --- log: ended forth/15.08.12