00:00:00 --- log: started forth/10.03.31 00:01:53 --- quit: ygrek (Remote host closed the connection) 00:21:10 --- join: ygrek (debian-tor@gateway/tor-sasl/ygrek) joined #forth 00:37:24 --- quit: dinya_ (Read error: Connection reset by peer) 01:34:09 --- quit: proteusguy (Ping timeout: 248 seconds) 02:29:26 --- join: dinya_ (~Denis@188.17.82.230) joined #forth 03:29:45 --- join: Snoopy_1611 (Snoopy_161@dslb-088-068-222-033.pools.arcor-ip.net) joined #forth 03:43:19 --- quit: probonono (Ping timeout: 260 seconds) 04:17:20 --- join: probonono (~User@unaffiliated/probonono) joined #forth 04:23:21 --- join: kar8nga (~kar8nga@91.35.72-86.rev.gaoland.net) joined #forth 05:05:27 --- quit: nighty__ (Quit: Disappears in a puff of smoke) 05:11:43 --- quit: dinya_ (Read error: Connection reset by peer) 05:24:15 --- quit: grub_booter (Ping timeout: 276 seconds) 05:38:32 --- nick: KipIngram-zzzz -> KipIngram 05:49:49 --- join: grub_booter (~charlie@2002:54c5:19d5:0:21a:a0ff:fedb:cda0) joined #forth 06:01:47 --- quit: Deformative (Read error: Operation timed out) 06:59:43 --- join: Deformative (~joe@2002:43c2:b722:4:224:8cff:fe67:e2dd) joined #forth 07:12:34 --- quit: Deformative (Read error: Operation timed out) 07:15:17 --- join: Deformative (~joe@bursley-185022.reshall.umich.edu) joined #forth 07:44:09 --- quit: grub_booter (Read error: Operation timed out) 07:47:27 --- join: grub_booter (~charlie@2002:54c5:19d5:0:21a:a0ff:fedb:cda0) joined #forth 07:48:30 --- join: proteusguy (~proteusgu@110.77.145.40) joined #forth 07:50:27 --- quit: grub_booter (Read error: Operation timed out) 08:01:04 --- join: grub_booter_ (~charlie@2002:54c5:19d5:0:21a:a0ff:fedb:cda0) joined #forth 08:10:22 --- quit: ASau` (Quit: off) 08:19:08 --- quit: TreyB (Ping timeout: 240 seconds) 08:26:14 --- join: TreyB_ (~trey@74.203.168.157) joined #forth 08:39:07 --- quit: Deformative (Ping timeout: 246 seconds) 08:40:37 --- quit: Quartus` (Ping timeout: 252 seconds) 08:58:20 --- quit: kar8nga (Ping timeout: 276 seconds) 09:41:20 --- join: forther (~forther@c-98-210-250-202.hsd1.ca.comcast.net) joined #forth 10:50:26 --- quit: TreyB_ (Quit: leaving) 10:50:35 --- join: TreyB (~trey@74.203.168.157) joined #forth 11:01:30 --- join: kar8nga (~kar8nga@91.35.72-86.rev.gaoland.net) joined #forth 11:21:17 --- quit: forther (Ping timeout: 265 seconds) 11:29:24 --- join: forther (~forther@c-98-210-250-202.hsd1.ca.comcast.net) joined #forth 11:36:25 --- quit: forther (Ping timeout: 264 seconds) 11:48:23 --- join: Deformative (~joe@bursley-185022.reshall.umich.edu) joined #forth 11:50:05 --- quit: kar8nga (Remote host closed the connection) 11:59:20 --- join: tgunr (~tgunr@2001:0:53aa:64c:0:197:bd06:59f5) joined #forth 12:00:43 --- quit: Deformative (Ping timeout: 246 seconds) 12:31:35 --- join: forther (~forther@207.47.34.100.static.nextweb.net) joined #forth 12:40:50 --- join: Guthur (~Michael@host81-131-241-198.range81-131.btcentralplus.com) joined #forth 13:29:25 --- part: forther left #forth 13:36:49 --- join: Deformative (~joe@bursley-185022.reshall.umich.edu) joined #forth 13:39:29 --- join: segher (~segher@84-105-60-153.cable.quicknet.nl) joined #forth 13:45:51 --- quit: tgunr (Read error: Connection timed out) 13:46:23 --- join: tgunr (~tgunr@2001:0:53aa:64c:0:197:bd06:59f5) joined #forth 15:00:08 --- join: Al2O3 (~Al2O3@nmd.sbx11995.highlco.wayport.net) joined #forth 15:11:20 --- quit: ygrek (Ping timeout: 245 seconds) 15:13:20 --- quit: Al2O3 (Quit: thanks) 15:21:35 --- quit: qFox (Quit: Time for cookies!) 16:16:28 --- join: skas (~skas@eth488.act.adsl.internode.on.net) joined #forth 16:20:11 --- join: nighty__ (~nighty@210.188.173.245) joined #forth 17:27:04 --- quit: tgunr (Read error: Connection timed out) 17:37:19 --- join: tgunr (~tgunr@2001:0:53aa:64c:0:197:bd06:59f5) joined #forth 18:10:34 --- quit: TreyB (Ping timeout: 258 seconds) 18:10:59 --- join: TreyB (~trey@adsl-76-240-61-114.dsl.hstntx.sbcglobal.net) joined #forth 19:10:58 --- log: started forth/10.03.31 19:10:58 --- join: clog (~nef@bespin.org) joined #forth 19:10:58 --- topic: 'The Forth programming language, etc. | Logged by clog | forth.pastebin.ca | quartus.net/search | gforth: tinyurl.com/s8uho | isforth.com | ANS Standard: tinyurl.com/nx7dx | Wiki: forthfreak.net' 19:10:58 --- topic: set by tathi on [Mon Nov 30 04:40:25 2009] 19:10:58 --- names: list (clog TreyB tgunr nighty__ skas segher Deformative Guthur grub_booter_ proteusguy probonono Snoopy_1611 crc KipIngram crcx mathrick cataska gogonkt scj gnomon madwork schmx johnlunney nottwo ASau alex4nder tmitt nighty_ saper madgarden jeremy_c malyn nighty^ foxes yiyus) 20:40:01 --- quit: gogonkt (Ping timeout: 252 seconds) 20:41:39 --- join: gogonkt (~info@116.5.48.17) joined #forth 20:56:55 --- join: Al2O3 (~Al2O3@c-67-177-224-151.hsd1.co.comcast.net) joined #forth 21:11:04 Is there something wrong with my client, or has there really been no actual activity here since yesterday afternoon?? 21:11:52 Heh. 21:12:11 Ok, I saw that so I guess we're just a boring bunch. 21:12:51 Yeah, maybe. 21:13:08 this channel has large amounts of idle time 21:14:38 Indeed. 21:15:26 I was mostly just worried that I'd broken my setup. I set some filters to ignore the join / part / quit messages, and since then I'd seen... nothing. 21:15:29 But now I know all is well. 21:17:07 yup 21:17:33 I seldom chat here anymore 21:20:10 --- quit: gnomon (Ping timeout: 252 seconds) 21:20:24 --- join: gnomon (~gnomon@CPE0022158a8221-CM000f9f776f96.cpe.net.cable.rogers.com) joined #forth 21:20:42 fwiw, here's the code I wrote today: http://retroforth.com/paste/?id=2069 21:22:16 Hmmm. I'm going to have to study up on your stuff sometime - that's a really interesting mix of syntax structures. 21:22:33 --- quit: skas (Quit: Leaving) 21:22:34 my forth is continually diverging from the mainstream 21:22:42 but it works really nicely for my purposes :) 21:22:54 That's what counts. 21:23:32 I got the C emulation of my FPGA processor working nicely. My FPGA guy flys in week after next, so we should be marching it along soon. 21:28:29 crc: Hey, your web interpreter's working now. When I first tried it a while back I caught it on a bad night. 21:28:48 KipIngram: try the latest one at http://rx-core.org/jsvm 21:30:24 the one on the main site is a pretty old image+vm 21:32:21 KipIngram: it's you and Deformative who are verbose, before you there was no activity for week periods. 21:33:04 crc: Seems to work. But it doesn't seem to like spaces. 21:33:14 what does it do? 21:33:19 ASau: Glad we could liven things up. 21:33:35 crc: It seems to "shrink" the interpreter window, but doesn't print anything. 21:33:59 what browser + version and os? 21:34:20 Chrome, Ubuntu 9.10. 21:34:27 Hang on; I'll try it in FF. 21:34:34 thanks 21:35:02 Same thing. But now I see that it doesn't "shrink" the window - it scrolls the page down. 21:35:10 If I scroll back up things look ok. 21:35:21 ok 21:35:32 I'll see if I can take care of that tomorrow 21:35:37 It seems to take the space as a return - it gives me a new line and an ok. 21:36:02 retro's listener reads token by token 21:36:20 I figured that was probably by design. Anyway, cool that you put it out there like that. 21:36:32 Once I get my processor working in VHDL I'm going to post it as well. 21:37:14 --- quit: proteusguy (Ping timeout: 258 seconds) 21:37:54 Meh. 21:37:59 I'll look forward to seeing it 21:37:59 Fuck my algorithms class. 21:38:38 I am getting all sorts of stupid segfaults because I misunderstood the spec so many times and had to rewrite my implementation, but I held on to my old code because I didn't have to rewrite everything. 21:38:48 So I have parts of code from when I misunderstood still. 21:38:55 And it just causes problems everywhere. D: 21:40:00 This is called "compatibility." 21:40:55 --- quit: Guthur (Quit: Computer says no) 21:42:56 --- join: crc_ (~charlesch@71.23.210.149) joined #forth 21:43:23 --- quit: crc (Disconnected by services) 21:43:28 --- nick: crc_ -> crc 21:43:36 --- mode: ChanServ set +o crc 21:56:53 --- join: twobitsprite (~isaac@75.127.97.165) joined #forth 21:57:25 --- quit: gnomon (Ping timeout: 264 seconds) 21:57:25 I love freenode... just /join # and there you are :) 21:57:45 --- join: gnomon (~gnomon@CPE0022158a8221-CM000f9f776f96.cpe.net.cable.rogers.com) joined #forth 21:58:29 does anyone know if gforth is tail-call optimized? Or, does that question even make sense when talknig about forth? 21:58:51 I.e., assuming my function is data-stack neutral, can it recurse forever? 21:59:23 there is a word RECURSE that guarantees that will work 21:59:24 not in gforth 21:59:58 segher: yes, I know there is a word to recurse... but does it leak control-stack space with each call? 22:00:12 crc: ahh... shame... 22:00:36 twobitsprite: in my gforth install (0.7.0) a recursive function dies at 3816 tail calls 22:00:49 there is no control stack at runtime 22:01:05 damn 22:01:11 twobitsprite: it's possible to work around this 22:01:26 : foo ( n-n ) rdrop 1+ dup . recurse ; 22:01:29 0 foo 22:01:39 and i take it back, RECURSE does not guarantee not to use the return stack 22:01:42 rdrop to drop the return address after each recurse 22:01:56 works in 0.7.0 as far as I can tell 22:02:22 or rewrite your code not to use recursive calls 22:02:43 well... I'm not writing the code... I'm hoping to write genetic algorithms using forth 22:02:45 this is almost always trivial to do -- if not, you are using way too long definitions 22:03:08 : foo ( n-n ) begin 1+ dup . again ; 22:03:14 should work as well 22:03:24 i.e., randomly generated code... which is trickier with having to keep track of things like "begin ... end" 22:03:41 --- nick: KipIngram -> KipIngram-zzz 22:03:47 I was hoping to elide all control structures and just rely on recursion 22:04:07 so set your forth to use deeeeeeep stacks 22:04:10 twobitsprite: just use 'rdrop recurse' 22:04:31 see the -d and -r options to gforth 22:04:38 though returning to the caller could be problematic 22:04:38 but... does that mess up future returns? 22:04:46 right 22:07:39 I see something about "cs-pick" etc in the docs... but I'm not sure what it does 22:08:36 or... is there another forth compiler which can help me? 22:08:53 or, any other stack based language? :) 22:11:00 hmm... now that I think about it... even if I work around the loop structures, I still have nested conditionals 22:24:52 All this "tail call recursion" craze is so popular that it 22:24:52 becomes annoying. 22:25:09 twobitsprite: what is "tail call" by your opinion? 22:25:47 And more. 22:26:00 Why do you think that tail call elimination is good? 22:26:30 Have you ever tried to debug complex recursive functions? 22:37:00 And it is higly unreasonable not to use usual control structures. 22:37:09 They are more expressive than recursion. 22:59:57 --- quit: Al2O3 (Quit: thanks) 23:00:22 --- join: proteusguy (~proteusgu@58.64.85.49) joined #forth 23:04:17 --- quit: tgunr (Read error: Connection timed out) 23:27:05 --- join: zuse (~zuse@pD95135F2.dip.t-dialin.net) joined #forth 23:37:44 --- join: qFox (~C00K13S@5356B263.cable.casema.nl) joined #forth 23:39:21 --- join: kar8nga (~kar8nga@91.35.72-86.rev.gaoland.net) joined #forth 23:59:59 --- log: ended forth/10.03.31