00:00:00 --- log: started retro/12.01.28
04:34:16 --- join: karswell__ (~coat@93-97-29-243.zone5.bethere.co.uk) joined #retro
04:36:59 --- quit: karswell_ (Ping timeout: 276 seconds)
06:10:00 --- join: Kumul (~Kumul@67.224.209.208) joined #retro
06:58:37 --- join: karswell (~coat@93-97-29-243.zone5.bethere.co.uk) joined #retro
07:00:14 --- quit: karswell__ (Ping timeout: 252 seconds)
09:23:36 --- join: karswell_ (~coat@93-97-29-243.zone5.bethere.co.uk) joined #retro
09:23:45 --- quit: karswell (Ping timeout: 244 seconds)
10:04:40 --- join: erider (~chatzilla@pool-173-69-151-233.bltmmd.fios.verizon.net) joined #retro
10:04:46 <erider> hi all 
15:27:35 --- quit: TheStitch (Ping timeout: 240 seconds)
16:01:55 <erider> hi all 
16:04:29 <crc> Hi erider
16:04:57 <erider> hey crc how goes it 
16:05:31 <erider> crc: hey does EOF == -1 
16:05:50 <crc> Not necessarily 
16:07:11 <erider> what is it? 
16:07:37 <crc> It could also be zero or something else depending on the host OS
16:09:34 <erider> hmm 
16:18:50 <crc> In C89, it's defined as an implementation specific negative integer 
16:19:40 <crc> It should be defined in stdio.h 
16:30:28 <erider> I got it I just didn't want to use any header files 
16:30:38 --- quit: karswell_ (Read error: Operation timed out)
16:31:35 <crc> Most systems will use -1
16:32:40 --- join: karswell_ (~coat@93-97-29-243.zone5.bethere.co.uk) joined #retro
16:32:52 <crc> But you can't guarantee portability if you hardcode that
16:34:47 <erider> (c & 0xf) << 4) | (d & 0xf) will this convert char to hex 
16:52:40 <erider> crc: brb 
17:05:13 <erider> ok back 
18:07:37 --- quit: erider (Remote host closed the connection)
18:08:05 --- join: erider (~chatzilla@pool-173-69-151-233.bltmmd.fios.verizon.net) joined #retro
18:17:46 <erider> chao 
18:17:51 --- quit: erider (Quit: ChatZilla 0.9.88 [Firefox 5.0/20110615151330])
21:02:32 --- quit: Kumul (Quit: gone)
23:59:59 --- log: ended retro/12.01.28