00:00:00 --- log: started forth/07.08.07
00:01:29 --- join: H4ns (n=Hans@70.91.193.41) joined #forth
00:25:50 --- join: ecraven (i=nex@eutyche.swe.uni-linz.ac.at) joined #forth
00:54:57 --- quit: H4ns (Read error: 110 (Connection timed out))
01:12:41 --- join: H4ns (n=Hans@70.91.193.41) joined #forth
01:26:21 --- quit: dgd2 (Read error: 110 (Connection timed out))
04:42:59 --- join: H4n1 (n=Hans@ita4fw1.itasoftware.com) joined #forth
04:45:55 --- quit: H4ns (Read error: 110 (Connection timed out))
04:46:04 --- nick: H4n1 -> H4ns
05:57:13 --- join: timlarson_ (n=timlarso@65.116.199.19) joined #forth
06:20:56 --- quit: Quartus__ (Read error: 104 (Connection reset by peer))
06:22:13 --- join: tetonca (n=chris@66.155.140.203) joined #forth
06:29:54 <tetonca> I440r I'm wondering about the definition of 'unique' in history.f
06:30:44 <tetonca> Two different depths depending on outcome.
06:31:53 --- quit: Al2O3 ("Eggplant & SenseTalk: Driving Success Through Automation")
06:42:14 <TreyB> We generally frown upon such definitions.
06:49:44 <tetonca> Albert told me not to do that. ;)
08:34:27 --- quit: ecraven ("bbl")
08:40:15 --- quit: Baughn (Read error: 110 (Connection timed out))
08:49:23 --- join: Quartus__ (n=Quartus_@205.205.50.2) joined #forth
08:52:23 --- join: Baughn (n=svein@2002:54ca:ec08:0:0:0:0:1) joined #forth
08:59:23 <I440r> its frownd upon... discouraged... not illegal :)
08:59:47 <I440r> dont look in my memory manager because the  "begin while until else then" loop will scare you!
08:59:49 <I440r> hehe
09:01:43 <I440r> result true returned on success. else false returned.  i see nothing wrong with that
09:01:46 <I440r> personally
09:16:24 <tetonca> hehe.
09:16:50 <tetonca> you have  ( n1 -- n1 add flag | n1 flag )
09:16:50 <Quartus__> what's frowned upon?
09:16:54 <tetonca> that's unbalanced.
09:17:24 <Quartus__> ah
09:17:34 <tetonca> two depths as consequence of what happens inside a word
09:18:07 <tetonca> one execution path doesn't embed the address on the stack; the other does.
09:19:59 <tetonca> I was told not to do that by my instructor.
09:20:23 <tetonca> (it's not really factored)
09:26:39 <rehges> it's reasonably common for words that indicate failure though
09:26:55 <rehges> there isn't really a better way anyway
09:27:23 <tetonca> So you just make sure it's correct and test it well.
09:29:52 --- quit: Baughn (Remote closed the connection)
09:32:03 <I440r> you could store the result(s) in some memory location and return success or failure alone on the stack. thats slower
09:32:29 <I440r> also, your instructor was correct but never say never.. 
09:32:39 <tetonca> It was my first guess .. a structure that seemed less than optimal.
09:33:11 <tetonca> (and a guess only)
09:33:31 <I440r> go with your first instincts :)
09:34:20 <tetonca> first instinct is to live without a cli hist and hope the author fixes it someday. ;)
09:34:31 --- quit: Quartus__ (Read error: 104 (Connection reset by peer))
09:34:32 <I440r> lol
09:34:42 <tetonca> ?exit is damaging my mind.
09:34:56 <tetonca> it's a toplogical scary zone.
09:35:04 <I440r> x support is probably a pipe dream unless you can find me some comprehensive documentation for the X protocol
09:35:14 <I440r> its a conditional exit
09:35:26 <tetonca> I know.
09:36:01 <tetonca> I'm just not used to trusting the stack effect prior to and after exec of that word.
09:36:18 <tetonca> I wrote a test word to use it and saw the effect.
09:36:42 <tetonca> (an exit that consumes a stack item is a new one on me, is all).
09:37:04 <I440r> hrm. my commenting on ?exit though cute are particularly unhelpful lol
09:37:35 <tetonca> Why not '<BOOL> if exit then'
09:38:11 <I440r> less efficient
09:38:23 <I440r> avoid if/and/but looping
09:39:00 <I440r> like my ?: word  if true-part else fapse-part then  is way less efficient than ?: true-part false-part
09:39:14 <I440r> space AND speed wise
09:39:23 <tetonca> I can kind of see the point.
09:40:01 <I440r> but there is one other consideration that i "consider" more important than EITHER of the above two
09:40:14 <tetonca> yeah.
09:40:41 <I440r> stated thusly it simplifies all issues... if "if exit then" is more readable to you... do it that way
09:41:44 <tetonca> 'if exit then' is helpful to me mostly in defining not reading someone else's definition.  I would initially rewrite it if I understood they were equvalent, to dissect it.
09:41:45 <I440r> did u run that experiment? :)
09:42:01 <tetonca> No I wasn't sure it was equivaent.
09:42:09 <tetonca> equivalent.
09:43:33 <I440r> i think i know why history is failing on turnkey
09:43:47 <I440r> the hooks to hook into the terminal are compile time actions i think
09:44:02 <I440r> hrm no.. theres a hinit that defers default... weird
09:44:40 <tetonca> Chuck Moore says not to put in hooks for 'future' use. ;)
09:44:41 <I440r> aha - i think i got it
09:44:52 <I440r> he is right and wrong 
09:44:57 <I440r> never say never
09:45:15 <tetonca> I know. I play a little Go.  Proverbs are provisional. ;)
09:45:32 <I440r> lol 
09:45:59 <I440r> i play go quite well against another player but i cant play a computer ever. it always wins :/
09:46:14 <tetonca> Oh yes you can. ;)
09:46:48 <tetonca> I think I made 20 kyu on KGS by beating the gobot.
09:47:05 <tetonca> It played better Go than me but did so algorithmically.
09:47:14 <tetonca> I spanked it once I saw the pattern.
09:47:21 <I440r> lol
09:47:37 <tetonca> (in a single game too -- no 2nd try)
09:48:11 <tetonca> I needed 19x19 to have time to spot its vulnerability.  It would have creamed me on 13x13.
09:48:42 <tetonca> A real human would have caught on a lot faster to how I was countering.
09:49:02 <tetonca> I got Sente and kept it after that. ;)
09:49:36 <I440r> there is no 13x13. there is ONLY 19x19 dangit
09:49:48 <I440r> there is NO spoon!
09:50:58 <tetonca> I think a skilled 10kyu player would have realized I never gained Sente. ;)
09:51:12 <tetonca> I was ignoring important attacks.
09:57:52 <I440r> how did u fix the isforth crash after an fsave again?
09:58:27 <tetonca> removed history.f from ./extend via it's inclusion in isforth.f
09:59:10 <tetonca> Prior to that 'hello' twice helped.
09:59:35 <tetonca> (as if 'hello' once bought me an opportunity to type it a 2nd time)
09:59:55 <I440r> yea that helped
10:00:25 <tetonca> you were able to reproduce the failure locally to see what I was describing?
10:00:33 <I440r> well i just did hello twice and it fixed it. exited and typed hello once and it crashed
10:00:38 <I440r> yes
10:00:49 <tetonca> good.
10:01:02 <I440r> i have already observed the failure and for now am stumped. i still think its caused by the addition of command line history
10:01:15 <tetonca> also one word (see iirc) leaves an address on TOS.
10:01:23 <tetonca> couldn't figure why.
10:01:37 <I440r> erm might be a bug
10:01:43 <tetonca> 'see foo' leaves an address on TOS.
10:01:53 <I440r> i modificated see alot to do the debugger which is also buggy
10:02:11 <tetonca> If I 'see foo drop' it seemed more correct resultant environment.
10:02:16 <tetonca> (data stack).
10:02:28 <tetonca> okay.
10:02:48 <I440r> yes the address at the top of stack left by see is its running decompile address left there
10:02:51 <I440r> wrongly
10:02:58 <tetonca> I've never seen an address on TOS after 'see foo' before.
10:03:10 <I440r> because i modified it for the debugger
10:03:19 <I440r> : foo 100 0 do i . loop ;  debug foo
10:03:36 <tetonca> Well that didn't stop me; but the history buffer thing was difficult to work around.
10:03:38 <I440r> that seffaults lol
10:03:41 <tetonca> ;)
10:03:53 <I440r> grrr
10:04:01 <I440r> debugger is brokificated too
10:04:22 <I440r> is the debugger brok for you?
10:04:31 --- join: Quartus__ (n=Quartus_@205.205.50.2) joined #forth
10:04:34 <tetonca> I have no idea how to use a debugger. ;)
10:04:54 <tetonca> I think the last one I used was in MS-DOS in maybe what .. 1986?
10:05:11 <I440r> create a bs definition called foo
10:05:14 <I440r> then say debug foo
10:05:21 <I440r> and tell me what happens
10:05:23 <tetonca> I'll try it.
10:05:45 <I440r> single step with the space bar. if you want to step INTO a : def use the enter key
10:05:55 <I440r> escape quits i believe
10:06:32 <I440r> you can also move the cursor (not IP) with the keys and then type H to run to the cursors location (H or h but they work differently)
10:06:54 <I440r> but its segfaulting for me here so its broken here
10:07:05 <tetonca> hm.
10:07:26 <tetonca> oh cool a blue screen.
10:07:33 <I440r> its not broke for you then
10:07:43 <I440r> or maybe it is
10:07:54 <I440r> no windows with a decompilation of your word?
10:08:01 <tetonca> I just did ./extend and then ./isforth and then : myword its definition ;
10:08:39 <tetonca> I see terminfo in hex dump upper right /rxvt in there. ;)
10:09:10 <tetonca> In left window a nicely formatted version of my definition.
10:09:33 <I440r> ok. space to single step each word in the def
10:09:44 <tetonca> Only one other window is populated (middle wnd in the group of three at the bottom)
10:10:16 <tetonca> stack report left wnd group of three
10:10:41 <tetonca> I had a lot of i/o words ." string " and 'cr'.
10:10:44 <I440r> there is a decompilation window. a memory window and two stack displays
10:10:51 <I440r> they shud work perfectly
10:10:58 <I440r> press the o key to see the output window
10:11:04 <tetonca> ah. 
10:11:22 <I440r> this doesnt work perfectly yet lol
10:11:25 <I440r> erm or AT ALL here
10:11:27 <I440r> lol
10:12:05 <tetonca> WellI do see a good output window.
10:12:18 <tetonca> But I can't navigate well in the definition.
10:12:36 <tetonca> It's modal and I can only access the movement modality.
10:12:37 <I440r> dont use any words that create widnows in the same way the debugger does tho (yet)
10:12:46 <tetonca> haha.
10:12:56 <tetonca> 'dont touch that its not finished!'
10:13:12 <I440r> NONE of isforth is finished... see that leetter B in its name? hehe
10:13:22 <I440r> yall are a testificatior
10:13:31 <tetonca> Once I back up in the word how do I single step from that point forward.
10:13:52 <I440r> im not sure you can move the IP backwards, just the cursor
10:13:56 <tetonca> E.g. up-cursor key gives green cursor.
10:14:00 <I440r> you can press h to "run to here"
10:14:01 <tetonca> got it.
10:14:09 <I440r> if it ever gets there u have to escape lol
10:14:13 <tetonca> what about exit when I'm at semicolon?
10:14:16 <I440r> or kill it
10:14:20 <I440r> escape?
10:14:23 <I440r> or q i ferget
10:14:24 <tetonca> oh.
10:14:41 <I440r> what terminal do you use
10:14:41 <tetonca> esc it is.
10:14:43 <I440r> rxvt?
10:14:51 <tetonca> what is the semicolon word called? sem?
10:14:59 <I440r> semicolon
10:15:04 <tetonca> rxvt (Terminal.app Mac OS X told to be rxvt)
10:15:07 <tetonca> tnx.
10:15:21 <I440r> ppc?
10:15:26 <tetonca> yeah.
10:15:33 <I440r> aha your running tathi's version hehe
10:15:34 <tetonca> but the host is Linux x86 running isforth.
10:15:41 <tetonca> ssh hostwithisforth
10:15:50 <I440r> aha :)
10:15:59 <tetonca> headless linux box running damn small.
10:16:14 <I440r> who give out isforth shell accounts?
10:16:16 <I440r> slava ? :)
10:16:24 <tetonca> your isforth on kernel 2.4.26
10:16:32 <I440r> yea but whos box is it?
10:16:38 <tetonca> mine! it's a mini-itx
10:16:50 <tetonca> actually it's in a ramdisk atm.
10:16:52 <I440r> ok your sshing to another box of yours thats running isforth
10:16:56 <tetonca> yes.
10:16:57 <I440r> gotchya
10:17:04 <tetonca> I used your kernel.com
10:17:08 <tetonca> I never used nasm.
10:17:30 <I440r> i probably shouldnt call it kernel.com lol
10:17:51 <tetonca> you should call your .f files .fs to match gforth so vim will syntax highlight.
10:17:56 <I440r> no
10:18:03 <I440r> SINGLE letter extensions
10:18:07 <I440r> nobody uses fortran
10:18:15 <tetonca> well I suppose vim can be spanked.
10:18:24 <tetonca> I have a template for that.
10:18:28 <I440r> ick
10:18:30 <I440r> use joe :P
10:18:37 <tetonca> joe is .. lame.
10:18:40 <tetonca> vim rox.
10:18:41 <I440r> lol
10:19:03 <I440r> vi is brain damaging. i know. i had to use it once... ONCE!
10:19:03 <tetonca> well I haven't used joe in ages maybe it has syntax highlighting now.
10:19:11 <I440r> ya
10:20:26 <I440r> i prefer codewrite. i wish that there was a linux version developed before borland shitcanned it
10:21:46 <tetonca> you can ask for it when they end this AI simulation of the world.  It's in your contract.
10:22:09 <I440r> :)
10:22:21 <tetonca> ;) I'm very into Bostrom these days.
10:22:31 <I440r> whussat?
10:22:45 <tetonca> Nick Bostrom's /Simulation Argument/.
10:22:51 <I440r> aha
10:23:12 <tetonca> He's got a pretty good take on why we might be living in a matrix.
10:23:51 <tetonca> Somebody wrote a corrolary that says our simulation ends in 2050 by Moore's Law (not chuck the other Moore)
10:24:01 <I440r> yea\
10:24:18 <I440r> from IBM said something quaint about processor power increasing blah blah
10:24:21 <tetonca> The dataset becomes garbage the moment the AI's realize they're in a simulator.
10:24:45 <I440r> but then its NOT a simulation 
10:25:06 <I440r> thats called enlightenment :)
10:25:07 <tetonca> There's even a new provision for limited nesting.
10:25:35 <I440r> something C coders should learn to do hehe
10:25:43 <I440r> erm actually
10:26:03 <I440r> c coders need to factor their if/and/but loops more... c coders need to limit indenting :P
10:26:22 <tetonca> Yeah you have a no-tab-stop fettish going.
10:26:36 <tetonca> I use whitespace myself.
10:26:47 <I440r> have you ever read the linux kernel coding standards doc?
10:27:01 <tetonca> No.  I've read kernel source tho.
10:27:13 <I440r> i have a parody of it somewhere that takes every single rationalizatin that linus pukes in there and blows it away
10:27:21 <tetonca> I tend to reduce my indent spaces to fit the page.
10:27:28 <I440r> two spaces max
10:27:34 <I440r> or of its asm you d
10:27:35 <I440r> label:
10:27:37 <tetonca> two is okay.
10:27:42 <I440r> <one space> blah blah
10:27:47 <tetonca> one is kind of hard to see easily.
10:28:07 <tetonca> I'll use one space if it helps.
10:28:17 <tetonca> (makes it fit without side scrolling)
10:28:27 <tetonca> I use 90x26 terminal.
10:29:05 <tetonca> I used to go a lot wider but I can't see that good anymore.
10:29:34 <tetonca> I still break at column 78 max (usually 67 or so).
10:30:10 <tetonca>  --
10:30:28 <tetonca> why doesn't 'words' bring newest definition to the top of its vocabulary?
10:31:24 <I440r> because 
10:31:25 <I440r> lol
10:31:40 <I440r> it doesnt display them in the order they are created because the vocabularies are hashed
10:31:56 <tetonca> also ctrl k and ctrl u should be useful on the input line when the history is active.
10:32:00 <I440r> a vocab is an array of 64 threads.  the thread a word is attached to depends on the word names hash value
10:32:31 <I440r> i would have to create a complete terminal application with its own complete terminfo JUST for isforth to be able to do that
10:32:37 <tetonca> well I'll have to circumvent that later. ;)
10:32:39 <I440r> im existing within your terminal
10:33:08 <tetonca> doesn't my terminal already support ctrl k and ctrl u?
10:33:32 <tetonca> ctrl u meaning kill the line  ; ctrl k meaning kill to EOL.
10:33:53 <I440r> well im not using readline
10:34:12 <I440r> but terminal input in linux is an abomination
10:34:20 <tetonca> I think this is more basic.  I saw it the other day.  I wish I could remember where.
10:34:27 <tetonca> Maybe in stty.
10:34:30 <I440r> why is why vi is an abomination
10:34:30 <tetonca> I bet that's it.
10:34:42 <I440r> termcap was developed specifically for vi and that lead to terminfo
10:34:48 <tetonca> hahah.
10:34:59 <tetonca> so there's a whole chain of abomination.
10:35:09 <I440r> terminfo is sooooo b0rked its a wonder ANYTHIGN works.  this is why ncurses is 500k of library
10:35:24 <tetonca> well pt taken.
10:35:35 <tetonca> something surely has to be done I agree.
10:35:44 <I440r> ncurses is horrible, what it has to do etc etc.  im very impressed with how well it does what it does
10:36:11 <tetonca> this probably explains lack of these bindings in firmware linux
10:36:27 <tetonca> I know libreadline isn't present. hell glibc isn't present. ;)
10:37:09 <I440r> doing a readline type interface was next on the todo list but i think fixing what i b0rked should come first :)
10:37:11 <tetonca> I think we're somewhat on the same page.
10:37:22 <tetonca> I agree. fix what's broken.
10:37:58 <tetonca> Anybody can add a feature and never return to it to fix what was broken before the feature got added.
10:38:29 <tetonca> that orthogonal word appears in that sentence somewhere.
10:39:03 <I440r> its called job security haha
10:39:14 <I440r> fix this break that be called back to fix more :)
10:39:16 <tetonca> ;) what's a job tho.
10:39:59 <tetonca> I'm kwai chang kain.  I will help you.  Your forth no work, I will help you. [foley: flute]
10:40:36 <I440r> lol
10:41:10 <tetonca> when they say 'work ethic' that implies work /is/ ethical.
10:41:14 <tetonca> But it's not.
10:41:20 <tetonca> It's theft and slavery.
10:41:58 <tetonca> Where's the 'play ethic'. we never hear about it because it's not in the propaganda model.
10:42:05 <tetonca> 'play' is their theft!
10:42:27 <I440r> !
10:43:24 <tetonca> They do allow 'For the love of Mike'.
10:43:51 <tetonca> I don't want to get banned so I'll stop there.
10:44:17 <I440r> there is no banned 
10:44:43 <I440r> at least i hope not, i always wanted #forth to be unmoderated... i.e. there is no "off topic" here
10:45:08 <tetonca> I get nervous about that.
10:45:28 <I440r> because there are alot of anally retentive people in anally retentive channels on irc
10:46:04 <tetonca> irc is governed by people invested in governing it. I guess that's a tautology.
10:46:22 <tetonca> When they show up I just stop typing.
10:46:24 --- quit: madwork (Read error: 104 (Connection reset by peer))
10:46:59 <I440r> well dont worry about it in here :)
10:47:06 <I440r> we would only ban werty :)
10:47:09 <I440r> for the FUN of ti!
10:47:10 <I440r> it
10:47:17 <tetonca> I don't want to try to adapt forth to infix but I wonder about the graphics layer if any.
10:47:48 <I440r> if i do an X interface it will be forthish not c-ish]
10:48:08 <tetonca> I guess the graphix (pixel) problem is in principle the string handling problem.
10:48:49 <tetonca> I should probably just think about it as with microcontrollers so as not to get lost.
10:49:10 <tetonca> (e.g. how would I do this on a micro)
10:49:30 <I440r> ohhh a console based frame buffer would be way easier than X lol
10:49:37 <I440r> but not as useful
10:49:50 <tetonca> I don't know if X has a future.
10:50:03 <I440r> i think X is here to stay
10:50:18 --- join: madwork (n=foo@204.138.110.15) joined #forth
10:50:19 <I440r> show me its replacement :)
10:50:27 <tetonca> Well emulators.
10:50:34 <tetonca> they're popping up everywhere.
10:50:48 <tetonca> they're bypassing X11.
10:51:26 <tetonca> I'm not advocating that I'm making a casual observation.
10:51:44 <I440r> hmmm
10:51:50 <I440r> how do you bypass x11
10:52:02 <tetonca> I'd guess they use the framebuffer directly.
10:52:10 <tetonca> I know it's on a VT in Linux.
10:52:22 <I440r> that wont work accross a network. X11 does
10:52:39 <tetonca> Yeah but you can do half on one side half on the other.
10:52:44 <tetonca> semaphores.
10:53:03 <I440r> yes but that takes a dedicated client for THAT application
10:53:11 <tetonca> No make it generic.
10:53:17 <I440r> exactly
10:53:34 <I440r> and it removes the "same look and feel for all applicaitons"
10:53:48 <tetonca> I wouldn't say that.
10:54:16 <tetonca> You start with a single machine and treat it's keyboard and display as if they were 20 miles away over a clean tcp/ip link.
10:54:31 <tetonca> send semaphores.
10:54:43 <tetonca> exchange semaphores.
10:54:59 <tetonca> But that's if you want a remote desktop for some reason.
10:55:04 <tetonca> I think that's overkill.
10:55:09 <I440r> thats what X does basically - cept the semaphores are a few hundred k in size sometiems lol
10:55:16 <tetonca> I know.
10:55:31 <tetonca> So if anything I'd say write an analogy to X11.
10:55:37 <tetonca> but not X11 itself.
10:56:03 <tetonca> You'd be roped into all sorts of things and before you knew it you'd be using infix and floats. ;)
10:56:40 <I440r> i hate floating point
10:56:49 <I440r> but ill add it if i ever get an assembler up and running
10:57:00 <tetonca> I dislike a computer that doesn't work the 2nd time when it worked the 1st time.
10:57:17 <I440r> floating point is like recursion. anything you can do WITH it you can do better without
10:57:25 <I440r> ya
10:57:28 <tetonca> Yeah.
10:57:31 <I440r> thats gotta get fixed lol
10:57:50 <tetonca> I thot of that but I was thinking about all the years gone by.
10:58:14 <tetonca> If i'm gonna put that kind of time in I don't want it lost.
10:58:28 <tetonca> Resigned to the time put in but let's preserve the gains.
10:59:00 <tetonca> Computers were much faster when they were introduced to mass markets.
10:59:10 <tetonca> (the UI was anyway).
10:59:23 <tetonca> At least I think they were.
10:59:40 <tetonca> Everyone got seduced by more functions.
11:00:14 <I440r> i remember when i came back to the states. i had my commodore 128 and i loaded a program and my dad said .... when does it stop loading?
11:00:22 --- join: forther_ (n=forther@207.47.34.100.static.nextweb.net) joined #forth
11:00:23 <tetonca> heheh.
11:00:29 <I440r> he showed me ultima 3 on his computer which loaded instantly lol
11:00:55 <I440r> nowadays you click on the "start" button, wait 3 seconds. then click on a menu item, wait 3 seconds.....
11:01:00 <I440r> and its acceptable
11:02:13 <tetonca> If it isn't written in forth it will never make it to Alpha Centauri on that first mission.
11:02:25 <tetonca> Mission will fail.
11:02:42 <tetonca> That's how I look at things .. will this save my ass when I'm too far to turn around.
11:02:49 <tetonca> When it /has/ to be fixable enroute.
11:02:53 <tetonca> Or else. ;)
11:03:07 <I440r> lol
11:03:08 <tetonca> that should say the scope of the complexity allowed.
11:03:35 <tetonca> Let's just say the silicon chip problem isn't unsolved in that scenario.
11:04:00 <I440r> i dont hold with everything that CM says or does but there are a couple of things he said that i agree with completely.  i.e. "Forth is THE software engineering solution"
11:04:16 <tetonca> I agree with that.
11:04:26 <tetonca> If it can't be done in forth it will break. ;)
11:05:00 <tetonca> Everything else is a mock-up.
11:05:15 <tetonca> A marketing tool about what we /will/ build not what we /have built/.
11:05:56 <tetonca> You should be able to thump it to make a point and not have it fall all apart like some Bill Gates presentation that crashes.
11:06:10 <tetonca> And look like a fool.
11:06:46 <tetonca> Easier said than done.
11:07:00 --- join: Baughn (n=svein@2002:54ca:ec08:0:0:0:0:1) joined #forth
11:07:18 <tetonca> But it might matter one day.
11:07:37 <I440r> lol
11:08:06 <I440r> i wonder if he fires people after a presentation crash of a new product hehe
11:08:38 <I440r> and here is widnows 5000 booting (smoke rises from computer)... oopts ignore that it doesnt happen often!
11:08:48 <tetonca> Right.
11:09:15 <tetonca> It worries me that it might not be possible really to get people to move towards reliable solutions.
11:09:29 <I440r> the world doesnt want reliable
11:09:33 <I440r> it wants NOW
11:09:42 <tetonca> It might be right up to a pt.
11:10:10 <tetonca> Certainly external events can set the timetable.
11:10:31 <tetonca> I think the game is to convince that's what's happened.
11:10:45 <tetonca> Prior to it having happened.
11:10:50 <tetonca> as a ruse.
11:11:14 <tetonca> But I don't have kids. ;)
11:11:29 <I440r> lol
11:12:45 <tetonca> They let college students send small missions into space now.
11:12:55 <tetonca> I think they're like 3" cubes.
11:13:39 <tetonca> First ones are just to find like dendrites and such and see what effects the environment has on basic hardware.
11:15:18 <tetonca> gah.
11:16:11 <I440r> \hmm
11:16:49 <tetonca> I think the point is just as you said to trust your intuition.
11:18:02 <tetonca> I'm gonna catch the zzz's.
11:18:26 <tetonca> We got weather coming by 06z or so. (2 a.m. east coast usa time).
11:19:05 <I440r> ok :)
11:19:26 <I440r> where are u located?
11:19:36 <tetonca> torrington ct usa
11:19:49 <I440r> ill be in liverpool ny this weekend :)
11:20:01 <tetonca> cool!
11:20:41 <tetonca> I hope I can sleep.  I'll see you around.  -chris@river.org btw.
11:20:50 <tetonca> (wa1tnr)
11:22:52 * tetonca drops carrier .. pigeons.
11:22:58 --- quit: tetonca ("User disconnected")
12:11:00 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth
12:11:00 --- mode: ChanServ set +o tathi
12:19:48 <Quartus__> hi, tathi.
12:20:02 <tathi> Hi, Quartus.
12:35:00 --- quit: forther_ (Read error: 110 (Connection timed out))
12:46:44 --- join: dgd2 (n=dgd@166.227.127.226) joined #forth
12:48:04 --- quit: dgd2 (Read error: 104 (Connection reset by peer))
13:06:51 --- join: forther_ (n=forther@207.47.34.100.static.nextweb.net) joined #forth
13:59:52 --- quit: timlarson_ ("Leaving")
14:18:11 --- quit: Quartus__ (Read error: 104 (Connection reset by peer))
14:46:15 --- quit: forther_ ("Leaving")
15:12:43 --- join: crest_ (n=crest@p5489D530.dip.t-dialin.net) joined #forth
15:17:56 --- quit: Crest (Read error: 110 (Connection timed out))
15:34:59 --- join: tnovelli (n=me@pool-72-79-234-10.spfdma.east.verizon.net) joined #forth
15:36:08 --- join: H4n1 (n=Hans@70.91.193.46) joined #forth
15:38:58 --- quit: H4ns (Read error: 110 (Connection timed out))
15:48:36 --- quit: crc (Read error: 101 (Network is unreachable))
15:53:20 --- nick: H4n1 -> H4ns
15:59:37 --- quit: crest_ ("Leaving")
16:26:04 --- join: arcus_ (n=Miranda@130.195.209.73) joined #forth
16:29:06 --- quit: arcus_ (Read error: 104 (Connection reset by peer))
16:45:11 <slava> http://www.crooksandliars.com/2007/08/06/worst-excuse-ever/
16:47:39 --- quit: slava ()
16:49:04 --- join: H4n1 (n=Hans@70.91.193.41) joined #forth
17:02:01 --- quit: H4ns (Read error: 110 (Connection timed out))
17:16:19 --- join: crc (n=crc@pool-70-110-138-203.phil.east.verizon.net) joined #forth
17:36:02 --- join: dgd2 (n=dgd@166.226.31.6) joined #forth
17:38:47 --- mode: ChanServ set +o crc
18:00:23 --- quit: madwork (Read error: 104 (Connection reset by peer))
18:02:09 --- quit: tathi ("leaving")
18:04:34 <I440r> http://news.com.com/2008-1082_3-5065859.html
18:50:03 --- part: tnovelli left #forth
21:50:14 --- log: started forth/07.08.07
21:50:14 --- join: clog (n=nef@bespin.org) joined #forth
21:50:14 --- topic: 'Welcome to #forth. We discuss the Forth programming language and a variety of technical subjects. Introduction and Helpful Reading: http://forthfreak.net/index.cgi?FnFC | ANS/ISO Forth Standard doc: http://tinyurl.com/nx7dx | Gforth compiler: http://tinyurl.com/s8uho | http://quartus.net/search | Paste: http://forth.pastebin.ca | http://angg.twu.net/miniforth-article.html <- due soon. Suggestions? 8-|'
21:50:14 --- topic: set by edrx on [Thu Jul 12 17:04:11 2007]
21:50:14 --- names: list (clog Quartus__ edrx dgd2 @crc H4n1 Baughn nighty^ @Quartus rehges maht_ uiuiuiu @JasonWoof TreyB madgarden tlockney mem4tim timlarson cmeme kc5tja gnomon uiuiu slava32 segher mrsbrisby ccfg @I440r warpzero)
21:57:18 --- quit: dgd2 (Read error: 110 (Connection timed out))
23:00:56 --- quit: Quartus (Connection timed out)
23:01:09 --- join: Quartus (n=neal@CPE0001023f6e4f-CM001947482b20.cpe.net.cable.rogers.com) joined #forth
23:01:09 --- mode: ChanServ set +o Quartus
23:20:30 --- quit: edrx (Read error: 113 (No route to host))
23:23:12 --- join: dgd2 (n=dgd@166.226.154.35) joined #forth
23:42:09 --- join: ecraven (i=nex@eutyche.swe.uni-linz.ac.at) joined #forth
23:59:59 --- log: ended forth/07.08.07