00:00:00 --- log: started forth/02.01.18 00:00:14 for next.. FOR BACK, FOR LEFT, FOR TURN, FOR BLAH, FOR LAH 00:00:57 begin >r ....... r> 1- 0= until ; 00:01:13 for is just a >r 00:01:32 next is a r> -1 dup 0= while r> repeat drop 00:01:46 erm make that a ?dup =0 until 00:02:00 erm while r> repeat 00:02:04 heh 00:02:19 : next r> 1- ?dup 0> while r> repeat ; 00:02:25 im lame tonight 00:02:41 erm argh 00:02:48 teh second r> should be a >r hehe 00:02:55 looks cryptic :-) 00:03:08 : for r> swap 2>r ; 00:03:28 2,2-0,2kholmes2,2---: i totally agree, but when you know what >r and r> does, and all those other fancy words, it starts looking a lot less cryptic 00:03:30 eww 00:03:32 color 00:03:36 i'll stop doing that 00:03:39 * futhin slaps himself 00:03:41 ern no - i dont think these can be : definitions very easilly hehe 00:03:58 neway i gtg zzz 00:04:01 yeah 00:04:07 maybe if i sleep i can code forth again hehe 00:04:07 good night 00:04:12 cuz i sure cant rite now :P 00:04:13 heh 00:04:22 : sleep bed go tuck light off ; immediate 00:04:25 yeah whatever, nobody noticed your bad code :P 00:04:42 clog logs everything :P 00:04:45 bastard :P 00:04:54 ; tuck swap snip ; 00:04:58 ew 00:04:59 so when ppl read the above disfunctional code thwy will laff at me :P 00:05:02 : tuck swap snip ; 00:05:08 heh 00:05:16 futhin: so...what does this collaboritive universe do? 00:05:17 bubye 00:05:18 no 00:05:23 i'm the only one that i know of that reads the logs 00:05:25 : tuck swap over ; 00:05:39 the swap nip is the reference to your msg 00:05:41 i believe bongo does 00:05:47 speuler? 00:05:48 not 100% sure :) 00:05:50 yes 00:05:55 nite nite 00:05:58 nite nite 00:06:02 --- quit: I440r ("reality strikes again") 00:06:13 the collaborative universe 00:06:26 let's talk about it in tunes, so that other ppl can read it or something :) 00:06:35 okay.. 00:23:45 --- quit: [9of7] (Read error: 113 (No route to host)) 00:33:55 --- quit: futhin ("-HAVOC- zzz") 00:34:29 --- quit: kholmes ("Client Exiting") 03:06:31 --- join: [9of7] (~l@c38038.upc-c.chello.nl) joined #forth 03:38:56 --- join: MrReach (~mrreach@209.181.43.190) joined #forth 03:40:03 hihi 03:55:09 --- join: LuckyPhil (~philh@CPE-203-45-197-55.qld.bigpond.net.au) joined #forth 03:57:44 --- part: LuckyPhil left #forth 04:30:34 --- quit: [9of7] (carter.openprojects.net irc.openprojects.net) 04:30:34 --- quit: Speuler (carter.openprojects.net irc.openprojects.net) 04:35:23 --- join: Speuler (~l@c38038.upc-c.chello.nl) joined #forth 04:35:23 --- mode: carter.openprojects.net set mode: +o Speuler 04:35:23 --- mode: ChanServ set mode: -o Speuler 05:28:33 --- quit: MrReach () 07:58:31 --- join: [9of7] (~l@c38038.upc-c.chello.nl) joined #forth 11:03:35 --- join: Fare (fare@samaris.tunes.org) joined #forth 11:03:36 --- quit: [9of7] (Read error: 104 (Connection reset by peer)) 11:09:07 --- join: futhin (thin@h24-66-212-245.cg.shawcable.net) joined #forth 12:56:38 --- quit: oxygene (carter.openprojects.net irc.openprojects.net) 12:58:58 --- quit: futhin (carter.openprojects.net irc.openprojects.net) 12:58:58 --- quit: Fare (carter.openprojects.net irc.openprojects.net) 12:59:17 --- join: futhin (thin@h24-66-212-245.cg.shawcable.net) joined #forth 12:59:17 --- join: Fare (fare@samaris.tunes.org) joined #forth 12:59:44 --- join: XeF4 (~xef4@dsl-XIII-194.kotikaista.weppi.fi) joined #forth 12:59:47 --- join: oxygene (oxygene@linux-future.de) joined #forth 12:59:47 --- mode: carter.openprojects.net set mode: +o oxygene 12:59:47 --- mode: ChanServ set mode: -o oxygene 12:59:50 moo 13:00:11 --- quit: oxygene (carter.openprojects.net irc.openprojects.net) 13:00:22 --- join: oxygene (oxygene@linux-future.de) joined #forth 13:00:22 --- mode: carter.openprojects.net set mode: +o oxygene 13:00:22 --- mode: ChanServ set mode: -o oxygene 13:02:27 hola 13:02:32 we've got a bunch of idlers right now 13:02:37 clog is a bot 13:02:53 but if you see i440r or mrreach on, they usually don't idle 13:03:11 i think speuler is coding forth in brainfuck :) 13:03:17 I've not seen i440r for months 13:03:40 he's working on getting some NANDs in brainfuck, and then he'll implement some stuff from there 13:04:02 good lord.. 13:05:31 heheh 13:05:40 i assume he's having lots of fun :) 13:23:29 --- quit: XeF4 ("pois") 14:46:57 --- quit: oxygene (carter.openprojects.net irc.openprojects.net) 14:50:13 --- join: oxygene (oxygene@linux-future.de) joined #forth 15:31:59 --- join: aaronl (aaronl@vitelus.com) joined #forth 15:32:11 hi aaronl 15:32:11 --- join: aaronl_ (aaronl@vitelus.com) joined #forth 15:32:21 hi aaronl 15:32:51 --- part: aaronl_ left #forth 18:04:03 --- quit: futhin () 19:25:37 --- join: futhin (thin@h24-66-212-245.cg.shawcable.net) joined #forth 19:25:56 --- quit: Fare ("sleep") 19:26:11 g'd morning 19:26:37 g'd evening :P 19:26:49 4:26 a.m. 19:27:15 heh 19:27:24 you wake up or you staying up and going to sleep soon? 19:27:31 are you a nocturnal ? 19:27:40 often 19:27:44 mostly 19:27:52 except when in a job 19:27:59 or on holidays 19:28:21 still awake 19:28:50 got 2 /mod working ... 19:29:03 (in bf, that is) 19:29:52 'nuff 4 2day 19:31:08 80 operations ... 19:40:00 cool 19:40:05 eh? 19:40:12 80 operations in 1 day? 19:41:33 nope. half an hour coding. only returned shortly ago 19:41:55 needed some menthal gymnastics before stretching out 19:42:01 80 forth operations in half-hour coding? 19:42:13 --- join: MrReach (~mrreach@209.181.43.190) joined #forth 19:42:16 and got an idea how to implement 2 /mod on the way back 19:42:19 hi mrreach :) 19:42:24 hi mrreach 19:42:24 hihi! 19:43:15 i'll be back ... 19:43:16 what's so hard about /mod ??? I had no probs with CODE def on x86 19:43:19 ok 19:43:46 he's coding it in brainfuck 19:43:54 HAHAHA! 19:43:59 he's implementing a forth in bf 19:44:06 bf?? 19:44:08 he's gotten the NANDs working 19:44:11 oh, brainfuck 19:44:12 bf == brainfuck 19:44:29 speuler, you are leet :) 19:44:31 is this the goofy liquid computer thing? 19:44:41 mrreach: huh? 19:45:15 heh, he was going on for a while about designing a hydaulic computer, with water valves 19:45:31 --- join: [9of7] (~l@c38038.upc-c.chello.nl) joined #forth 19:45:34 hydraulic 19:45:42 wb, [9of7] 19:45:49 * [9of7] alias Speuler 19:45:53 yep 19:46:01 <[9of7]> hydraulic what ? 19:46:17 computer ... you were thinking about it some time ago 19:46:26 <[9of7]> ValveForth ? 19:46:44 <[9of7]> yes 19:46:47 * MrReach keeps his opinion to himself on this one. 19:47:28 <[9of7]> i started playing with the digital analog of valveforth (gateforth) 19:48:34 what's so hard about implementing /mod ?? I had not probs with it on x86 19:48:49 <[9of7]> it took me about 80 instructions 19:49:00 <[9of7]> may be able to bring it down to 60 ... 70 19:49:40 <[9of7]> it is the complexity of the task of 2 /mod 19:49:58 <[9of7]> hehe 19:50:07 although I started with SM/REM as the primitive, if I recall 19:50:32 <[9of7]> i coded it in brainfuck 19:50:46 you mean the phrase "2 /mod" ??? 19:50:51 <[9of7]> yes 19:50:53 wouldn't that be even easier yet? 19:51:01 <[9of7]> how ? 19:51:13 mov ax, bx 19:51:21 <[9of7]> no move 19:51:23 asl ax 19:51:27 <[9of7]> no shift 19:51:28 sbb bx, bx 19:51:35 what platform? 19:51:40 <[9of7]> brainfuck 19:52:01 erm, ok 19:52:57 <[9of7]> only 4 instructions, +2 for iteration/conditional 19:53:12 <[9of7]> +, -, <, > 19:54:02 <[9of7]> (didn't use char input and output, the remaining two instructions) 19:54:24 <[9of7]> of altogether 8 instructions 19:54:54 ok 19:55:02 <[9of7]> got about 15 forth primitives by now 19:55:05 you're right, /mod would be difficult 19:56:29 <[9of7]> been thinking about it for 2 days, in idle periods 19:57:01 I take it this will be implemented in some type of PGA?? 19:57:31 <[9of7]> don't think so. but, who knows . 19:57:44 <[9of7]> bf cpu would be easy to implement in hardware ... 19:57:57 <[9of7]> a few hundred gates 19:58:16 <[9of7]> massive parallelism could actually get this to speed 19:58:20 <[9of7]> hehe 19:59:04 you think about odd things, sometimes. Have you been drinking? 19:59:32 <[9of7]> alcohol, you mean ? not a drop for ... 3 or 4 days 19:59:55 <[9of7]> that's my normal mode :) 19:59:56 heh @:^> 20:00:59 <[9of7]> t'is longer ago than that 20:01:23 <[9of7]> can't exactly remember when i had the last alc 20:02:29 <[9of7]> i do drink more when i'm in germany 20:02:50 <[9of7]> but the beer here is not comparable 20:03:03 <[9of7]> (here = netherlands) 20:04:36 well, time for dinner and some teli with sifey 20:04:40 with wifey 20:04:46 CUL8R 20:04:51 --- quit: MrReach () 20:04:52 <[9of7]> g'd nite 20:58:54 --- quit: futhin ("bye") 20:59:34 --- quit: [9of7] ("using sirc version 2.211+KSIRC/1.1") 23:42:06 --- join: futhin (Havoc36@ab-cal-a52-01-37.look.ca) joined #forth 23:42:27 hi 23:45:21 --- join: Xuz (aemerson@bgp01079860bgs.wanarb01.mi.comcast.net) joined #forth 23:45:36 hi xuz :) 23:45:41 how's it going? 23:46:26 Pretty well, how're you? 23:46:33 --- mode: ChanServ set mode: +o Xuz 23:47:11 pretty good 23:47:20 getting back into forth sort of :P 23:47:31 i've gotten familiar with pygmy because of this pygmy tutor 23:47:37 next i'll try out a f-pc tutor 23:48:01 Good :) 23:48:53 then next i'll have to figure out how to interface libraries from gforth 23:49:08 and apparently i have to figure out something called "select" for the sockets.. 23:50:27 Oh, that's just standard Unix. 23:51:12 What're you trying to make? 23:51:37 my current project is a forth mud :) 23:51:49 i've got some other leet ideas/projects too :P 23:52:07 Ahh, yes. 23:52:20 were you the one that had some code for interfacing with the libraries? 23:52:21 * Xuz is having trouble keeping his forthers straight :) 23:52:25 Yes. 23:52:31 cause i never recieved an email from you i don't think.. 23:53:12 * Xuz doesn't have his other computer fixed yet. 23:53:19 * Xuz thinks. . . 23:53:29 * Xuz grins, "Well, I ported MzScheme to OpenBSD, may as well port GForth :)" 23:59:59 --- log: ended forth/02.01.18