00:00:00 --- log: started retro/06.11.14
04:42:58 --- join: Raystm2 (n=NanRay@adsl-68-95-251-145.dsl.rcsntx.swbell.net) joined #retro
04:56:33 --- mode: ChanServ set +o Raystm2
05:39:24 --- join: _timlarson (n=timlarso@65.116.199.19) joined #retro
05:45:32 --- join: Ray_work (n=Raystm2@199.227.227.26) joined #retro
05:47:01 <Ray_work> Good morning.
06:07:04 --- nick: Raystm2 -> nanstm
06:28:50 <lukeparrish> good morning
06:29:10 --- mode: ChanServ set +o lukeparrish
06:59:44 <Ray_work> hey there lukeparrish. Hope you are well today and everyday.
07:07:55 <lukeparrish> yup very well today, and most days
08:06:46 --- part: forther left #retro
08:26:51 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #retro
08:42:16 --- join: neceve (n=claudiu@unaffiliated/neceve) joined #retro
09:02:22 --- quit: Quartus (Read error: 104 (Connection reset by peer))
09:50:49 <lukeparrish> Is there already a version of for in retro that counts upwards?
09:51:21 * lukeparrish just made one that uses the return stack
09:51:28 <lukeparrish> http://retroforth.net/paste/?id=249
09:56:15 <lukeparrish> seems a little messy though
09:58:41 * Ray_work needs a forth on this computer or a web forth.
09:59:56 --- join: Quartus (n=trailer@CPE0001023f6e4f-CM013349902843.cpe.net.cable.rogers.com) joined #retro
10:06:55 <Ray_work> ooh I got colorForth here, lets see...
10:06:59 <Ray_work> Hi Quartus. :)
10:07:05 <Quartus> Hey.
10:40:00 --- quit: _timlarson (Read error: 104 (Connection reset by peer))
10:44:49 --- join: Snoopy42_ (i=snoopy_1@dslb-084-058-161-248.pools.arcor-ip.net) joined #retro
10:53:00 --- quit: Snoopy42 (Read error: 145 (Connection timed out))
10:53:10 --- nick: Snoopy42_ -> Snoopy42
10:58:50 <Ray_work> lukeparrish:   : for-up dup for dup i - swap next ; 
11:01:32 --- join: _timlarson (n=timlarso@65.116.199.19) joined #retro
11:03:17 <lukeparrish> hmm. that works, but it makes you keep an extra element on the stack
11:08:07 <Ray_work> that's the ( n -- n-many ) version 
11:08:19 <Ray_work> you can adjust it to take a count and a start...
11:09:50 <Ray_work> : for-up2 ( n c -- c-many-n's-incrementing )  for dup i - swap next ; 
11:10:38 <Ray_work> or to ajust for an extra unnecessary element.
11:11:24 <Ray_work> : for-up3 ( n c -- c-many-n's-incrementing ) for dup 1 + 1 - swap next drop ;
11:11:51 <Ray_work> eliminates the first 0 
11:13:40 <Ray_work> or 
11:14:46 <Ray_work> : for-up4 ( n c -- "you know " ) for dup 1 - swap next drop ; \ starts with 0 drops the last element
11:16:46 <Ray_work> I think the problem with the macro you posted... It won't take account for a for with in a for for instance, I'm assuming with out really looking very deeply at it.
11:16:58 <lukeparrish> hmm
11:17:14 <Ray_work> or even an if in a for
11:17:26 <Ray_work> anything that happens to need the return stack.
11:20:29 <lukeparrish> hmm
11:20:44 <lukeparrish> well, you have to use rdrop after next
11:21:16 <lukeparrish> http://retroforth.net/paste/?id=250 has a matching program that uses tail-first matching
11:21:28 <lukeparrish> I'd kind of like to have head-first though
11:22:22 <lukeparrish> like this: http://retroforth.net/paste/?id=251
11:34:07 <lukeparrish> an if in a for is kind of complex anyway, as you have to rdrop before the exit.
11:50:21 <Ray_work> performance wise, I'm sure my versions are faster. understanding wise, I'm certain my versions will be understood. I have to complain about the major complexity where it is unneeded. :)
11:51:48 <lukeparrish> but it's doing something different, isn't it?
11:52:23 <Ray_work> I'm sorry I don't understand the question?
11:53:09 <Ray_work> oh yeah yeah. 
11:53:23 <lukeparrish> the programs I just pasted were for pattern-matching
11:53:25 <Ray_work> I see now. your doing some sort of character matching here.
11:53:38 <Ray_work> I did something similar for chuckBot.
11:53:39 <lukeparrish> sorry, I should have explained better
11:53:42 <Ray_work> collision detection.
11:54:11 <Ray_work> I had to detect when chuckBot met a wall, so that he wouldn't pass thru it.
11:54:41 <lukeparrish> right
11:54:43 <Ray_work> the neat solution was: 
11:55:53 <Ray_work> I took the coords and packed them thusly:   10000 * + 
11:56:25 <Ray_work> same with the wall posititions which were the xy coord of the top left corner of a wall.
11:56:56 <Ray_work> subtracted them with each other and when a match hit it was just test for 0.
12:36:07 --- quit: neceve (Remote closed the connection)
12:38:07 --- nick: nanstm -> tiff
14:01:33 --- quit: Cheery ("Download Gaim: http://gaim.sourceforge.net/")
14:10:10 --- quit: _timlarson ("Leaving")
14:28:42 --- join: forther (n=forther@c-67-180-209-27.hsd1.ca.comcast.net) joined #retro
15:10:24 --- quit: Ray_work (Read error: 104 (Connection reset by peer))
17:24:48 <crc> good evening
17:25:10 <Quartus> Hey crc. How's the patient?
17:26:07 <crc> healing
17:26:22 <Quartus> Good!
17:27:16 <crc> the last of the bandages from the surgery are off, and she can be without the temporary cast for an hour or two at a time without (much) pain
17:27:36 <Quartus> Sounds like it's right on schedule.
17:58:07 --- part: forther left #retro
19:41:56 --- join: forther_ (n=forther@c-67-180-209-27.hsd1.ca.comcast.net) joined #retro
19:52:17 --- quit: forther_ ("Chatzilla 0.9.76 [Firefox 2.0/2006101023]")
22:06:16 --- quit: virl (Remote closed the connection)
22:28:18 --- nick: tiff -> Raystm2
23:59:59 --- log: ended retro/06.11.14