00:00:00 --- log: started forth/05.12.07
00:39:22 --- join: I440r (n=_I440r_@rrcs-24-242-160-169.sw.biz.rr.com) joined #forth
00:48:01 --- quit: JasonWoof ("off to bed")
00:49:43 --- quit: amca ("d34d")
04:21:28 --- join: PoppaVic (n=pete@0-2pool198-17.nas30.chicago4.il.us.da.qwest.net) joined #forth
05:17:11 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth
06:01:44 --- nick: Raystm2 -> nanstm
08:38:54 --- quit: PoppaVic (Read error: 110 (Connection timed out))
08:39:10 --- join: virl (n=hmpf@chello062178085149.1.12.vie.surfer.at) joined #forth
10:50:20 --- join: zoly (n=l@p549DCF2F.dip.t-dialin.net) joined #forth
10:50:51 <zoly> 'morning
10:50:53 --- join: amca (n=plump@as-bri-3-105.ozonline.com.au) joined #forth
10:51:11 --- join: JasonWoof (n=jason@c-71-192-20-4.hsd1.ma.comcast.net) joined #forth
10:51:12 --- mode: ChanServ set +o JasonWoof
10:52:33 <amca> Morning
10:52:54 <JasonWoof> morning :)
10:53:07 <amca> How are you going this morn?
10:53:19 --- topic: set to 'Welcome to #forth. We discuss the Forth programming language, simplicity, and a variety of technical subjects. The rules are simple: don't spam, don't troll, and speak English, please.' by amca
10:54:40 --- topic: set to 'Welcome to #forth. We discuss the Forth programming language, simplicity, and a variety of technical subjects. The rules are simple: don't spam, troll, or speak English, please.' by zoly
10:55:21 <zoly> :)
10:55:25 <amca> JasonWoof: Is it actually morning where you are?
10:55:31 <amca> Hi zolyu
10:55:33 <amca> Hi zoly
10:55:38 <zoly> hi 
10:55:49 <amca> How are you? Is it morning where you are?
10:56:07 <zoly> morning is what morning feels
10:57:03 <zoly> like, dark outside, no coffee, and reluctant to get out of bed
10:57:33 <zoly> never mind the time. thermodynamically speaking.
10:57:47 <amca> hehe
10:57:52 <amca> I understand that
10:58:05 <amca> Here is it warm and humid and only 05:00
10:58:19 <zoly> coffee?
10:58:25 <amca> Healthy! :)
10:58:40 <amca> Yeah, I know it's boring, but it makes me happy.
10:59:19 <zoly> boring makes you happy?
11:00:28 <zoly> well, may be better as  interesting = dangerous makes you dead
11:01:13 <amca> Well it isnt borning to me. But being high on health and likfe isnt too glamorous to society.
11:01:55 <zoly> i shouldn't think about dangerous. causes my heart to skip beats
11:02:16 <zoly> gf wants to start skydiving and bungee jumping ...
11:02:21 <amca> lol
11:02:25 <zoly> i am scared of heights
11:02:29 <amca> I wanna try rock climbing
11:02:30 <zoly> better, of depth
11:02:35 <amca> And Im scared of heights
11:02:38 <amca> hehe
11:02:38 <amca> yeah
11:02:52 <zoly> i am even more scared of falling
11:02:56 <amca> When Im swimming in a pool, and the bottom is deep, and I can see it, it gives me vertigo
11:03:34 <zoly> most dangerous thing i am doing at a time like this, is playing darts
11:03:46 <amca> lol
11:03:46 <zoly> those have sharp points.
11:03:50 <amca> Drunk?
11:03:58 <amca> On one leg?
11:03:58 <zoly> no. hardly ever
11:04:09 <amca> With naked women trying to distract you?
11:04:18 <amca> and on LSD
11:04:19 <amca> ?
11:04:20 <zoly> now, that would be fun
11:04:21 <amca> :)
11:04:39 <zoly> i can play with closed eyes :)
11:05:09 <amca> hehe
11:05:21 <amca> "Pin the dart on the bouncing mammary"
11:05:31 <zoly> i got two hands
11:07:03 <amca> oh? :)
11:07:13 <amca> What will the non-dart hand do?
11:07:20 <zoly> scratch my ass?
11:07:49 <zoly> lift a pint?
11:07:51 <amca> Why not scratch one of the naked girls asses?
11:08:32 <zoly> yes, why not?
11:09:13 <amca> I dont know. That would have been the first thought I would have had for where to place my non-dart hand.
11:09:57 <zoly> your power of imagination is striking
11:10:17 <amca> Really? :P
11:10:44 <amca> The imaginative part is not that it would be touching said ladies, but *how* it would be touching them ;)
11:11:00 <zoly> tell us
11:11:49 <amca> I'm not sure that that level of detail of that subject matter in this particular channel is appropriate. >.>
11:12:08 <zoly> explain it in RPN terms
11:12:24 <amca> lol
11:13:05 <amca> ok
11:13:25 <amca> I'll nopaste it
11:15:24 <zoly> meanwhile, here is the Hungarian Phrasebook, for a laugh: http://www.thisisawar.com/LaughterMPHungarian.htm
11:17:04 <amca> Please fondle my buttocks!
11:17:12 <zoly> Bailiff: "I quote an example. The Hungarian            phrase meaning 'Can you direct me to the station?' is translated by            the English phrase, 'Please fondle my bum.'"
11:19:37 * amca loves Python humour and needs to buy some DVDs and CDs 
11:20:01 <amca> http://www.rafb.net/paste/results/CGssyN52.html
11:20:37 <amca> I have a tape of The Final Ripoff (I think)
11:20:43 <amca> audio tape
11:21:05 <amca> Do you see any modifications to my code that would be benificial?
11:24:38 <segher> amca: like this:  http://www.rafb.net/paste/results/J4V4Ob18.html
11:25:25 * amca looks
11:26:19 <amca> Dont need the 0?
11:26:35 <segher> why would you need it?
11:27:04 <segher> it can't be eaten by the loop, and it can't be eaten by anything after the loop (as it is an infinite loop)
11:27:08 <amca> I forgot about how to use loops, and when I looked at the gforth docs...
11:28:02 <segher> http://www.rafb.net/paste/results/aO351e70.html
11:28:04 <zoly> amca, you don't need to repeatedly stack the girls within the loop if you push them before, and just dup them within
11:28:24 <segher> there, even shorter.  and it will crash on bad^H^H^Hless optimal compilers :-)
11:28:59 <segher> zoly: heh
11:29:20 <amca> GIRLS is an array. NAKED selects from that array the girls that are naked.
11:29:58 <zoly> maybe "choose" or "any" would be a better name?
11:30:05 <amca> segher: Do you have a url on the use of RECURSE?
11:30:18 <segher> it's part of the ANS
11:30:32 <segher> iirc, anyway
11:30:39 --- join: PoppaVic (n=pete@0-1pool47-214.nas30.chicago4.il.us.da.qwest.net) joined #forth
11:30:51 <amca> ANS isnt very userfriendly for learning stuff :)
11:31:17 <segher> RECURSE just calls the definition it is part of
11:31:57 <PoppaVic> : recurse  
11:31:58 <PoppaVic>   lastxt compile, ; immediate compile-only ok
11:32:17 <PoppaVic> He's right, though... ANS is just this side of "shoot me - please"
11:32:53 <segher> : recurse  ?comp latest @ link> compile, ; immediate    on my system :-)
11:35:25 <amca> zoly: How would you use "choose" in DARTLESS?
11:35:52 <zoly> gal choose
11:35:56 <segher> .... girls ['] naked? choose ....
11:36:15 <PoppaVic> oh.. vector-indices
11:36:24 <amca> what does ['] do?
11:36:47 <PoppaVic> in many ways, C is a lot more simple ;-)
11:36:58 * amca hasnt come up against ['] yet
11:37:06 <PoppaVic> : [']  
11:37:06 <PoppaVic>   '  POSTPONE ALiteral ; immediate compile-only ok
11:37:42 <PoppaVic> : '  
11:37:42 <PoppaVic>   (') name?int ; ok
11:37:51 <zoly> girl choose undress
11:38:02 * PoppaVic knows he told you to toy w/i gforth ;-)
11:38:13 --- join: lscd (n=lscd@adsl-213-180-182-5.cybernet.ch) joined #forth
11:38:56 <amca> PoppaVic: w/i = ?
11:39:05 <PoppaVic> with[in]
11:39:30 <PoppaVic> having 'see' around is sooo handy
11:40:02 <amca> see will tell me how, not what
11:40:24 <amca> zoly: choose would be a parsing word?
11:40:30 <PoppaVic> apropos and info/manpages a book.. For gforth, it's info-files
11:40:45 <zoly> no.  girl would possible return address and count
11:41:13 <PoppaVic> hmm
11:41:24 <amca> could you please put that differently? I didnt understand you
11:41:36 <zoly> what could is girl without address?
11:41:42 <zoly> good...
11:41:47 <PoppaVic> choose ( base-a offset -- )
11:41:55 <PoppaVic> that's a rough approx
11:41:55 <amca> girls \ pointer/address to array of girls
11:42:27 <PoppaVic> girls redhead nude choose ...
11:43:40 <amca> need to do something like "for each girl, fondle if naked"
11:44:19 <PoppaVic> sounds tedious
11:44:38 <lscd> leave it to us, then. 
11:44:43 <amca> you have a quicker algorithm?
11:45:15 <lscd> unless you can make it run in parallel (isn't this an embarassingly parallel problem? but your hands/etc may be a limiting factor), i don't see how you're going to beat O(N) time
11:45:30 <PoppaVic> girls 0 do ." already had sex; take nap" cr loop ;
11:45:38 <amca> well we only have one hand, so it is linear, rather than parallel by nature
11:45:58 <lscd> if you limit to that one hand, sure
11:46:04 <lscd> otoh, you have knees, and there are other people playing darts
11:46:15 <amca> Well you could possibly use both feet too I suppose
11:46:29 <lscd> i thought of that, but some would probably object
11:46:30 <PoppaVic> ok, yah lost me 3 curves ago.
11:46:33 <amca> But we are writing the code for just one player
11:46:47 <PoppaVic> are you _trying_ to multithread? coprocess?
11:46:58 <lscd> apparently not
11:47:13 <amca> PoppaVic: We are seeing if multithreading is applicable to this situation
11:47:19 <PoppaVic> doubtful
11:47:34 <amca> And unless we want to use feet as well as the dartless hand, then probably not
11:48:09 <lscd> amca: basically, it really comes down to whether or not you're willing to share
11:48:09 <PoppaVic> maybe it's a "detached thread" ;->
11:48:16 <lscd> if you are, multithreading would be useful
11:48:26 <amca> lscd: We arent willing to. :)
11:48:35 <amca> PoppaVic: :P
11:48:37 <lscd> typical :D
11:48:44 <zoly> this is more like a multifingered app
11:49:03 <lscd> zoly: yeah, but your fingers don't stretch far enough to count significantly
11:49:04 <lscd> i think
11:49:07 <PoppaVic> Sounds like sloppy 2nds, 3rds and (other), to me
11:51:51 <amca> so, say GIRLS is an address to an array of girls, to iterate through each girl, you would increment the index by the size of GIRL, right?
11:52:05 <PoppaVic> yep
11:52:29 <lscd> that would be problematic if GIRL wasn't a constant size though
11:52:52 <amca> lscd: All the same *****, different faces.
11:53:24 <amca> and then for each girl, you would use the offset to the clothing status to test said status to find out if to fondle, right?
11:53:34 <lscd> amca: ooh. no points. ;)
11:54:51 <segher> just always fondle, and let it THROW if it fails
11:55:06 <amca> so you would have somehting like 'num-girls 0 DO I +naked IF... THEN LOOP'
11:55:07 <amca> ?
11:55:46 <segher> #girls 0 ?DO naked i cells + ['] fondle CATCH drop LOOP
11:55:46 <amca> hmm...no that wouldnt work
11:56:19 --- quit: PoppaVic ("tootles, lads")
11:56:25 <humulus> i have a fucking problem
11:56:40 <amca> This has got to be the geekiest chat about sex I have ever had
11:56:40 <segher> so does amca, it seems ;-P
11:56:45 <amca> lol
11:56:53 <amca> Yeah - my gf is at her place, not here :/
11:56:56 <amca> humulus: What is it?
11:57:06 * amca is gonna save this log
11:57:11 <humulus> amca: i talked to you yesterday?
11:57:14 <humulus> : asm-xo-1 ( n "name" -- )
11:57:14 <humulus>   name { n addr len }
11:57:14 <humulus>   ['] asm-xo-21,31-00 n addr len s" " asm-xo-1-define
11:57:14 <humulus>   ['] asm-xo-21,31-01 n addr len s" ." asm-xo-1-define
11:57:14 <humulus>   ['] asm-xo-21,31-10 n addr len s" o" asm-xo-1-define
11:57:15 <amca> yep
11:57:16 <humulus>   ['] asm-xo-21,31-11 n addr len s" o." asm-xo-1-define ;
11:57:20 <humulus> that is my word
11:57:27 <amca> O_O
11:57:34 <amca> Out of my knowledge
11:57:44 <humulus> when i comment the last line out it works
11:58:26 <humulus> when i start forth it stack underflow
11:58:44 <humulus> i can paste the relevant rest too
11:58:49 <segher> : print-o-and-.
11:59:03 <amca> humulus: use nopaste for any lengthy code please
11:59:07 <segher> ( opcode -- ) dup 2 and IF [char] o emit THEN
11:59:15 <segher> 1 and IF [char] . emit THEN ;
11:59:43 <humulus> segher: is that for me/
11:59:49 <segher> guess so, yes
12:00:32 <humulus> i do not know how that should help me?
12:01:17 <segher> your code looks like it does the disassembly of "o" and "." on powerpc, correct?  so does my code, and it is quite a bit simpler ;-)
12:01:42 <segher> you're juggling way too much stuff on the stack
12:01:43 <humulus> that is the assembler :)
12:01:49 <segher> oh okay
12:01:58 <humulus> so what
12:02:13 <segher> that's not very fortish ;-)
12:02:37 <segher> you want to have the same input syntax as "normal" assemblers?
12:03:02 <humulus> no 
12:03:04 <humulus> postfix
12:03:08 <segher> ah
12:03:33 <segher> then, why not just make a forth word that modifies the last emitted asm insn to have an "o" modifier, etc?
12:04:04 <humulus> it seems that the last line comsumes to much stuff from the stack
12:04:19 <segher> so you'd say for   addeo 3,4,5    3 4 5 addeo,    and for    addeo. 3,4,5    3 4 5 addeo,   .,
12:04:53 <humulus> but i do not why cuz asm-xo-21,31-10 is quite the same then asm-xo-21,31-11
12:05:44 <humulus> : asm-xo-21,31-10 ( ... n -- ... code )
12:05:45 <humulus>   \ sets bit 21 to 1 and 31 to 0
12:05:45 <humulus>   1 lshift $400 or ;
12:05:45 <humulus> : asm-xo-21,31-11 ( ... n -- ... code )
12:05:45 <humulus>   \ sets bit 21 to 1 and 31 to 1
12:05:47 <humulus>   1 lshift $401 or ;
12:07:09 <segher> : 2*   1 lshift ;    is a standard word
12:07:25 <humulus> ok but that's not the reason ;o)
12:07:33 <segher> of course, just a side note :-)
12:07:34 <JasonWoof> sorry, forgot all about irc for a long while
12:07:52 <JasonWoof> no, not morning, but I had just gotten up... so it's nice to hear "good morning"
12:08:02 <humulus> morning ;)
12:08:06 <lscd> good morning
12:08:25 <humulus> well i'm about to do svn commit :D
12:08:58 <amca> hehe
12:09:03 <amca> JasonWoof: How are you?
12:09:33 <JasonWoof> hehe :)
12:09:46 <JasonWoof> wow, I seem to be getting a might bit cranky
12:09:50 <JasonWoof> I better eat something
12:10:11 <amca> What yummy food will you select?
12:11:13 <JasonWoof> leftover borito
12:11:19 <amca> yummy!
12:11:25 <JasonWoof> salivating just thinking about it
12:11:40 <JasonWoof> humulus: I don't understand your asm-xo-* words
12:12:11 <JasonWoof> humulus: they are supposed to set those two bits to certain values, and leave the other bits alone?
12:12:20 <humulus> yeah
12:12:34 <humulus> how much stuff can i past without being kicked ;O)
12:12:36 <JasonWoof> doesn't look like they do anything of the sort
12:13:06 <JasonWoof> eg you start out by moving all the bits in the input
12:13:26 <humulus> well they actually set all the bits in the range 21 to 31
12:13:59 <JasonWoof> to what?
12:19:56 <JasonWoof> the words you pasted above do not set bits in a range, they shift everything up one bit, then set the 2 bits as you described in the comments
12:20:40 <amca> I'm off now, so I shall catch you perverted programmers later
12:20:57 --- quit: amca ("d34d")
12:30:41 * JasonWoof drops like flies
13:01:37 --- part: segher left #forth
13:13:50 --- quit: saon ("brb, changing to ion")
13:15:30 --- join: saon (i=1000@unaffiliated/saon) joined #forth
14:05:20 --- quit: madgarden (Read error: 110 (Connection timed out))
14:06:20 --- nick: lscd -> lscd-sleep
14:22:54 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-131-119.pools.arcor-ip.net) joined #forth
14:30:15 --- quit: Snoopy42 (Nick collision from services.)
14:30:50 --- nick: snoopy_1711 -> Snoopy42
15:33:20 --- join: aum (n=aum@60-234-156-82.bitstream.orcon.net.nz) joined #forth
16:38:30 --- part: zoly left #forth
17:02:37 --- join: madgarden (n=madgarde@Toronto-HSE-ppp3708198.sympatico.ca) joined #forth
17:24:40 --- quit: madgarden (Read error: 110 (Connection timed out))
17:50:06 --- quit: crc (Remote closed the connection)
17:55:47 --- join: crc (i=crc@pool-70-110-139-103.phil.east.verizon.net) joined #forth
18:01:28 --- join: amca (n=plump@as-bri-1-71.ozonline.com.au) joined #forth
18:07:06 --- mode: ChanServ set +o crc
18:12:16 --- join: sproingie (n=chuck@64-121-2-59.c3-0.sfrn-ubr8.sfrn.ca.cable.rcn.com) joined #forth
18:22:10 --- quit: saon ("leaving")
18:23:01 --- join: saon (n=saon@unaffiliated/saon) joined #forth
18:32:48 --- quit: saon ("brb")
18:33:20 --- join: saon (i=1000@unaffiliated/saon) joined #forth
19:01:06 --- join: madgarden (n=madgarde@London-HSE-ppp3545637.sympatico.ca) joined #forth
19:21:19 --- quit: tathi ("leaving")
20:21:37 --- quit: crc (Read error: 104 (Connection reset by peer))
20:23:48 <amca> Time for a siesta. Catch you all later.
20:23:52 --- quit: amca ("d34d")
20:57:00 --- join: swalters_ (n=swalters@6532183hfc82.tampabay.res.rr.com) joined #forth
21:33:10 --- quit: aum ()
22:28:46 --- quit: sproingie (Remote closed the connection)
22:34:14 --- join: amca (n=plump@as-bri-4-1-59.ozonline.com.au) joined #forth
22:35:52 <amca> Is it possible in forth to have named stack parameters, or would it make it another language? e.g. have a word which expects 3 parameters on the stack, and can refer to their stack position by a name.
22:43:49 <JasonWoof> amca: yes, this is called "local variables" and some forths support it
22:44:10 <JasonWoof> I think gforth does
22:44:19 <JasonWoof> you name the parameters in your stack comment
22:45:01 <JasonWoof> eg you can do something like:   : foo (( a b c -- ) a b + c ! ;
22:45:15 <JasonWoof> I don't have any idea what that word is where I put ((
22:46:17 <amca> Ah. I didnt realise that they were on the data stack
22:47:16 <amca> That is not the case
22:47:29 <amca> : exp { a b c }  compiled
22:47:29 <amca> .s .  compiled
22:47:29 <amca> .s .  compiled
22:47:29 <amca> .s .  compiled
22:47:29 <amca> .s  compiled
22:47:29 <amca> ;  ok
22:47:31 <amca> 1 2 3 exp <0> 790634787 <-1> 796029813 <-2> 1633906540 <-3>
22:47:33 <amca> *the terminal*:7: Stack underflow
22:47:35 <amca> 1 2 3 exp
22:47:37 <amca>       ^^^
22:48:09 <amca> At least not in gforth. Unless I am getting something wrong
22:48:51 <amca> Ah
22:48:55 <amca> I see
22:49:06 <amca> It pops the items off the stack into the local vars
22:50:35 <amca> I was thinking more of leaving the items on the stack, and having the labels more like array indexes that you can use to directly reference the variables
22:51:05 <amca> Anyone know if gforth local vars are reentrant?
23:02:47 <JasonWoof> yeah, it pops them off. because otherwise you couldn'd to this:  : foo { a b c -- ) a b + c ! ;
23:03:12 <JasonWoof> should be reentrant
23:04:19 * amca nods
23:04:38 <amca> So gforth would allocate the locals on the heap
23:27:38 --- quit: amca ("storm")
23:59:59 --- log: ended forth/05.12.07