00:00:00 --- log: started retro/10.05.11
01:01:11 --- quit: nigol (Ping timeout: 252 seconds)
02:54:14 --- quit: sixforty (Quit: Leaving.)
08:08:03 --- quit: crc (Ping timeout: 246 seconds)
08:09:55 --- join: crc (~charlesch@184.77.185.20) joined #retro
08:14:42 --- join: docl (~luke@216-161-87-126.ptld.qwest.net) joined #retro
08:25:49 * docl notes the -1 !match can be moved out of the loop and be executed only once.
08:40:39 <docl> ack, there's a bug in the flags of that code. match is 0 when it should be -1.
08:57:14 --- join: virl (~virl__@chello062178085149.1.12.vie.surfer.at) joined #retro
09:31:02 --- quit: docl (Ping timeout: 264 seconds)
12:24:33 --- quit: virl (Remote host closed the connection)
17:37:45 --- join: sixforty (~sixforty@pdpc/supporter/active/sixforty) joined #retro
17:46:20 --- quit: sixforty (Quit: Leaving.)
17:56:02 --- join: docl (~luke@216-161-87-126.ptld.qwest.net) joined #retro
18:40:05 --- join: sixforty (~sixforty@pdpc/supporter/active/sixforty) joined #retro
19:03:26 --- quit: probonono (Ping timeout: 245 seconds)
20:45:29 <docl> compare% works now
20:48:26 <docl> question: is zeither ( whether either char is null) more readable if it returns 0 for either being null, or should it return true when either is null?
20:51:45 <docl> : zeither ( nn-f ) 0 =if drop -1 ;then 0 =if -1 ;then 0 ;
20:51:45 <docl> : char-compare ( nn-f) 2dup zeither -rot =if not ;then !match 0 ;
20:51:51 <docl> or
20:51:55 <docl> : zeither ( nn-f ) 0 =if drop 0 ;then 0 =if 0 ;then -1 ;
20:51:55 <docl> : char-compare ( nn-f) 2dup zeither -rot =if ;then not !match 0 ;
20:54:42 <docl> (the char-compare flag tells whether to exit the loop)
20:58:00 --- join: virl (~virl__@chello062178085149.1.12.vie.surfer.at) joined #retro
21:40:38 --- quit: sixforty (Quit: Leaving.)
22:07:10 --- quit: retro-commit (Ping timeout: 240 seconds)
22:23:22 --- quit: virl (Remote host closed the connection)
22:29:36 --- quit: docl (Ping timeout: 252 seconds)
23:59:59 --- log: ended retro/10.05.11