00:00:00 --- log: started forth/04.06.12 00:05:57 --- quit: kc5tja ("THX QSO ES 73 DE KC5TJA/6 CL ES QRT AR SK") 00:40:24 --- join: topher (~chris@lsanca1-ar42-4-61-175-184.lsanca1.dsl-verizon.net) joined #forth 00:49:54 --- join: arke_ (~Chris@wbar8.lax1-4-11-100-108.dsl-verizon.net) joined #forth 00:49:57 --- quit: arke (Read error: 104 (Connection reset by peer)) 01:00:03 --- quit: topher ("Client Exiting") 01:24:22 --- quit: SDO (Read error: 54 (Connection reset by peer)) 01:39:20 --- part: ForthFreak left #forth 02:07:19 --- join: solar_angel (~jenni@Toronto-HSE-ppp3685160.sympatico.ca) joined #forth 04:23:55 --- join: qFox (C00K13S@cp12172-a.roose1.nb.home.nl) joined #forth 06:05:00 Hi qFox 06:10:29 hi 06:11:56 whoa... i've had the weirdest morning. 06:12:04 is DTC really faster than STC on Intel? 06:12:24 i probably just need to actually build in my optimizer... 06:12:32 Heh. 06:12:54 Yes, probably. 06:13:32 --- quit: htp123 (Read error: 60 (Operation timed out)) 06:15:14 Argh, I underestimated the evil of 32-bit addressing on x86. 06:19:40 lol, oh? 06:19:50 * solar_angel underestimated the evil of STC. 06:19:56 Hehe. 06:19:58 although it works now, at least i can say that much. 06:20:00 Ever messed with them? 06:20:04 with what? 06:20:18 The _ordinary_ rules are evil enough, but then there's a huge pile of exceptions. 06:20:23 32-bit addressing on x86. 06:20:39 lol, you're working on an assembler? 06:21:02 I'll just write a limited assembler, so that something like [NOS] is compiled as [ESI] or whatever. 06:21:10 Yes, for the Forth system. 06:21:18 *nods* same situation for me. 06:21:24 i've got a fair start on a complete assembler. 06:21:27 Using I440r's IsForth right now, though. 06:21:36 Good for you. :) 06:21:56 i'm still trying to get ?DO working now... but that's a recent thing. 06:23:06 I don't think I've ever used ?DO... Always been a fan of simple loops (for/next, tail recursion). Mostly because I can't remember all those loop variants. ;) 06:23:20 heh 06:24:00 --- join: htp123 (~tehsux@S010600055d233ab7.gv.shawcable.net) joined #forth 06:31:20 there are many yeah 06:31:35 Yep. 06:31:46 i use do loop and begin while repeat mostly 06:32:20 i have most of them in my forth compiler... 06:32:23 except for for/next 06:32:31 How many other languages do you think have a serious "These Are The Loop Constructs I Use" debate? ;) 06:32:31 i'm missing that one. 06:32:33 well if you can do one, you can do them all, i think 06:32:48 heh 06:32:48 Robert - how many other languages support "NIP AND TUCK" as valid syntax? 06:32:58 :p 06:33:10 OK, I don't get the joke in that. 06:33:15 nip() and() tuck() 06:33:28 its a surgical procedure, afaik 06:33:35 facelifting etc 06:33:43 or related to.. 06:33:46 Thanks. 06:33:56 hehe 06:34:06 also a tvshow 06:34:08 :) 06:36:33 : now 1 ; : i 2 ; : screw 3 ; : things + ; : up do loop ; NOW I WILL SCREW THINGS UP 06:36:55 *lol* 06:37:02 my FORTH is case sensitive. 06:37:12 i hate it :0 06:37:33 hate what? 06:37:35 cs 06:37:46 i hate case in general. 06:37:52 i don't even capitalize 'i'. 06:37:55 or my name. 06:38:36 I was born to be a pedant. Just tell me if I get too annoying and I'll keep quiet. 06:38:46 well, thats besides the point really. its the confusion and fact that its easier to remember enterthisintowindowsnow then EnterThisIntoWindowsNow type of long intercrap stuff 06:39:28 plus i dont like to write in caps as it means i'd either have to turn on capslock while typing words, or hold shift 06:39:47 heh 06:39:53 i'm willing to type constants in caps though 06:40:10 but thats just something i've learned to do 06:40:31 I wouldn't write much faster without capitalization. 06:40:40 * Robert can't type properly anyway 06:40:47 plus in my source its easy to spot constants that way, since they are the only words written in caps :p 06:41:01 well its not so much faster, as it is easier 06:41:09 minimal, but still.. 06:41:48 Can't beat the amount if time I spend rephrasing everything I type. :) 06:42:00 hehe 07:25:48 --- quit: solar_angel ("*gone gone gone*") 08:38:10 mornin' 08:38:27 --- join: arke__ (~Chris@wbar8.lax1-4-11-100-108.dsl-verizon.net) joined #forth 08:38:57 Hi teehee and arke__ 08:39:12 Oh, same person I guess? 08:39:32 ye3s 08:39:43 Started hacking at that assembler. 08:39:56 --- quit: arke_ (Connection reset by peer) 08:40:27 Not really an assembler, though. 08:40:47 Robert: how far + what does it do? 09:02:56 Not far at all, a few pages of code & definitions. 09:03:19 And it's basically just for the instructions that the Forth needs. 09:03:31 Example: 09:03:32 : SWAP ( -- ) $87 write TOS [NOS] ; 09:03:40 Where: 09:03:42 : TOS ( -- ) EAX ; 09:03:42 : [NOS] ( reg -- ) ESI [NONE] >modrm write ; 09:06:02 --- join: SDO (~SDO@co-trinidad1a-156.clspco.adelphia.net) joined #forth 09:07:38 [NONE]? 09:12:55 Er, yes, meaning no constant is added to ESI. 09:16:47 --- join: kc5tja (~kc5tja@66-74-218-202.san.rr.com) joined #forth 09:16:59 --- mode: ChanServ set +o kc5tja 09:17:05 1hi kc5tja 09:17:19 Greetings 09:17:33 Tja. 09:17:46 Yeah, whatever. :) 09:18:02 It's nice that your suffix means "hi" in Swedish. 09:18:08 ? 09:18:12 I thought it meant "whatever". 09:18:30 Hm, you're right, it has different meanings. 09:18:37 That's why I responded the way I did. :) 09:18:41 Oh. I didn't know that. 09:18:59 If it sounds hesitant, it means something like "well..." 09:20:55 Ahh 09:20:59 That's probably what I was thinking 09:21:56 Don't worry, I probably miss half of what you mean because of lacking English skills. 09:23:11 :) 09:23:43 I need to figure out where to go with Kestrel today. 09:24:03 I think it would probably be best if I can get the emulator to show a frame buffer of some kind. 09:24:25 What do you folk(s) think? 09:37:54 sounds goot 09:37:59 --- nick: arke__ -> arke 09:38:55 Robert: wouldn't something like TOS [NOS] XCGH, be better? :) 09:39:10 XCHG* 09:39:19 yeah 09:39:23 Try to implement it, then. 09:39:34 x86 addressing is a little...well...you'll notice. 09:39:40 odd? :) 09:39:43 kc5tja: Sorry, but I don't know what that means. 09:40:05 Robert: You know what folk is right? (e.g., volk in German) 09:40:09 Robert: he means making bochs for the Kestrel, kinda 09:40:27 kc5tja: Yes. 09:40:27 Robert: just so he can test it, and maybe start developing. 09:40:47 The emulator I have only emulates the CPU, but doesn't address interrupts (yet) nor does it handle keyboard, video, or "disk" I/O. 09:41:01 kc5tja: I meant, what an "emulating showing a framebuffer" means. 09:41:38 A framebuffer is a chunk of memory that contains video data. 09:42:13 Uhm, yes... I just don't see the alternative. 09:42:18 ?? 09:42:22 An emulator that does not emulate video at all? 09:42:23 You're confusing ME now. 09:42:31 Robert: It's a CPU emulator. 09:42:37 It emulates the CPU. 09:42:49 It does not emulate the whole of Kestrel. 09:43:07 OK, and you asked if it was a good idea to emulate the entire Kestrel? 09:43:29 To spend time working on it, yes. There are a few who would prefer I dive right into the Verilog. 09:43:58 But I personally would prefer to get the framebuffer running, so that myself and/or others can generate a body of code that the real CPU can (hopefully) execute when the real CPU is produced. 09:44:26 cool 09:44:36 are you writing the emulator in forth? 09:44:44 lalalim: Yes. It'll run in GForth. 09:44:48 Under Linux. 09:44:54 Ah. I think that's probably best, then. 09:44:54 cool 09:44:58 It will use the SDL library to provide its framebuffer display. 09:45:13 i started writing a simple Chip-8 emulator :) 09:45:33 However, I *MUST* emphasize that the emulation will not be 100% complete, nor will it necessarily be 100% accurate. 09:46:28 As long as the differences won't be HUGE, I guess modifying the code won't be such a bad job. 09:46:36 That's what I'm banking on. 09:46:46 Of course, it all ultimately depends on how the hardware turns out. 09:47:31 I expect the greatest differences in the system to (a) be concealed/dealt with by the MachineForth compiler itself, and (b) most differences are expected to be in the video hardware system. 09:47:44 (e.g., register layouts will likely end up different, etc) 09:48:49 Let's just say that the emulator is the Kestrel "as I currently see it, and preferably, want it." It does not necessarily match future reality when it's done. :) 09:49:17 :) 09:49:54 Actually I'd love having a shot at writing some software for the Kestrel, if a simulator became available. 09:50:08 I'm getting really tired of x86 now. 09:50:18 Will you do something MachineForth-like? 09:50:32 That's the other thing too -- the emulator does not properly deal with real-world timing (yet?). 09:50:45 Robert: Yes. The assembler for it is already in the Kestrel files distribution. 09:50:45 Erm, brb. 09:50:51 It still needs more testing though. 09:50:54 Ah, good! 09:51:03 But people who actually use it will inevitably find and help fix bugs. 09:52:15 Documentation will need to be written for it too. But I think it's best to finish the emulator first. 10:15:58 --- join: topher (~chris@lsanca1-ar42-4-61-178-027.lsanca1.dsl-verizon.net) joined #forth 10:16:01 --- join: chris__ (~chris@lsanca1-ar42-4-61-178-027.lsanca1.dsl-verizon.net) joined #forth 10:16:21 only on MadTV: an actor doing an impression of an actor doing an impression 10:16:27 --- part: chris__ left #forth 10:20:42 --- join: I440r (~FooBlah@168-215-246-243.gen.twtelecom.net) joined #forth 10:27:32 --- quit: topher (Client Quit) 10:32:12 --- join: O3BEPH (~z@193.201.231.126) joined #forth 10:32:57 hi ! 10:32:58 --- nick: O3BEPH -> Serg 10:33:18 i got some ZX forth, but it err's on :test 2 3 * . ; 10:33:24 --- join: topher (~chris@lsanca1-ar42-4-61-178-027.lsanca1.dsl-verizon.net) joined #forth 10:35:28 Serg: You need to put a space between : and test. :) 10:36:26 sure, i forgot it only here ;))))) 10:37:19 * Serg fires up emulator to give it another try 10:39:39 heh, this time worked 10:39:47 It's my technical support field. 10:40:06 sup kc5tja 10:40:15 * Robert returns from the lake. 10:40:19 * kc5tja will be working on my Kestrel emulator some more today. My goal is to get the video and keyboard functionality working. 10:40:21 i found the error: on PC ':' and ':' are same key 10:40:39 ; and : i mean 10:40:41 You mean : and ; ? 10:40:42 :) 10:41:02 on my emu, ';' is LShift-O 10:41:16 but i err-ly used PC key 10:41:31 * kc5tja nods 10:42:01 putting ':' at end too ;) 10:42:24 radio if you guys care 10:42:48 warpzero: ? 10:43:03 Serg: http://wza.us/radio.html 10:43:24 --- nick: Serg -> Serg[GPRS] 10:43:28 ;) 10:47:07 ZX-FORTH v2.7M: 31006 bytes free 10:47:43 Heh, and here I am looking at Firth of Fifth .ogg file, and it's 16MB in size. :D 10:47:52 s/at/at a/ 10:48:16 (of course, the song is also some 10 minutes long, and has a very wide dynamic range too) 10:48:53 * Serg[GPRS] needs to stomp 17G of music down to 32-mono 10:49:31 i have an 11k .mod file of really beautiful music 10:49:55 hmm...I still haven't quite figured out how to handle audio in the Kestrel yet. 10:51:23 The emulator will almost certainly not have audio support. 10:51:23 i seen many SSTV proggies for ZX on my rarities CD 10:51:27 --- quit: arke (Read error: 104 (Connection reset by peer)) 10:51:31 --- join: arke_ (~Chris@wbar8.lax1-4-11-100-108.dsl-verizon.net) joined #forth 10:51:36 i wonder how do they input audio 10:51:47 Probably some kind of hardware hack that you have to build. 10:51:58 hamcomm ? 10:52:29 Well, SSTV can be deciphered easily by a simple level triggering circuit, because it's frequency modulated. 10:52:49 1200Hz is black, and 2400Hz is white, and everything in between are shades of grey. 10:52:57 1000Hz is the sync pulse, if I'm not mistaken. 10:53:03 i know ;) 10:54:02 when i was on trash comp job, i seen folks hunting old multi-cards ;) 10:54:19 coz they were burning ports like matches 10:55:14 Heh 10:56:09 on some RU IRC, i was kicked for saying "C=a+++b" ;))) 10:56:54 I don't even know if that's legal C, since it can be interpreted in a number of ways. 10:57:08 A++ + B or A + ++B 10:57:27 i tryed on DJGPP - compiles, but forgot result 10:58:20 and this is not the only hole in C syntax 11:02:15 Nope. 11:02:40 what nope ? fails to compile ? 11:03:36 Hole in C syntax I guess. 11:03:38 Ambiguity of English: I was agreeing with your comment that it is not the only syntactical hole in C. 11:04:27 * Serg[GPRS] always agrres by Yes and denies by No 11:07:00 While technically correct, it's still somewhat ambiguous. 11:07:14 I was being idiomatic. 11:07:49 amBUGous 11:07:57 * Serg[GPRS] likes wordplay 11:08:20 --- quit: topher (Remote closed the connection) 11:08:36 --- join: topher (~chris@lsanca1-ar42-4-61-178-027.lsanca1.dsl-verizon.net) joined #forth 11:08:58 (ru, old) 'amba' - totall failure, lossage, crash, death 11:29:48 --- quit: warpzero (Read error: 60 (Operation timed out)) 11:50:56 --- part: slava left #forth 11:57:08 bitwise fileoperation are suck suck 11:57:17 :( 12:00:43 cant handle the confusion. i quit 12:01:36 --- quit: Serg[GPRS] (Read error: 60 (Operation timed out)) 12:05:58 --- nick: arke_ -> arke 12:08:49 --- join: ianp (ian@inpuj.net) joined #forth 12:09:31 * ianp cheers for kc5tja 12:17:28 Hehe :) 12:17:38 * kc5tja is hungry. I will probably get something to eat. 12:18:29 :) 12:18:30 :) 12:27:23 * arke is playing Freeciv 12:35:57 OK, this sucks. 12:36:16 I can't leave the house until the plumbers get back to fix a leak in one of our toilets. GAHH! I'm so hungry!! 12:48:24 :/ 12:48:32 maybe have some tea or something 12:48:50 I've been munching on chocolates all day. 12:49:03 It satisfied my stomach for the most part, but now it's violently protesting. 12:49:11 And I don't want to order pizza -- I just don't have the cash for it. 12:49:37 Sneak into people's gardens and see if you find any fruit. 12:49:50 ordering pizza is so expensive. 12:49:54 i mean, it's dough and tomatoes... 12:50:23 Yeah, but you have to pay for gas too. :) 12:50:27 But I understand completely. 12:52:32 yea 12:52:38 and the ovens etc :P 12:54:13 w00tzors! 12:54:23 Got the testKey.fs code to run again under the new emulator. 12:59:05 :) 12:59:24 * Robert got some tea and a sandwitch 13:00:48 Robert: wrote some more docs? 13:00:50 --- join: Sonarman (~matt@adsl-64-169-94-145.dsl.snfc21.pacbell.net) joined #forth 13:01:16 arke: No. I'm still thinking about what to do next. 13:01:55 arke: Either I'll continue on F 2, code something for Kestrel, or throw a small system together myself. 13:04:08 --- quit: Sonarman (Client Quit) 13:20:37 --- join: Topaz (~top@exten-halls-131.soton.ac.uk) joined #forth 13:20:45 --- join: Sonarman (~matt@adsl-64-160-165-86.dsl.snfc21.pacbell.net) joined #forth 13:21:54 Robert: :) 13:28:31 --- quit: Topaz (Read error: 54 (Connection reset by peer)) 13:33:05 --- nick: topher -> topher|away 13:33:19 --- join: lalalim_ (~lalalim@pD95EA84A.dip.t-dialin.net) joined #forth 13:34:06 --- quit: lalalim (Read error: 60 (Operation timed out)) 13:41:31 --- quit: skylan (Read error: 104 (Connection reset by peer)) 13:44:27 freeciv anyone? 13:46:15 --- join: skylan (~sjh@vickesh01-4831.tbaytel.net) joined #forth 13:47:54 --- nick: lalalim_ -> lalalim 13:52:41 --- join: Topaz (~top@exten-halls-131.soton.ac.uk) joined #forth 13:59:23 --- quit: Topaz (Read error: 54 (Connection reset by peer)) 14:11:49 arke: Still dead/gayming? 14:11:59 gaming 14:12:06 OK. 14:38:59 --- join: poingie (~chatzilla@user-2inja8r.dialup.mindspring.com) joined #forth 14:39:41 --- join: TheBlueWizard (TheBlueWiz@207.111.96.10) joined #forth 14:39:42 --- mode: ChanServ set +o TheBlueWizard 14:39:54 hiya all 14:40:19 Hi Wizard, and poingie 14:41:01 wow chatzilla flickerzilla = 14:41:33 Use irssi. :) 14:43:49 eh. i'm on win 14:44:24 'sides, i like typeahead find in chat windows 14:46:06 OK, there's xchat for win. :) 14:46:12 yech 14:46:26 there's irssi for win :) 14:46:33 hm 14:46:54 what have you got to say for yourself NOW? :) 14:47:09 Sonarman: Really? Didn't know that 14:47:16 got a q ... is there a forth for win with ffi support? 14:47:24 ffi ? 14:47:43 thinking of doing some SDL stuff. particles and stuff 14:47:58 looking to write a schmup, for kicks 14:48:03 Win32Forth can access functions in DLLs 14:48:12 probably so can SP-Forth 14:48:17 sp-forth? 14:48:31 SDL? 14:48:48 ok, well it turns out the Windows version of irssi requires Cygwin 14:48:51 TheBlueWizard: simple directmedia layer 14:49:05 sort of cross platform directx, much simpler than directx 14:49:44 sp-forth is a Russian forth system, meaning not much English documentation. better goi with Win32Forth :) 14:49:47 /goi/go 14:49:53 heh, good idea 14:50:15 hopefully the sdl parts wont be too painful to port then 14:50:19 re tbw 14:51:17 hopefully i can use forth to just bang straight on the surface 14:51:37 and then just flip pages or resync it on vblank... no idea how with sdl tho 14:51:53 * kc5tja will be working with SDL with gforth under Linux today. 14:52:26 yah i was looking at gforth 14:52:30 ffi doesnt work on win :( 14:52:34 SDL_Flip(SDL_Surface *screen); 14:52:51 kc5tja: SDL allows easy doublebuffering 14:52:52 heh, sounds easy then 14:54:02 arke: I'm not doing any dbl buffering 14:54:26 ok 14:55:41 arke: I'm doing this for my Kestrel emulator. 15:01:06 --- join: Topaz (~top@exten-halls-131.soton.ac.uk) joined #forth 15:01:16 Hi 15:06:59 --- quit: Topaz (Read error: 54 (Connection reset by peer)) 15:08:45 hi Robert 15:08:58 Boo. 15:09:38 Moo. 15:09:39 .ooM 15:10:20 Ehm, yes. 15:11:00 What would be best, a limited, Forth-primitives-only assembler or a "real" one? I'm starting to think that in the end, the latter option may pay off... 15:12:14 well, just provide common things 15:12:29 MOV, ADD, OR, AND, XOR, IF<, etc. 15:12:34 Yeah, but HOW common? 15:12:52 There's a HUGE amount of addressing combinations, different MOV instructions, etc.. 15:15:14 you could always just steal an assembler :) 15:15:20 Hrm. 15:15:21 like the one from bigForth 15:15:31 I guess I could... "get some inspiration", yes. 15:15:42 it's complete (AFAIK), and portable 15:15:50 kind of portable 15:15:58 Sounds nice. 15:16:04 Thanks for the tip 15:16:39 you'd get floating point instructions for free :-) 15:16:55 dammit. i can't get this CD out of the driv 15:16:56 :D 15:17:06 --- quit: Sonarman ("reboot") 15:22:56 --- join: Sonarman (~matt@adsl-64-160-165-105.dsl.snfc21.pacbell.net) joined #forth 15:23:57 yay, thank you Debian 15:24:03 you got my CD out of the drive 15:27:47 :) 15:28:10 Robert: Just provide what you need, when you need it. 15:28:49 hey, Debian has gforth 0.6.2 15:28:50 --- join: Topaz (~top@exten-halls-131.soton.ac.uk) joined #forth 15:29:13 it wouldn't build under Gentoo 15:29:36 Sonarman: I got mine to compile from the available sources from the GForth site. 15:30:51 well, i'm on PPC and supposedly it won't build under PPC because of some "long long" bug in gcc 15:31:34 but apparently those clever Debian creatures were able to do it 15:31:35 kc5tja: I just thought that a more general assembler could become handy later, and introduce some more optimization possibilities. 15:31:48 kc5tja: But you're right, that was my initial thought. 15:32:43 kc5tja: is the only difference between VIBE 2.1 and 2.2 that 2.2 uses EMPTY and is loaded on demand? 15:39:07 Sonarman: The "d" command is handled differently too. 15:39:08 --- quit: poingie (Read error: 104 (Connection reset by peer)) 15:39:17 Otherwise, they're the same. 15:39:52 Robert: That's basically what I'm doing with my FTS/Forth and the Kestrel's MachineForth assembler. 15:40:13 Oh man, I'm so happy -- I modeled the abstract state machine for the assembler, and so far as I can tell, I haven't run into any bugs yet either. 15:40:43 In fact, it compiled the testKey code *perfectly*, and it runs exactly as expected (the old code kept crashing the emulator, thus prompting the re-write of the assembler) 15:52:14 kc5tja: awesome 15:53:40 kc5tja: Heh, I'd kill for a chance to write a MachineForth assembler. I'm stuck with i386, and that kind of discourages you... 15:55:17 I could do it the colorful way and just replace every MachineForth primitive with the corresponding x86 instructions. 15:55:42 Would cost me some performance, but I guess I could live with that. 15:55:57 that's what chuck moore did, right? 15:56:21 Like I said, yes. 15:56:36 Heh. My 13 year old sister picked up the OS Design and Implementation book. 15:57:08 oh. colorful. yes 15:58:16 :) 15:58:24 That's what my history teacher told me 15:59:00 "Dear Robert, you're CONSTANTLY INSINUATING EVERYTHING. Your tests are IMPOSSIBLE TO CORRECT. I'll just give you an average grade. Bye." 15:59:16 Er, insinuating maybe isn't the best word here. 16:03:59 OHHH 16:04:11 now i see what i was doing wrong 16:04:16 What? 16:04:27 Robert: That's how it's supposed to be done. (Replace each "MachineForth instruction" with one, two, maybe three x86 instructions) 16:04:38 i thought that create-file leaves an exception # on the stack while write-file doesn't, when it's really vice-versa 16:05:08 Sonarman: They BOTH should. 16:05:34 grr. i just typed forth code into my bash shell 16:05:39 <- going crazy 16:06:03 Sonarman: Well, just think, if you were using scsh, you'd be typing Lisp expressions. (Well, Scheme, but still) 16:06:15 kc5tja: Using a more x86-specific approach I guess you could make it quite a bit faster. But with my poor optimization skills, I'd probably ruin it anyway. :) 16:06:24 kc5tja: :) 16:06:39 kc5tja: oh, you're RIGHT. they BOTH do 16:07:03 thank you kindly 16:07:29 Robert: Hehe. Well, I tried the x86-specific way, and while it does work, I quickly found myself with a TON of basic primitives, just because the x86 has so much capability compared to a basic MISC processor. 16:07:51 So the thing to be aware of when writng an x86 machine forth assembler/compiler is to just watch out for the feature creep. 16:08:02 kc5tja: Hehe, thanks for the advice. :) 16:08:24 My FTS/Forth Cross Compiler (on my web stie) is a good example of some serious feature creep. It WORKS, but it's too complex even for me. 16:08:37 My MachineForth assembler for the FTS1001 can replace it in a heartbeat. 16:08:58 Robert: :) 16:09:05 Sonarman: no problem. :) 16:09:47 OK, back to programming... 16:10:04 Good luck 16:10:29 Thanks. :) 16:16:51 --- quit: Topaz (Read error: 113 (No route to host)) 16:46:09 YAY! Got SDL to initialize and quit without segfaulting! 16:46:28 * kc5tja now realizes that GForth isn't nearly as limited as I thought it was. This fflib package is the sweetness. 16:47:15 Oh, nice. 16:47:25 SDL in Forth, that sounds neat. 16:53:26 ack 16:53:31 i just found my bug 16:53:39 it includes the path in the list 16:53:39 lol 16:53:43 er 16:53:45 i meant 16:53:47 it autosorts 16:53:47 lol 16:53:54 can't have it do that 16:54:27 Hrm, what are you writing? 16:54:34 explorer.exe replacement 16:56:30 well, not really 16:56:34 just a filemanager for windows 16:57:07 arke: Well, if you open source it and let it grow, it'll almost certainly evolve into an explorer.exe replacement. 16:57:30 the problem is 16:57:32 its written in jamagic 16:57:37 and nobody has jamagioc 16:57:38 lol 16:57:48 What the heck is jamagic? 16:58:15 this lame scripting language+IDE for super-RAD 16:58:30 Ahh 16:58:35 can it show Printers like explorer.exe does? 16:58:44 i could have it do that lol 16:59:06 lol 16:59:16 its really RAD though --- I've got like 50 lines of code (could be 25-30) and it displays the window already 16:59:27 * kc5tja is happy that GForth can grok other C libraries, and quite easily too. 16:59:39 * arke is away: work 16:59:41 You KNOW that this means that GForth and GCOM will get to know each other quite well. :) 17:01:25 cool...I've been trying to figure that out for age cuz I'd like to be able to get a list of printers for one of my Python scripts at work (so I can pick a printer and print some stuff out) 17:20:40 --- quit: qFox (Read error: 60 (Operation timed out)) 17:25:08 --- join: solar_angel (~jenni@Toronto-HSE-ppp3685160.sympatico.ca) joined #forth 17:26:31 how does count work? 17:28:09 : count ( a -- a n ) dup c@ swap 1+ swap ; 17:28:10 n/m 17:28:12 I think that's it. 17:28:14 yeah it is 17:28:59 does s, take a s" and do that placement? 17:29:20 :( Darcs is broken now. :( 17:29:31 kc5tja: Darcs ? 17:29:41 I upgraded from 0.9.20 to 0.9.21, and now it won't commit any of my changes to the repository. 17:32:50 Hmm.. Just found some old web logs from #forth. 17:33:08 Matched against my first Forth-like compiler - it was done 5 days after I first joined. :D 17:33:42 hehehe 17:33:54 i like this channel. 17:34:10 Yes, so did I. 17:34:21 The people were...different. 17:34:38 Robert: You don't like us anymore? :) 17:34:44 no holier-than-thou high-level-m*sturbationists extolling the virtues of n'th degree seperation from hardware in here :P 17:35:17 kc5tja: I've become a Forther myself, you don't appear like gods anymore. :( 17:35:38 lol Robert 17:36:11 well, we could always start a channel called #forthcpudesign 17:36:16 Heh. I like Fare's answer to "what kind of language is Forth?" 17:36:26 "language cool forth is". 17:36:42 lol @ language cool forth is. 17:37:00 :) 17:37:49 And the first thing I do in here is asking if Forth is like C++ (both high- and low-level). 17:37:49 seriously, a C coder i was talking to today got all defensive when i suggested that FORTH makes OS development faster. 17:38:03 I want to change history. 17:38:09 *lol* 17:39:13 And then MrReach told me that if I'm happy with C, I should leave. 17:39:17 So I left. 17:39:28 Hahah :) 17:39:38 Now I see what they said after I did that for the first time. 17:39:59 cleverdra: "poor, sad soul" 17:40:09 This must have been before I first came on -- I don't remember any of this happening since I joined. 17:40:10 MrReach: "Forth is not for everybody." 17:40:24 *lol* 17:41:15 Actually, I440r messaged me after that and taught me Forth. 17:41:23 So a few hours later, I return. 17:41:29 :) 17:41:30 LOL 17:42:01 my intro to FORTH is even weirder. 17:42:40 after many years of developing RPN language prototypes and experiments of my own, i heard about FORTH... and then i found "Moving FORTH". 17:42:48 i really hadn't done any FORTH until i started writing one. 17:43:49 I made Speuler show me how to write one. 5 basic primitives, and I was hooked. 17:44:20 Wasn't used to being able to implement a decent compiler in an evening. 17:44:46 hehe 17:46:29 I only wish electronics were so easy. *sigh* 17:47:43 Software has totally ruined me, I think. 17:47:56 The ability to *create* things without spending any cash to do it has totally made me lazy, I think. 17:48:07 Hehe. :) 17:48:12 The Kestrel is the first significant hardware project that I'll be undertaking since at least my homebrew CPU. 17:48:13 but electronics *are* easy. 17:48:23 (And come to think of it, this *HAS* a homebrew CPU in it -- funny how history repeats itself) 17:48:43 solar_angel: no no, I mean to get something working in "five easy steps," completely from scratch, in one evening. 17:49:05 kc5tja - 7400-series? 17:49:27 i'm telling you, when i was 11, and i built my first binary adder, it felt like xmas. 17:49:37 solar_angel: That's what I built my first CPU out of. 4-bit. Didn't do anything terribly useful. Definitely was NOT Turing complete. :D 17:49:37 of course, then xmas a couple years later, when i built a 3-digit binary counter... 17:49:42 Oh, if only I'd known about stack machines back then. 17:49:47 hehe 17:50:00 But ti did not take me one evening, and definitely took more than five steps. 17:50:01 i was building my 32-bit 4-bit-instruction machine in TTL at one time 17:50:09 i have enough breadboard and components... 17:50:30 but making the jumper wires is incredibly time-consuming. 17:50:57 Yeah, one bus point-to-point link consumes 30 minutes, not including debugging time. 17:51:48 hehehe. 17:51:54 try building a 32-bit ALU 17:51:54 * Robert wishes he hadn't got into electronics so late. 17:52:19 *shrug* 17:52:27 i literally had to make a *special* order to the company, wait till they had new stock, and bought them totally out of breadboard :P 17:52:43 Haha, how much did you get? 17:52:51 64 of the single-panel ones. 17:52:59 Heh. 17:53:19 Wasn't that kind of...expensive? 17:53:59 in those quantities, you'd be surprised the discounts they'll cut you :P 17:54:20 Still sounds like a really insane project. :) 17:54:37 it was... not really sure what i was thinking. 17:54:46 oh well, now i have all the breadboard i'll ever need. 17:54:51 Haha, yeah. 17:55:13 Why did you have to make it _32-bit_ ? 17:56:42 because it was 32-bit? 17:56:52 i lucked out, though, when buying parts 17:56:58 and ran across a tube of 74182's. 17:57:50 carry lookahead generators. 17:57:56 What do they do? 17:57:59 since i was doing fast carry lookahead addition. 17:58:07 they reduce the latency of really big adders. 17:58:15 Carry lookahead? 17:58:28 you'd have to know a hell of a lot about digital design to get it :P 17:58:38 Oh well.. I'll save that for another day. 17:58:39 Robert: Generates the carry signals based on the same inputs the rest of the adder uses to perform the arithmetic with. 17:58:47 basically, it's about calculating available bit carries ahead of the actual carry arriving 17:58:57 thanks kc5tja, better than i could have said. 17:59:08 So instead of rippling the carry bit-by-bit, it does it, say, byte-by-byte instead, which makes addition go faster. 17:59:12 anyway, it's designed to reduce it from O(n) to O(log n), and it does a good job. 17:59:23 it does better than byte by byte, you can stack them in trees. 17:59:52 Yeah, but with only 32-bits, you can probably get by with byte-by-byte in a linear array. 18:00:33 But, whatever. If I were to do the same thing today, I'd probably choose to use a carry-save adder instead. 18:00:54 Lots more wires, but quite a bit faster too. 18:01:11 carry save? 18:01:14 Heh. 18:01:29 Speed...long wires...sounds like a great combination. 18:01:36 A CSA works by producing both the AND and the XOR results given two inputs. 18:01:48 Robert: Nobody said anything about long wires. I just said a lot MORE wires. 18:02:05 kc5tja: I mean a 32-bit CPU on breadboards in general. 18:02:11 kc5tja - that sounds like carry lookahead so far. 18:02:29 A CSA is intended to be used in a pipelined system, where any arbitrary width of addition is computable in only 3 clock cycles. 18:02:34 Well, 3 pipeline stages. 18:02:41 ahh. 18:02:55 As the the AND/XOR results from stage N-1 feed stage N, and its results feed N+1, etc. 18:03:21 You can add 2048 bit operands that way trivially. 18:03:53 hrm... 18:04:53 ohhhh 18:05:01 carry save is basically a pipelined version of carry lookahead. 18:05:12 that actually makes perfect sense. 18:07:16 If you take the schematic of a single bit full-adder, and insert a flip flop in between the two half-adders that stores both the AND and XOR result, that's basically a 1-bit CSA. 18:07:24 Then extend that to however many bits you want. 18:07:34 hrm... i'm reading up on it now. 18:07:55 Instead of wrapping the output carry of one bit to the input of another, a third stage is introduced to take care of it, and that's why it needs three stages. 18:08:46 Anyway, I'm getting distracted. I need to work on my kestrel emulator. 18:08:46 :) 18:08:55 heh. 18:14:33 --- quit: solar_angel ("*sleeeeep*") 18:15:08 Heh. It's good when people halz a dozen time zoned behind you start going to bed. 18:16:05 --- quit: I440r (Read error: 54 (Connection reset by peer)) 18:16:17 --- join: I440r (~FooBlah@168-215-246-243.gen.twtelecom.net) joined #forth 18:16:35 Hey I440r 18:17:08 The first thing I saw you say when I looked through those ancient logs was "I still need a job". :) 18:21:14 He 18:21:15 Heh 18:22:05 well, gotta go...bye all 18:22:10 Bye TheBlueWizard :) 18:22:11 Ciao. 18:22:26 bye Robert and kc5tja 18:22:32 --- part: TheBlueWizard left #forth 18:51:15 --- quit: Sonarman ("leaving") 18:57:28 --- join: Sonarman (~matt@adsl-64-160-165-168.dsl.snfc21.pacbell.net) joined #forth 19:03:20 --- join: solar_angel (~jenni@Toronto-HSE-ppp3685160.sympatico.ca) joined #forth 19:05:14 Couldn't sleep? 19:09:32 --- join: warpzero (~warpzero@dsl.142.mt.onewest.net) joined #forth 19:10:08 had to stay up, more or less. 19:10:32 Forth using it's magic powers, I see. 19:10:40 * Robert just worked Georgia. :) 19:10:46 The _real_ Georgia. 19:11:53 heh. 19:11:57 what where? 19:12:12 On the radio. 19:12:18 oh. 19:12:19 7001 kHz 19:12:20 alrightie. 19:12:23 Hehe. 19:12:54 That was kind of aimed at kc5tja... But if you can stand listening, I won't stop you. 19:16:50 Robert: Georgia, Russia, I assume? 19:17:10 Georgia, Soviet Union would be more correct. 19:19:10 wouldn't that be Georgia, Independant State? 19:19:45 I thought the soviet union was dissolved 19:19:47 I don't know Eastern Europe's geography. 19:20:06 Actually, it's not in Europe. 19:20:32 And I only said Georgia, Soviet Union is more correct than Georgia, Russia. It's still totally wrong. :) 19:20:54 OK, OK, the *country* of Georgia. 19:21:00 But don't worry, I'm no master of Geography either. I just happen to know the neighbourhood. 19:21:22 ahh, I love being pedantic 19:21:26 =P 19:21:30 And I'm childish enough to really enjoy poking fun of you. 19:21:39 fridge: :) 19:22:09 hey guys 19:22:21 anyone who can make it up here before midnight can come to a lan party 19:22:36 can't make it sorry 19:22:50 wrong side of the planet 19:23:02 oh yeah 19:23:18 Midnight was over 4 hours ago. 19:23:47 never been to a lan party 19:23:54 3 cheers for the lan! 19:24:19 whoa. a heavy metal version of "Day Tripper" 19:24:20 Hey warpzero.. Do you happen to know a certain lscd/a32 ? 19:24:26 Sonarman: Heh... 19:24:47 on #argv? 19:24:49 it sounds good :) 19:24:59 Robert: yeah i think so 19:25:28 Hehe. I just checked your whois, and I remembered her talking about that channel. 19:25:38 yeah 19:25:42 what about her 19:25:50 Er, nothing. 19:26:09 I was just curious, "friends of friends" on IRC is an interesting topic. 19:27:10 They should log all private messages and create some statistics based on that. 19:27:21 well 19:27:24 i don't really know her 19:27:30 i just kindof invaded that channel one day 19:27:32 (Yes, yay for privacy) 19:27:36 :D 19:28:03 I got that, since you asked, I gave my motives for asking. 19:44:34 --- quit: solar_angel ("*eeepslay*") 20:24:31 --- quit: Sonarman ("leaving") 20:26:02 --- join: crc (crc@0-1pool176-25.nas6.philadelphia1.pa.us.da.qwest.net) joined #forth 20:30:40 OK, attempting to get the SDL library to interpret a 640x480x8 frame buffer is apparently not possible at all. 20:30:49 Despite the fact that the call to create the screen apparently worked fine. 20:32:54 i hate shit like that 20:35:07 I gotta be doing something wrong. 20:35:18 But no amount of documentation will tell me. :/ 20:35:39 I set the palette, too, so that's not an issue. 20:44:17 YAY! 20:44:23 It produces video!!! 20:44:27 Sort of. 20:44:31 Still some bugs in it, but it DOES work. 20:47:46 It is remarkably slow though. 20:48:01 We're looking at a video frame rate of about 0.5 per second. :/ 20:49:13 what are you working on? 20:49:53 My emulator. 20:50:13 oh, i didn't think you'd use video for that 20:50:25 I don't understand your logic. 20:50:35 it's just a processor current isn't it? 20:50:36 I'm not aware of a computer emulator that didn't emulate the video system. :) 20:50:58 The processor emulator works. I'm attempting to now proceed to the whole Kestrel computer itself. 20:51:10 ah ok. didn't think you were that far yet 20:51:47 Nice thing about stack machines is that they're so simple, it's trivial to write an emulator for them. 20:52:08 I just need to figure out how best to get this to work though. 20:52:23 the video system? 20:52:25 Some details, for performance reasons, must be different from real-world hardware though 20:53:49 Still some bugs that I can't seem to locate though!!! 20:54:00 hehe 20:54:00 Why is it suddenly NOT calling my cpu tick function? 20:54:05 what are you writting this in? 20:54:08 Forth 20:54:17 gforth? 20:54:21 yep 20:54:39 i've heard nothing good about that one yet :) 20:54:51 Because nobody knows what they're talking about. 20:54:58 They are prejudiced because it's an ANSI Forth. 20:55:13 I seem to be having mostly good luck with it. 20:55:18 ever used bigforth? 20:55:19 With fairly adequate performance levels. 20:55:28 bigForth constantly crashes on me. 20:55:37 But it's probably improved since I last used it, I don't know. 20:55:50 yah i had problems with it too last time i used it 20:55:54 none of my friends seem to though 20:56:13 It is native code though -- I might try it again to compare performance against gforth ONCE I get this code working. 20:56:27 yah that'd be interesting 20:56:59 bigforth claims to be quite fast 20:57:24 --- quit: warpzero (Read error: 60 (Operation timed out)) 21:00:20 --- join: LOOP-HOG (~jdamisch@sub22-119.member.dsl-only.net) joined #forth 21:00:24 how do 21:01:05 re LOOP-HOG 21:01:36 ok, another question for you pups, how many of you really give a dustmites phartz electric signature in a methane snowstorm about Forth? 21:01:39 heh? 21:02:02 I'm working on http://www.memnonio.com/forth.html 21:02:25 i'm basically at the point to where i'm taking sugestions about links and structure and such 21:03:49 its getting a facelift eventually, i was hoping to get something to show done tonight but i'm taking a break 21:04:09 if you want to sugest something just use the green mail button to respond to me 21:05:43 Huh? 21:06:03 :) 21:06:04 Oh, I have a link for you. 21:06:12 kewl dewd 21:06:17 http://www.shockfamily.net/cedric/fflib.html 21:06:25 is it crusty? 21:06:32 How to access external C libs using gforth -- the world's FIRST real documentation for it! 21:06:44 It's rather well written. Terse, but well written. 21:06:55 its just shockfamily sounds so shocking 21:07:10 The guy's last name really is Shock. 21:07:31 it'll be linked by midnight if I just visit for 50 min and then work like a fiend on my site 21:07:39 LOOP-HOG: This guy's page is how I got gforth to talk to SDL for my Kestrel emulator. 21:08:07 Although, it's not behaving quite right, at the moment. I'm getting mixed signals on the display pitch, and I'm wondering why it's not displaying all 480 lines yet. 21:08:37 itll be in the LITERATURE section unless you specify otherwise 21:08:42 kool 21:08:56 Literature is fine, I guess. 21:09:00 It's more of a how-to. 21:09:06 project? 21:09:17 let me look at my list and see if i need a new catagory! 21:09:27 No, it's not a project per se. 21:09:34 It's just plain vanilla documentation. 21:09:42 Docs that *should* have been included with gforth from the beginning. 21:10:51 i see 21:11:12 maybe just in HOW TO section 21:12:01 --- join: warpzero (~warpzero@dsl.142.mt.onewest.net) joined #forth 21:12:26 its going into the codeshare section, and then when I get a bunch of code links in there i will organize it better 21:12:41 * kc5tja nods 21:13:23 hi 21:13:32 warp, got any FORTH links for me? 21:16:37 kc5tja, got tested for green belt today. 21:17:50 madgarden: Cool. 21:17:59 Until a few weeks comes up, I won't have ANY time for aikido. 21:18:18 I just go once a week. 21:18:28 That's all I'll have time for in the coming weeks. 21:18:30 But, judo learns quick. 21:18:31 Right now, i can't go to ANY. 21:18:36 :-/ 21:30:46 COLOR BARS WORKS! :) 21:33:19 Screenshot! 21:35:36 just a second. 21:36:54 http://www.falvotech.com/screenshot.png 21:37:53 Hee, awesome. 21:37:57 Bit squiggly there on the bottom half... 21:38:11 That's because I'm using binary arithmetic instead of saturated arithmetic. 21:38:33 A... ha... 21:38:51 Remember the CPU is a true 32-bit processor -- no concept of 8-bit bytes. 21:38:56 However, graphics data is byte-packed. 21:39:09 so I load the stack with $00000000, and add $01010101 for every line. 21:39:14 Ahh, right. 21:39:17 Obviously, after 256 lines, it carries over. :D 21:39:24 --- join: Sonarman (~matt@adsl-64-171-254-160.dsl.snfc21.pacbell.net) joined #forth 21:41:24 I would like to point out, however, that gforth is clearly not the world's best implementation of Forth in which to make a machine emulator in. :D 21:41:33 But it nonetheless seems to work with somewhat decent performance. 21:41:38 About one frame per second video performance. 21:41:39 :D 21:41:40 better than Joy :D 21:41:46 (VERY brute force too) 21:41:56 Sonarman: Did you see the screen shot? 21:42:01 nope 21:42:02 http://www.falvotech.com/screenshot.png 21:42:15 grats 21:42:36 Thanks. :-) 21:42:48 I just wish darcs worked, so I could check it into the repo and upload it to the site. >:/ 21:42:50 AWESOME 21:42:57 The maintainers of darcs broke it in the latest build. 21:43:09 i echo LOOP-HOG's sentiment 21:44:53 :) 21:45:21 oh, i LOVE being able to listen to audio CDs on the computer now!! 21:45:24 Well, I'm certainly very pleased myself. 21:45:35 --- quit: Sonarman ("leaving") 21:45:55 --- join: Sonarman (~matt@adsl-64-171-254-160.dsl.snfc21.pacbell.net) joined #forth 21:47:57 Lord knows, it took me ALL DAY to get this far. 21:48:13 There are still some small bugs lurking about, but I am progressively getting closer to squashing them. 21:48:22 I was thinking of puting my site into a .arc file so that someone could easily rip it off and put it up on their serverspace, thus spreding Forth spores 21:49:04 if i can get my hands on a groovey little Forth computer and have some time to experiment then that will be Fun! 21:49:08 I don't think many folks have a decompressor for .arc, I don't think? I know I certainly don't. 21:49:14 .zip 21:49:16 i mean 21:49:18 oop 21:49:22 :) 21:49:27 I haven't seen .arc since 8088 days. :D 21:49:29 stuck in the 80s 21:49:46 all 8's and 0's :) 21:50:05 yup 21:50:29 And then ZIP came along, and squashed it like a bug. 21:50:38 Faster, better compression ratios, and easier to use. Gotta love it. 21:51:16 LOOP-HOG: Anyway, this emulator ought to provide some idea of what it's like to program for the kestrel at the lowest levels. And indeed, it will need it, since the emulated hardware is indeed very primitive. 21:52:30 but we just stick it in FORTH words, right 21:52:37 we're flying a kit 21:52:40 Right now, Forth doesn't exist on it. 21:52:40 we're flying a kite 21:52:44 oh 21:52:53 That will come with time. 21:52:54 so you have some assembly on it 21:53:05 just to test it 21:53:19 The assembler currently runs on GForth, so it's somewhat inconvenient. That will be fixed shortly though. 21:53:25 i mean, later there will be a FORTH to organize the complexity into 21:53:32 I need to implement a "ROM" wordset so I can easily create and save "ROM images." 21:53:47 even label the core assembly routines that we normally don't see, like firmware stuff 21:53:55 LOOP-HOG: eventually, there will exist a FORTH ROM for it. 21:54:13 LOOP-HOG: Here is the "assembly language" to produce the color bars: 21:54:24 how about booting? 21:54:27 include emu.fs 21:54:27 include asm.fs 21:54:27 0 org 21:54:27 ': !, b!, !b, ;' 21:54:27 ': rxstatus RXSTAT #, ;' 21:54:30 ': rxbuffer RXDATA #, ;' 21:54:32 ': txbuffer rxbuffer ;' 21:54:35 ': quit rxstatus a!, !a, ;' 21:54:45 ': w4k drop, rxstatus a!, @a, ' w4k >body @ jz, quit ;' 21:54:45 ': wait4key 0 #, w4k ;' 21:54:45 ': 4p dup, !a+, ;' 21:54:45 ': 16p 4p 4p 4p 4p ;' 21:54:45 ': 160p 16p 16p 16p 16p 16p 16p 16p 16p 16p 16p ;' 21:54:47 ': l 160p 160p 160p 160p $01010101 #, +, ;' 21:54:56 ': 10l l l l l l l l l l l ;' 21:54:57 ': 80l 10l 10l 10l 10l 10l 10l 10l 10l ;' 21:54:57 ': 100l 10l 10l 10l 10l 10l 10l 10l 10l 10l 10l ;' 21:54:57 ': 480l FrameBuffer #, a!, 80l 100l 100l 100l 100l ;' 21:54:57 ': colors $00000000 #, 480l wait4key ;' 21:55:36 It would be somewhat easier to read if I had a real IF/THEN constructs, which I suppose should be the next thing to code. 21:55:57 But as you can see, MachineForth and regular Forth is virtually indistinguishable. 21:58:49 But it doesn't look very readable to me 21:59:02 there is readable and unreadable FORTH 21:59:11 What is unreadable? 21:59:28 If i was engrosed in the subject material then I would understand it 22:00:16 I'm just used to seeing a little more formating, but thats ok i guess 22:00:31 Read it left to right, like English sentences. 22:00:36 rolling loops out into words 22:00:41 I admit that my GForth code makes somewhat better use of formatting too. 22:01:25 LOOP-HOG: Unrolling loops results in faster execution, which is markedly apparent in the emulator. :D 22:01:35 especially with only 0.5 to 1 frame per second video. :D 22:01:42 its neat 22:02:05 I should also note: it'll be a HECK of a lot more readable once a native machine Forth compiler is on the Kestrel itself. 22:02:05 i dont understand what all of the words do 22:02:13 I can do away with all those commas, the excess # words, etc. 22:02:24 Well, read it from "colors" on up. 22:02:31 480l == 480 lines of video 22:02:39 Lots of loop unrolling, yes. 22:02:46 i'll just take it as a datastructure and format it my own way 22:02:54 but the keyboard will be funney 22:02:58 probably 22:03:06 That's precisely how it's intended to be read. The concept of "executable data structures" works for Forth as it does for Lisp. 22:03:22 I'm going to use a bone-stock IBM PS/2 keyboard for the Kestrel. 22:03:41 I have no intentions of working with custom keyboard layouts. 22:03:43 I WANT A STOCK PS/2 KEYBOARD MAN!!!!! :) 22:03:52 I have a squishy new one 22:04:12 No, I meant that the keyboard interface is a PS/2 port. 22:04:20 I haven't seen a PS/2 keyboard in some years. 22:04:38 Besides, the Micron keyboards are vastly better, in my opinion. 22:04:42 Not nearly as much key travel. 22:05:04 I just want the old style with the clicky sound and the easy keys 22:05:26 regular keyboard port 22:05:31 If I could have that, BUT, with half the travel of each key, I'll be ecstatic. 22:05:48 The keyboard I'm using now has little travel, but it's mushroomy. It actually reminds me of the Amiga 1000 keyboard somewhat. 22:06:05 (My Amiga 500 keyboard is somewhat worse, actually -- it feels like a VIC-20 keyboard. :/) 22:07:19 well, atleast it works 22:07:29 ok, i'm going to work on my site for awhile now 22:07:37 okay 22:14:10 ETH Oberon has files ending in .Arc :-) 22:19:21 --- join: solar_angel (~jenni@Toronto-HSE-ppp3685160.sympatico.ca) joined #forth 22:25:19 what ever happened to the Maryland Forth Interest Group 22:25:35 'nother dead link 22:26:41 I've decided that both Forth and FORTH are proper practice 22:26:52 especially in ForthLand 22:26:54 Hehe :) 22:27:01 I occasionally say FORTH. 22:27:22 I used to a lot actually. Now I tend to say Forth. But, the jury is still out, after all these years, as to what is proper. 22:27:38 but the Silicon Valley FIG site is still up, id like to pay them a visit one day 22:27:53 some day i'd like to go on vacation and visit california by train 22:27:55 I'd like to, but they are quite jaded. 22:28:01 As far as I've seen at least. 22:29:56 one time :) 22:30:11 should i still say that the U.S. FIG is defunct? 22:30:38 It certainly seems that way, doesn't it? 22:30:52 no, the site has been updated last in Jan 2004 22:30:58 i'll take it off 22:35:07 --- quit: arke (Read error: 104 (Connection reset by peer)) 22:35:13 --- join: arke_ (~Chris@wbar8.lax1-4-11-100-108.dsl-verizon.net) joined #forth 22:36:40 --- quit: solar_angel ("*gone again*") 23:01:51 Barefoot Auditor link dead 23:02:26 I just determined that, since I get about one frame per second throughput on my box, the CPU "executes" at 415kHz or so. 23:03:13 Oops, 419kHz. :) 23:03:13 your cpu in real life would? 23:03:26 In real life, my CPU would run at 25.175MHz -- 60 times faster. 23:03:33 (obviously :) ) 23:03:42 i see 23:04:15 so how far from emulator to whatever you do to get that programable chip to be a FORTH chip? 23:04:29 There is still quite a bit of distance. 23:04:35 I need to write the Verilog. 23:04:44 I need to simulate it. (NOTE: Not the same thing as emulation) 23:05:11 Then I need to build a circuit around the chip. This is very tough -- the circuit itself must be debugged, as well as the actual chip's programming. 23:05:41 have you done this b4? 23:05:44 Once the circuit is built and verified to run the programs that are known to run on the emulator, then and only then can I release it as being ``finished''. 23:05:48 --- quit: warpzero (Excess Flood) 23:05:50 Nope. 23:05:54 Total learning experience for me. 23:06:12 i have a Forth link for a guy that has classes to do what you are trying to do 23:06:15 just a sec 23:06:35 I know who you're talking about, I think. 23:06:46 He has some videos on the Ultratechnology website. 23:07:04 http://www.sandpipers.com/ 23:07:40 doesn't he live in CA? 23:07:45 big him 23:08:24 bug him 23:08:44 back 2 work 23:10:33 --- join: warpzero (~warpzero@dsl.142.mt.onewest.net) joined #forth 23:12:41 Why should I bug him? 23:12:50 That defeats the purpose of my endeavoring for this project. 23:13:05 * kc5tja sighs -- I fucking hate big parties. 23:17:31 ok 23:17:48 just if you get stuck you can ask the guy that went out into Forth land teaching how to do it 23:17:54 i guess 23:18:12 I predict most of the problems will be electrical, not Forth CPU derived. 23:18:32 I'm pretty sure the CPU will operate as advertised, since most of the software-related bugs will be worked out via the emulator (which is its primary mission) 23:19:18 Although I can already start to feel the "classic computer" feel of the Kestrel, even in what little I've completed. 23:19:58 I am, however, thinking of changing the video refresh code a bit, so that it executes 307,200 CPU instructions, and then refreshes the full screen all at once. 23:20:08 Right now, it executes 640 instructions, then refreshes a single line of video data. 23:21:06 I'm back!!! 23:21:09 --- nick: arke_ -> arke 23:21:15 kc5tja: good that you're here, i gotta tell you something 23:21:19 arke: http://www.forthbox.com/screenshot.png 23:21:35 kc5tja: remember how you said 1.5krpm was a torque field day for piston engines? for 23:21:40 kc5tja: I beg to differ. 23:21:50 kc5tja: the only thing my engine does at that RPM is shake. 23:22:07 kc5tja: host couldn't be found 23:22:14 arke: Because you don't have a transmission to match it 23:22:19 arke: Sorry 23:22:22 * kc5tja is getting tired. 23:22:26 kc5tja: lol 23:22:27 http://www.falvotech.com/screenshot.png 23:23:02 :) 23:23:04 what WM is that? 23:23:10 amiwm, right? 23:23:53 Yes, that's amiwm 23:23:56 kc5tja: btw, i don't think its the tranny. 23:24:10 kc5tja: I think it's just my masochistic engine :) 23:24:22 No, it's the tranny. 23:24:25 The gear ratio is totally wrong. 23:24:26 ... 23:24:31 eh 23:24:39 i don't understand that --- 23:24:56 The gear ratios of the transmission is optimized for use in a car that is *already traveling*. 23:25:12 yeah 23:25:27 lets say I'm going 25mph in 3rd gear, that's about 1.6krpm 23:25:30 This is why a CVT would eliminate the sensation of "shaking" that you mentioned. 23:25:40 its quite low and shakes a bit (not too much) 23:25:57 kc5tja: because it would keep it in an RPM range where it doesn't shake? :) 23:26:26 No, because the engine could continue to spin freely at those speeds. 23:26:37 eh... 23:26:40 Never mind, dude. 23:26:47 I'm too tired to explain it, and I'm easily offended right now. 23:26:48 no, I really want to know, explain please :) 23:27:06 oh, didn't want to offend you in any way, sory if i did. 23:27:11 No, you didn't. 23:27:22 ok 23:27:24 But there is a big party here, much bigger than I ever was lead to believe. 23:27:37 And it's getting louder and louder, and it's getting closer and closer to the time I go to bed. 23:27:45 And I don't want to have to fucking deal with it. 23:27:49 But I can see that I have to. 23:28:12 :( 23:30:20 how big is it? 23:31:01 --- quit: Sonarman ("leaving") 23:31:28 * arke is writing a quick and dirty file manager hack 23:33:35 LOOP-HOG: There are about 25 people here at the moment. 23:33:40 Not including those who normally live here. 23:38:47 not fun. 23:39:00 Nope. Not for me at least. 23:39:47 But, I'm just happy that I got my emulator to actually work. 23:39:51 * kc5tja is very, very, very, very pleased. 23:40:21 And with a gut-wrenching performance of 420kHz, man, Intel will have no choice but to bow down to my 1337 CPU design superiority. 23:40:24 YAY 23:40:42 fridge: http://www.falvotech.com/screenshot.png 23:41:06 commit it to the repos, goon! 23:41:29 fridge: I can't. The maintainers of darcs broke 0.9.21 -- it won't commit on my system anymore. 23:41:37 =~( 23:41:44 :( 23:41:47 I already mailed three bug reports to the authors. 23:42:11 Including rather lengthy strace outputs 23:42:11 I need to setup the framebuffer 23:42:16 oh shit.... 23:42:19 jamagic just crashed 23:42:21 so I can view stuff on the console 23:42:21 lol 23:42:45 it better have saved my shit 23:43:27 I'm using 0.9.19 23:43:44 Just a second. 23:43:47 This is getting rediculous. 23:44:01 ack 23:44:04 fucking piece 23:44:06 grrr 23:44:10 I TOLD it to save 23:44:13 ack 23:45:12 Back. For now. 23:45:20 I had to tell them to quiet down. 23:45:20 --- quit: fridge (Remote closed the connection) 23:45:42 I have my music on full blast, with headphones, and I could still hear them, behind a closed door. 23:45:46 >:( 23:45:55 Fuck the neighbors, *I* will call the police if it gets out of control. 23:50:40 heh 23:52:03 wow 23:52:09 I'm writing this so forthish 23:52:29 function _Spill(List, From) { List.Clear(); __Spill(List, From); } 23:53:47 Things yet to do in my emulator include block storage. I have NO idea how IDE drives identify themselves. So I'm just going to totally fake it. 23:54:30 nondot.org/~sabre 23:54:37 click on the OS articles 23:54:40 it has stuff on IDE there 23:54:57 yeah, but I think it's more a case of being too lazy to emulate the full hardware of an IDE drive. 23:55:07 I mean, I'm already running at a meager 420kHz as it is. 23:55:08 :) 23:57:45 Oh, HOLY COW, I forgot -- I already had IF and THEN in the machineForth compiler! :) 23:57:47 ;) 23:57:51 ^_^ 23:59:07 try them out dude 23:59:24 I am. I'm working on a new test program for the FTS1001/Kestrel now. 23:59:59 --- log: ended forth/04.06.12