00:00:00 --- log: started forth/06.03.02 00:45:54 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #forth 01:32:18 --- quit: amca (Read error: 113 (No route to host)) 01:43:27 --- join: jes (n=user@193.219.74.136) joined #forth 02:53:37 --- join: JasonWoof (n=jason@pdpc/supporter/student/Herkamire) joined #forth 02:53:37 --- mode: ChanServ set +o JasonWoof 02:54:08 --- quit: PoppaVic ("Pulls the pin...") 03:17:39 --- join: PoppaVic1 (n=pete@0-2pool236-250.nas22.chicago4.il.us.da.qwest.net) joined #forth 03:17:57 --- nick: PoppaVic1 -> PoppaVic 03:18:05 wow, this is the coolest thing ever: http://www.projectblackdog.com/ 03:18:24 hmm? 03:20:08 oh.. That is sorta' neat.. I'm too slow with osx updating. What's the guts? 03:20:24 it's a linux box 03:20:30 that fits in your pocket 03:20:41 with a USB port 03:20:53 you plug it into a pc and it grabs the monitor, keyboard, and mouse 03:21:02 and runs off the USB power 03:21:24 right, got that. OH?? grabs? what's the cpu/mem? Does it take the mainbox too? 03:21:26 yank it and it uses a tiny battery to do a clean shutdown and save state 03:21:40 doesn't grab the host cpu/ram 03:21:51 it's got it's own cpu, ram and flash 03:22:34 what cpu? mem amount? 03:22:39 if the host is running an X server it just connects to that 03:22:43 hell, what distro? ;-) 03:22:53 hah! that is sorta' cool 03:23:53 * Dimensions: H: .50? W: 1.75? L: 3.5? 03:23:53 * Weight: 1.6 ounces 03:23:53 * 400Mhz PowerPC Processor * 64MB RAM * 256MB or 512MB Flash Memory * USB 2.0 03:24:21 hmm.. Shitty ram, otherwise sweet 03:24:25 s/?/inches/ 03:24:33 bah. Linux doesn't need that much 03:24:49 --- join: nballen (n=nballen@ppp-69-239-137-85.dsl.renocs.pacbell.net) joined #forth 03:24:51 well, I *LIKE* ram - for shlib and plugins, etc, etc. 03:24:59 My desktop system had 128MB up until a few months ago and was perfectly fine 03:25:07 I'd wager they have a way to use the mobo ram, though 03:25:33 what's shlib? 03:25:34 I definitely feel it's a slick idea, though' 03:25:39 shared libs 03:27:49 --- quit: nballen (Client Quit) 03:28:13 --- part: jes left #forth 03:35:43 well, when should that work with the host overtaking mechanism of blackdog? 03:36:33 the host machine must be a brand new box, eh? or does that work also on older machines with an usb port? (host overtaking) 03:37:39 their web site says Win XP 03:37:52 (or any Linux running an X server, presumably) 03:38:48 doesn't mention OS X, but Ethernet-over-USB and the X protocol are both standard, so if you're running an X server I'd assume it would work. 03:42:11 yes cool. 03:44:11 winxp understands the X protocol? 03:45:18 no. 03:45:24 no 03:45:42 sounds like it autoloads a "driver" over USB that is an X server 03:46:44 so it says to winxp that it should load a specific file from blackdog and use it? how does it do that? 03:47:11 it doesn't say. 03:47:26 hummingbird used to be the doze X11 server 03:47:33 winxp must have some mechanism for that 03:48:09 as a guess, I'd say it probably provides a USB disk interface also, with an autorun.inf script or whatever 03:50:02 if that's the case, you *might* be able to load it up with software that worked on earlier Windows. 03:50:57 well, anyway you look at it - tis interesting.. Now, can you stack 'em and do IPC as well? ;-> 03:51:12 Pocket Beowulf-clusters ;-) 03:58:32 heh 04:03:06 also sorta' reminds me of the "plugins" of the ancient t/s-1000 04:08:05 --- quit: PoppaVic ("Pulls the pin...") 04:08:12 --- quit: neceve ("Bye people, I'm leaving") 04:41:52 --- join: PoppaVic (n=pete@0-1pool47-184.nas30.chicago4.il.us.da.qwest.net) joined #forth 05:25:30 --- quit: PoppaVic ("Pulls the pin...") 05:45:27 --- quit: rsyncx ("Leaving") 05:52:32 --- join: Robert (n=robert@unaffiliated/robert) joined #forth 06:22:23 --- join: kenpex (i=guest@host51-195.pool872.interbusiness.it) joined #forth 06:26:20 hi Robert 06:27:44 reAll 06:28:30 hi 06:29:00 kenpex: new here? 06:29:14 tathi yes 06:29:48 Hi, tathi and kenpex. 06:29:58 hi kenpex 06:30:08 virl, robert 06:30:13 so...do you do much forth? 06:30:15 Hi virl, too. 06:30:59 tathi no, I've never done any forth, I've stumbled on it because I was learning about threaded code 06:31:16 kenpex, so from where are you coming? 06:31:17 I've read a bit about it, and similar stack based languages like joy 06:31:22 virl Italy 06:31:41 kenpex, not that, from which programming background are you coming. 06:31:51 but I dunno if or why I will ever use it, it seems interesting mainly if U do embedded stuff 06:31:58 virl: mhm 06:32:07 kenpex: if you liked Joy, did you see Factor? (http://factorcode.org/) 06:32:11 well I started with basic, then assembler 06:32:14 then C 06:32:15 then C++ 06:32:18 then mhm java 06:32:22 then I think lisp 06:32:23 sml 06:32:26 ocaml 06:32:28 prolog 06:32:38 rebol, ruby, io 06:32:46 well something like that 06:32:58 tathi: nah 06:33:30 by the way, mostly graphical applications, 3d, opengl, numerical analisys, buy also everything else I find fun 06:34:08 tathi: wow it seems nice 06:34:40 heh. you might get along with slava 06:34:59 IIRC he's doing a Master's in math and doing opengl at work 06:35:12 #concatenative here 06:36:04 :) 06:38:26 I think there's not single language to rule them all 06:38:40 or at least, I haven't found it yet 06:41:50 --- part: rehges left #forth 06:42:08 oops; forgot to say that slava is factor's author 06:42:40 and yah, all languages are good (and bad) at different things AFAICT 06:45:21 no, there are some just bad ones too 06:45:30 mhm like visualbasic 06:47:02 or well, maybe someone will get angry, but I would say delphi too 06:47:06 true true :) 06:47:21 * tathi hasn't ever used delphi 06:48:12 delphi is nice, but it's not really simpler than c++, but it's unsupported, less widespread and it's not a standard 06:49:17 well if we have to talk about the -language- and not the community and the tools then c++ is a bad-only language too, because you could use something like oCaML as a general-purpose system language and there's nothing in the _language_ that makes it less powerful than c++ 06:49:30 but in the real world, c++ is a nice language to know/use too 07:04:08 --- join: rsyncx (i=nobody@CPE000c41aac435-CM00111ae4f4cc.cpe.net.cable.rogers.com) joined #forth 07:17:52 --- quit: uiuiuiu (Read error: 104 (Connection reset by peer)) 07:22:57 --- join: uiuiuiu (i=ian@dslb-084-056-208-206.pools.arcor-ip.net) joined #forth 07:30:13 --- quit: Cheery (Read error: 104 (Connection reset by peer)) 07:32:38 --- part: rsyncx left #forth 07:44:41 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-169-192.pools.arcor-ip.net) joined #forth 07:46:45 --- quit: Snoopy42 (Nick collision from services.) 07:46:51 --- nick: snoopy_1711 -> Snoopy42 07:50:52 --- quit: virl ("Verlassend") 08:18:51 --- quit: OrngeTide ("bye") 08:49:17 --- quit: kenpex (Read error: 104 (Connection reset by peer)) 09:41:13 --- join: neceve (n=Clau@unaffiliated/neceve) joined #forth 09:50:52 --- join: danniken (i=CapStone@adsl-69-155-122-222.dsl.ltrkar.swbell.net) joined #forth 10:32:57 --- quit: tathi ("leaving") 10:44:31 --- join: thinkinginbinary (n=tom@phoenix.thomastuttle.mooo.com) joined #forth 10:48:14 Quartus: hey 10:51:59 Quartus: Do you run Norton Internet Security? 11:05:01 --- quit: neceve ("Bye people, I'm leaving") 11:06:05 --- join: rsyncx (n=bob@CPE000c41aac435-CM00111ae4f4cc.cpe.net.cable.rogers.com) joined #forth 11:15:05 --- quit: rsyncx ("Leaving") 11:18:25 --- join: rsyncx (n=bob@CPE000c41aac435-CM00111ae4f4cc.cpe.net.cable.rogers.com) joined #forth 11:18:29 --- quit: rsyncx (Read error: 104 (Connection reset by peer)) 11:19:06 --- join: rsyncx (n=bob@CPE000c41aac435-CM00111ae4f4cc.cpe.net.cable.rogers.com) joined #forth 11:21:36 --- quit: rsyncx (Client Quit) 11:36:25 --- quit: thinkinginbinary ("leaving") 11:45:34 --- join: sproingie (n=chuck@64-121-2-59.c3-0.sfrn-ubr8.sfrn.ca.cable.rcn.com) joined #forth 11:46:21 --- join: rsyncx (n=bob@CPE000c41aac435-CM00111ae4f4cc.cpe.net.cable.rogers.com) joined #forth 13:00:01 --- part: danniken left #forth 13:10:41 --- join: I440r (n=foo@cpe-67-11-173-9.satx.res.rr.com) joined #forth 13:48:28 --- quit: JasonWoof ("leaving") 13:52:50 --- join: JasonWoof (n=jason@pdpc/supporter/student/Herkamire) joined #forth 13:52:50 --- mode: ChanServ set +o JasonWoof 13:57:03 --- nick: nanstm -> Raystm2 14:07:31 --- quit: JasonWoof ("oops, missed one") 14:43:41 --- join: airbrush (i=airbrush@216-237-213-237-access-r30-ad.northstate.net) joined #forth 15:00:26 --- join: JasonWoof (n=jason@pdpc/supporter/student/Herkamire) joined #forth 15:00:26 --- mode: ChanServ set +o JasonWoof 15:24:39 --- quit: airbrush ("Leaving") 15:25:05 --- quit: rsyncx ("Leaving") 15:46:01 --- quit: sproingie ("Konversation terminated!") 17:44:55 --- join: Cheery (i=Henri@a81-197-45-47.elisa-laajakaista.fi) joined #forth 18:02:07 --- quit: JasonWoof ("off to bed") 20:01:35 --- join: scope (n=junk@njd.paradise.net.nz) joined #forth 20:58:03 --- join: neceve (n=Clau@unaffiliated/neceve) joined #forth 22:23:55 --- join: PoppaVic (n=pete@0-1pool74-143.nas24.chicago4.il.us.da.qwest.net) joined #forth 22:55:11 --- join: chris2 (n=chris@p549D1899.dip0.t-ipconnect.de) joined #forth 23:09:50 hi 23:10:00 howdy 23:10:10 is there an idiom for looking up and calling a word at runtime? 23:10:24 yes 23:10:33 same as the outer loop would use 23:10:58 and where can i read about it? 23:11:26 like ' foo execute, you mean? 23:11:35 in your documents. You likely want tick ' or ['] and some executor, yeah 23:11:50 will try, thx 23:12:03 np 23:13:29 that doesnt work if the word has not yet been defined, tho...? 23:13:38 oh, well - right 23:14:30 are you trying to define them or run them? 23:14:49 i'm defining a word to call a word that may not yet have been defined 23:15:07 can't call something non-defined 23:15:30 well, then it should break at run-time, not at compile time 23:15:44 sure. 23:17:03 what variant are you running? 23:17:17 gforth 23:17:26 see ' 23:17:38 then see (') 23:18:13 ok 23:18:41 : a ' b execute ; : b ." B" ; does not work 23:19:18 you better read the info-pages 23:20:00 you can NOT 'embed' the word 'b' in a, if b does NOT exist. 23:20:11 in no way at all? 23:20:35 sounds like you actually want to embed a string and then lookup the string it leaves on the stack - and that's just plain foolishness. 23:20:50 well, it has a certain purpose here... 23:22:56 i mean, that ['] doesnt work is clear to me... but i dont understand why ' b does not work, since b is defined when i call a 23:23:38 Umm.. Sure. OK. You have fun. 23:23:50 ;) 23:26:04 (oh, i understand... it depends on the definition order, since the directory only is looked up in one direction) 23:26:18 : test name name-too-short? find-name cr .s ; 23:26:34 test foo 23:26:40 test test 23:38:40 but will test work inside a definition? 23:39:01 did you try it? 23:39:22 Attempt to use zero-length string as a name 23:39:31 : dotest test cr ; 23:39:40 * PoppaVic sighs 23:40:03 let me guess, you then just did "dotest" 23:40:15 yes 23:40:29 doh ;) 23:40:47 okay, i understand why it doesnt work. but i dont know how to fix it 23:41:38 well, time to check the info-files 23:56:21 the manual is very clever ;) "Parsing words are hard to use in other words, because it is hard to pass program-generated parameters through the input stream." 23:56:33 and i looked at some definitions gforth uses for parsing words 23:56:38 sure 23:57:12 it uses immediate words that postpone the code that actually handles the word 23:57:24 yep 23:58:12 according to that, : [test] name . ; immediate : dotest [test] cr ; should work 23:58:39 ok, try it 23:59:45 it prints 2, which is correct 23:59:53 but then: *the terminal*:2: unstructured : dotest [test] cr ; 23:59:59 --- log: ended forth/06.03.02