00:00:00 --- log: started forth/06.02.10 00:08:39 --- quit: Cheery ("Leaving") 00:22:53 --- join: Cheery (i=Henri@a81-197-3-163.elisa-laajakaista.fi) joined #forth 04:31:03 --- join: amca (n=plump@as-bri-3-59.ozonline.com.au) joined #forth 04:31:12 --- quit: amca (Read error: 104 (Connection reset by peer)) 05:14:32 --- join: PoppaVic (n=pete@0-1pool66-214.nas22.chicago4.il.us.da.qwest.net) joined #forth 07:40:01 --- nick: Quiznos -> QuiznosOnDate 08:17:19 --- join: Robert (n=robert@unaffiliated/robert) joined #forth 08:17:42 Does anyone know which protocol ordinary 3.5" PC floppy drives use? 08:17:59 * Robert notes that a floppy drive is about as cheap as a small Flash memory, and gets ideas. 08:18:24 protocol? /dev/.... 08:19:34 Robert: but they're slow and unreliable 08:19:42 True. 08:20:06 ...but cheap. 08:20:11 :) 08:20:22 well, sure, it shouldn't be too hard to get one for free 08:20:30 so are cd-rw 08:20:32 Yeah. 08:20:34 lots of people have an old pc they keep around for parts or something 08:20:42 * Robert nods. 08:20:43 * PoppaVic raises his paw ;-) 08:20:48 So I'd like to know how to interface it. 08:20:56 just like any other drive 08:21:34 I mean from a hardware point of view. 08:21:49 that's what I said 08:22:15 floppies never really report as well as cd/dvd drives, though 08:22:36 Robert: you making an OS? 08:22:38 maybe you need a punchtape machine ;-) 08:22:42 JasonWoof: No, I mean electrically. 08:22:47 From e.g. a microcontroller. 08:23:44 Robert: you trying to make something? or are you just curious? 08:24:47 I'm planning to make something eventually, yeah, but no specific plans yet. 08:37:40 cool 08:46:39 --- quit: PoppaVic ("Pulls the pin...") 08:48:20 --- join: PoppaVic (n=pete@0-2pool238-198.nas24.chicago4.il.us.da.qwest.net) joined #forth 09:23:24 --- quit: PoppaVic ("Pulls the pin...") 09:31:03 --- join: PoppaVic (n=pete@0-1pool46-217.nas30.chicago4.il.us.da.qwest.net) joined #forth 10:51:02 --- quit: PoppaVic ("calls it a Knight - Once a knight is enough") 10:57:06 --- join: snowrichard (n=richard_@adsl-69-155-177-158.dsl.lgvwtx.swbell.net) joined #forth 10:57:13 Hi. 10:57:22 hello 10:57:42 been trying out APLX free version. found a bug 10:58:06 What's APLX? 10:58:17 a version of the APL language for linux 10:58:44 from microapl in britain 10:59:34 Ah, OK. 10:59:40 what the... isn't IS part of the ans forth standard? 11:01:11 my satellite radio keeps cutting out -- rain 11:01:55 DEFER/IS isn't part of ANS. It's a proposed extension, though, and you'll find it all over. 11:02:17 Anton Ertl has an implementation up that should be easy to find. 11:11:36 --- part: snowrichard left #forth 11:13:55 I was just looking up the calling conventions for IS and was supprised not to find it in my usual reference 11:14:08 but I got it right on the seccond guess :) 11:14:35 looks like I can catch all output in gforth if I override EMIT and TYPE 11:33:46 ahh :) and sometimes forth code just comes out beautifully 11:33:56 I sat down to write two words 11:34:08 wrote one, and then realized that the first 2/3 of it did what I wanted the seccond word to do 11:34:12 factor! 11:39:13 --- quit: Robert (Nick collision from services.) 11:40:50 I don't understand... 11:40:50 : etype for dup b@ emit 1+ next drop ; ' etype is type ok 11:40:51 see type 11:40:51 : type 11:40:51 etype 0= 11:40:53 IF 2drop EXIT 11:40:56 THEN 11:40:58 type ; ok 11:42:48 I told it to override type 11:42:59 with etype 11:43:10 but instead it changed the definition of type to something totally weird 11:43:18 not what it was before, and not what I told it to change to 12:03:52 --- nick: QuiznosOnDate -> Quiznos 12:39:37 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 12:47:28 --- join: neceve (n=Clau@unaffiliated/neceve) joined #forth 13:01:04 --- join: TheBlueWizard (i=TheBlueW@ts001d0582.wdc-dc.xod.concentric.net) joined #forth 13:08:09 JasonWoof, possibly type isn't a deferred word? 13:11:36 It works for me... 13:12:43 Actually works here too. What Forth are you working in? 13:13:45 oh, I was assuming it was the cgi stuff he was working on in gforth 13:13:57 Works in Gforth 6.2. 13:14:22 From the looks of the result, the IS is just jamming the xt into the word in question, overwriting something. 13:14:28 JasonWoof's result, that is. 13:14:44 yeah 13:27:00 --- quit: uiuiuiu (Read error: 104 (Connection reset by peer)) 13:32:07 --- join: uiuiuiu (i=ian@dslb-084-056-221-030.pools.arcor-ip.net) joined #forth 13:33:56 never mind my IS issues. I didn't realize I had already redefined type. thus it was not defered 13:34:23 thanks for the help 13:34:32 I should have isolated it to test better 13:35:24 I cleaned up my phone number pretty printer considerably 13:36:14 although the bit that removes 1s from the begining is still ugly 13:37:19 Well get back in and fix it, mister 13:41:28 --- quit: Cheery ("Leaving") 14:05:40 --- quit: neceve (Read error: 110 (Connection timed out)) 14:41:29 You tell'em Quartus. Kids these days. Leaving their 1s all over the place. 14:42:21 What are ya gonna do? 14:48:51 --- join: crc (i=crc@pool-151-197-233-76.phil.east.verizon.net) joined #forth 14:49:15 --- mode: ChanServ set +o crc 15:21:01 --- join: ThinkingInBinary (n=tom@pool-68-163-237-248.bos.east.verizon.net) joined #forth 15:21:17 Quartus: hey 15:31:09 Hey 15:31:28 Quartus: I might be picking up my PIC this weekend. 15:31:44 Neat. 15:31:49 Yeah, it should be fun. 15:32:10 I'm already drooling over all the cool little "hackish" assembly language features it has. 15:33:22 hi crc 15:33:24 Fun indirect addressing, and a really cool way to access up to 96 bytes of RAM in a sliding "window". 15:33:29 hi virl 15:37:14 Sounds neat. 15:38:02 Quartus: A few questions... Should I implement multitasking? Do you think it would be cool to build a better version with 4 of the new 16-bit PIC's running in parallel? Can I do ANS in 32k program FLASH and ~3900 bytes RAM? 15:39:06 Start with the basics; branch out from there. And yes, you should be ok in that space, for small apps. 15:39:42 Quartus: I think a 16-bit SMP FORTH system in my pocket would be insanely sweet. After I build this, of course. 15:40:18 :) 15:40:46 Quartus: Although I'd probably want a von Neumann architecture for the SMP one. 15:43:21 What would that entail? 15:44:35 Quartus: von Neumann architecture is when a CPU has shared code/data memory. (Harvard architecture is when they're separate, like on PIC's. It's popular with them because it puts code and data access on separate busses and allows the CPU to simultaneously read/write memory while prefetching the next instruction.) 15:45:29 Oh, right. 15:45:37 I'd forgotten the terminology. :) 15:45:49 No problem. 15:45:54 I always forget which is which. 15:46:01 I remembered Harvard. 15:49:17 --- part: TheBlueWizard left #forth 15:55:27 --- quit: Teratogen (Remote closed the connection) 15:56:12 ThinkingInBinary, if space proves to be a problem, moving to tokenized Forth might be one way to go. 15:57:07 Quartus: Well, with 16-bit addresses (24-bit for machine code), and probably a thirst for >256 words, it's almost the same. 15:57:22 Quartus: Actually, 12-bit RAM and 15-bit machine code. 15:58:21 Quartus: Gotta go, see you later. 15:58:50 --- part: ThinkingInBinary left #forth 16:59:41 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-150-008.pools.arcor-ip.net) joined #forth 17:08:16 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 17:08:26 --- nick: snoopy_1711 -> Snoopy42 17:10:00 --- join: sproingie (n=chuck@64-121-2-59.c3-0.sfrn-ubr8.sfrn.ca.cable.rcn.com) joined #forth 17:42:49 --- quit: tathi ("leaving") 17:58:25 --- join: TheBlueWizard (i=TheBlueW@ts001d0672.wdc-dc.xod.concentric.net) joined #forth 18:02:07 --- quit: madgarden ("?OUT OF DATA ERROR") 18:08:33 --- join: madgarden (n=madgarde@Toronto-HSE-ppp3713137.sympatico.ca) joined #forth 18:34:24 --- join: crc_ (i=crc@pool-70-110-161-70.phil.east.verizon.net) joined #forth 18:39:06 --- quit: crc (Read error: 110 (Connection timed out)) 18:44:44 --- nick: crc_ -> crc 19:08:07 --- join: crc_ (i=crc@135-pool1.ras04.jfk01.dial.cogentco.com) joined #forth 19:20:41 --- part: TheBlueWizard left #forth 19:20:58 --- quit: crc (Read error: 110 (Connection timed out)) 19:28:07 --- join: ThinkingInBinary (n=tom@pool-68-163-237-248.bos.east.verizon.net) joined #forth 19:39:48 --- part: ThinkingInBinary left #forth 19:39:52 --- join: ThinkingInBinary (n=tom@pool-68-163-237-248.bos.east.verizon.net) joined #forth 19:52:50 --- quit: crc_ (Read error: 110 (Connection timed out)) 20:11:31 --- join: segher (n=segher@dslb-084-056-138-228.pools.arcor-ip.net) joined #forth 20:19:41 --- nick: skylan_ -> skylan 20:24:57 --- quit: ThinkingInBinary (Remote closed the connection) 20:25:51 --- quit: segher_ (Read error: 110 (Connection timed out)) 20:26:32 --- quit: JasonWoof ("shutting down to plug in a hard drive") 20:45:05 --- join: JasonWoof (n=jason@pdpc/supporter/student/Herkamire) joined #forth 20:45:05 --- mode: ChanServ set +o JasonWoof 20:46:49 --- quit: JasonWoof (Client Quit) 20:51:58 --- join: asymptote (n=weldon@199.73.33.226) joined #forth 20:53:57 --- join: JasonWoof (n=jason@pdpc/supporter/student/Herkamire) joined #forth 20:53:57 --- mode: ChanServ set +o JasonWoof 21:30:51 --- quit: sproingie (Remote closed the connection) 21:35:57 --- quit: asymptote ("Leaving") 23:19:10 --- join: OrngeTide (i=orange@rm-f.net) joined #forth 23:39:44 --- join: Cheery (i=Henri@a81-197-3-163.elisa-laajakaista.fi) joined #forth 23:39:57 --- quit: JasonWoof ("good night!") 23:59:59 --- log: ended forth/06.02.10