00:00:00 --- log: started forth/04.06.24 00:15:20 --- quit: jDoctor ("Lost terminal") 00:25:10 --- quit: Herkamire ("bed") 00:28:16 core linux, compiling kernel 00:28:17 ay 00:28:18 yay 00:28:37 --- join: lalalim (~lalalim@p508ABC17.dip.t-dialin.net) joined #forth 00:28:43 which in itself is somewhat redundant, since as soon as I do, I'm "rebooting" and installing 2.6.7 00:28:44 --- quit: lalalim_ (Read error: 60 (Operation timed out)) 00:28:49 ;) 00:35:48 --- join: htp123 (~tehsux@S0106000d6151238b.gv.shawcable.net) joined #forth 00:56:05 ack, this is pissing me off 00:56:10 VMWare should _NOT_ crash 01:43:37 --- join: zardon (~zardon@S0106000d6151238b.gv.shawcable.net) joined #forth 01:47:24 does anyone know how to make gdb disassemble memory that has changed since load time? 01:50:02 --- quit: I4_work (Read error: 110 (Connection timed out)) 02:40:17 --- join: Topaz (~top@spc1-horn1-6-0-cust217.cosh.broadband.ntl.com) joined #forth 03:17:26 --- quit: htp123 ("*") 03:31:18 --- quit: Klaw (Read error: 104 (Connection reset by peer)) 04:09:56 --- join: qFox (C00K13S@cp12172-a.roose1.nb.home.nl) joined #forth 04:51:03 --- join: I4_work (~mark4@168-215-246-243.gen.twtelecom.net) joined #forth 04:52:46 --- nick: I4_work -> I44wrk 04:52:57 hrm cant decide :P 04:53:03 --- nick: I44wrk -> I4_wrk 05:02:23 --- quit: skylan (orwell.freenode.net irc.freenode.net) 05:02:23 --- quit: zardon (orwell.freenode.net irc.freenode.net) 05:02:23 --- quit: kuvos (orwell.freenode.net irc.freenode.net) 05:02:23 --- quit: cmeme (orwell.freenode.net irc.freenode.net) 05:02:25 --- quit: ianp (orwell.freenode.net irc.freenode.net) 05:02:25 --- quit: ChanServ (orwell.freenode.net irc.freenode.net) 05:02:25 --- quit: lalalim (orwell.freenode.net irc.freenode.net) 05:02:25 --- quit: fridge (orwell.freenode.net irc.freenode.net) 05:02:26 --- quit: SDO (orwell.freenode.net irc.freenode.net) 05:02:26 --- quit: Topaz (orwell.freenode.net irc.freenode.net) 05:02:27 --- quit: Robert (orwell.freenode.net irc.freenode.net) 05:03:59 bubye 05:04:01 :p 05:05:07 --- join: ChanServ (ChanServ@services.) joined #forth 05:05:07 --- join: Topaz (~top@spc1-horn1-6-0-cust217.cosh.broadband.ntl.com) joined #forth 05:05:07 --- join: zardon (~zardon@S0106000d6151238b.gv.shawcable.net) joined #forth 05:05:07 --- join: lalalim (~lalalim@p508ABC17.dip.t-dialin.net) joined #forth 05:05:07 --- join: ianp (ian@inpuj.net) joined #forth 05:05:07 --- join: fridge (~fridge@dsl-203-33-162-85.NSW.netspace.net.au) joined #forth 05:05:07 --- join: SDO (~SDO@68.170.20.201) joined #forth 05:05:07 --- join: skylan (~sjh@vickesh01-4831.tbaytel.net) joined #forth 05:05:07 --- join: cmeme (~cmeme@216.184.11.30.unused.swcp.com) joined #forth 05:05:07 --- join: kuvos (C00K13S@cp12172-a.roose1.nb.home.nl) joined #forth 05:05:07 --- join: Robert (~snofs@c-bf5a71d5.17-1-64736c10.cust.bredbandsbolaget.se) joined #forth 05:05:07 --- mode: irc.freenode.net set +o ChanServ 05:05:26 --- quit: skylan (orwell.freenode.net irc.freenode.net) 05:05:26 --- quit: zardon (orwell.freenode.net irc.freenode.net) 05:05:26 --- quit: kuvos (orwell.freenode.net irc.freenode.net) 05:05:27 --- quit: cmeme (orwell.freenode.net irc.freenode.net) 05:05:27 --- quit: ianp (orwell.freenode.net irc.freenode.net) 05:05:28 --- quit: ChanServ (orwell.freenode.net irc.freenode.net) 05:05:28 --- quit: fridge (orwell.freenode.net irc.freenode.net) 05:05:28 --- quit: lalalim (orwell.freenode.net irc.freenode.net) 05:05:29 --- quit: SDO (orwell.freenode.net irc.freenode.net) 05:05:29 --- quit: Topaz (orwell.freenode.net irc.freenode.net) 05:05:30 --- quit: Robert (orwell.freenode.net irc.freenode.net) 05:05:52 --- join: ChanServ (ChanServ@services.) joined #forth 05:05:52 --- join: Topaz (~top@spc1-horn1-6-0-cust217.cosh.broadband.ntl.com) joined #forth 05:05:52 --- join: zardon (~zardon@S0106000d6151238b.gv.shawcable.net) joined #forth 05:05:52 --- join: lalalim (~lalalim@p508ABC17.dip.t-dialin.net) joined #forth 05:05:52 --- join: ianp (ian@inpuj.net) joined #forth 05:05:52 --- join: fridge (~fridge@dsl-203-33-162-85.NSW.netspace.net.au) joined #forth 05:05:52 --- join: SDO (~SDO@68.170.20.201) joined #forth 05:05:52 --- join: skylan (~sjh@vickesh01-4831.tbaytel.net) joined #forth 05:05:52 --- join: cmeme (~cmeme@216.184.11.30.unused.swcp.com) joined #forth 05:05:52 --- join: kuvos (C00K13S@cp12172-a.roose1.nb.home.nl) joined #forth 05:05:52 --- join: Robert (~snofs@c-bf5a71d5.17-1-64736c10.cust.bredbandsbolaget.se) joined #forth 05:05:52 --- mode: irc.freenode.net set +o ChanServ 07:15:16 --- join: onetom (~tom@novtan.bio.u-szeged.hu) joined #forth 07:15:50 hi 07:17:13 save6 200003 16 flux13 6 80003 move16 disk13 floppy!3 ; 07:17:18 tadaa 07:17:59 i can paste color text from within my editor through screen into irssi 07:18:21 :) 07:18:34 if anyone interested, just ask me about the solution 07:18:51 (what is not perfect yet...) 07:19:25 i need help developing a color text experimenting enviroment 07:19:49 what do you need it for? 07:20:42 exploring the strengths & weaknesses of colored text 07:21:06 hehe 07:21:39 eg we can use it for a more conscise xml representation 07:23:04 and of course we can use it for colorforth like programming languages 07:24:03 yeah 07:31:23 i imagine that many configuration files - even in a linux environment - can b replaced w a colored text what can b "run" instead of just "parsing" 07:32:29 eg 1 can generate virtualhosts for apache by definig : vhost-type1 ... dir ... log ... whatever ; 07:32:56 and then vhost-typeN asd.domain.com 07:33:49 instead of specifying 07:33:50 07:33:50 ServerName aron.dunacafe.hu 07:33:50 DocumentRoot /var/www/aron.dunacafe.hu 07:33:50 ErrorLog /var/log/apache2/dunacafe.hu/error.log 07:33:52 CustomLog /var/log/apache2/dunacafe.hu/access.log combined 07:33:55 07:34:09 such a bunch of lines tenth of times 07:35:26 most configuration files r hard to maintain after a while, coz u need variables cycles etc.. 07:37:41 true 07:57:39 wheres herk ? 08:18:01 --- quit: madwork (Read error: 104 (Connection reset by peer)) 08:20:32 --- join: madwork (~madgarden@derby.metrics.com) joined #forth 09:45:28 hi 09:47:01 Hi 09:55:18 hi 09:58:16 4 CED3 is16 a11 fullscreen6 editor8 and5 it14 rox! 09:58:30 8) 09:58:31 Nice colors. ;) 09:58:54 its pasted here from within ced 10:01:06 the main code is just these few line 10:01:07 s 10:01:08 : addspace >r 3 ( ^C) c!+ r> irccolors swap iexec 16 ( ^V) c!+ 16 c!+ 20 c!+ ; 10:01:08 : enter param ln> nip inp do i c@ dup space? if addspace else 10:01:11 c!+ then loop ascii ' c!+ 0 swap c! cmd system ; 10:01:14 --- join: Herkamire (~jason@h000094d30ba2.ne.client2.attbi.com) joined #forth 10:01:25 eh.. herk missed it ;) 10:02:18 hi onetom 10:03:47 hello herk 10:04:46 im just hacking tile & my color editor these days & im just very happy about it, coz it works reasonably 10:05:20 what's tile again? 10:05:26 and it is also able to interoperate w my irc client through gnu screen 10:05:43 so we could easyly talk about colored code now 10:05:58 nifty 10:06:19 ftp.gnu.org/gnu/non-gnu/tile-forth 10:06:45 4 CED3 is16 a11 fullscreen6 editor8 and5 it14 rox! 10:07:29 the basic editor functionalities r almost perfectly finished 10:07:42 bound checking for DEL is missing 10:07:48 backspace is missing 10:08:02 you are writing CED? 10:08:16 and intelligent SPACE & ENTER meaning hasnt been definied yet 10:08:21 Color EDitor 10:09:20 what are you doing with space and enter? 10:09:42 in herkforth ENTER executes the word on the spot, and space inserts it into the editor. 10:09:56 dont know 10:10:13 anyway its just an editor yet, not a workbench 10:11:02 @the moment enter pastes the "current line" into the irc window of my screen 10:12:25 tile looks very cool 10:12:35 its clean at least... 10:12:59 but its very dumb/minimal to some extent :( 10:13:23 yeah 10:13:31 my editor is pretty bare bones in many ways 10:13:39 i had to implement a bunch of words before i could do anything useful w it in linux.. 10:13:44 but has some mind bogglingly useful bits too 10:14:05 namely pressing SHIFT-F to go to the definition of the word under the cursor 10:15:27 there was no raw keyboard input, no system word, no double wordset, no "c,", no file wordset, no >= <= u> ... 10:15:55 hmm.. & how do u look for its definition? 10:16:04 raw keyboard... you mean getting keyups? 10:16:19 i mean key downs at first ;) 10:16:27 there is no KEY? 10:16:55 generally I don't look, unless it's moved 10:17:02 yes, there is, but the terminal is left in line buffering canonical mode.. 10:17:09 HashSet is a Set; so 10:17:10 my source words are an index into the dictionary and color bits 10:17:14 er ww 10:17:33 oh, that's a pain. I hate that terminal shit 10:18:03 Herkamire: ah, so ur editor is the chuck type huffman compressed halfcompiling editor? 10:18:04 so I just grad the field in the dictionary that says where the source is, make sure it's still there, and display. 10:18:22 (if it's not there then I search for a red word that points to that dict entry) 10:18:30 no, 10:18:33 no huffman shit 10:18:41 no text stored in the source tokens at all 10:18:46 terminal shit, huffman shit.. :) 10:18:47 the text is in the dictionary 10:19:24 source tokens are a 12 bit index into the dictionary, and 4 bits to indicate color 10:20:20 so 0x0031 would be the fourth word in the dictionary in green (1). 10:20:47 ooh :)) gotit. funny 10:21:00 how do you do colors in irc? 10:21:04 (irssi) 10:21:28 bbiab 10:27:31 back 10:27:52 I think the idea for storing source this way came from aha 10:28:08 and colorforth. I sorta merged the ideas 10:28:54 soon I will store each defenition seperately in a database, so I don't have to have that silly search thing. 10:29:11 and the stupid code I have that tries to guess where the begining and end of the definitions are 10:29:31 (the begining of a normal word is trivial to find, but for a constant, it is not) 10:54:07 Herkamire: google irc colors, 1st hit http://www.ircbeginner.com/ircinfo/colors.html 10:57:55 --- join: tathi (~josh@pcp02123722pcs.milfrd01.pa.comcast.net) joined #forth 10:58:58 Herkamire: 10:58:58 #include irccolors.fs create irccolors 10:58:59 ] n red green white cyan purple yellow brown 10:58:59 n n darkgray n n n n n 10:58:59 n red green white cyan purple yellow brown 10:59:01 n n lightgray n n n n n lightgreen [ 10:59:03 : addspace >r 3 ( ^C) c!+ r> irccolors swap iexec 16 ( ^V) c!+ 16 c!+ 20 c!+ ; 10:59:06 : enter param ln> nip inp do i c@ dup space? if addspace else 10:59:09 c!+ then loop ascii ' c!+ 0 swap c! cmd system ; 11:08:44 #include? 11:13:12 qFox: learn C 11:13:17 onetom: thanks 11:13:29 oh come on, that was uncalled for :) 11:13:34 i was referring to #include in forth 11:15:23 well, that's inconsistant 11:15:34 ? 11:15:52 it says ^O puts it back to normal colors, then later it says it's ^0 11:16:44 Linux Terminal? 11:17:37 tathi: is there such a thing as ^0 on the linux terminal? 11:17:54 the doc says it works on mIRC and PIRCH 11:18:04 I thought irssi might be the same 11:18:06 apparently not 11:18:19 No. 11:18:28 I'd assume it's a typo. 11:19:59 At least, there's no standard character code for it... 11:20:24 usually ctrl-whatever means subtract $40 from the char code. 11:22:41 that would make it negative... 11:22:48 well, here goes 11:23:08 2blue 11:23:10 yeah. Normally you just have A-Z, and [ \ ] ^ _ 11:23:12 wow 11:23:53 in irssi you hit ^C to change colors. that's nerve wracking 11:24:30 bold 11:24:40 test 11:24:44 Herkamire: ? 11:24:46 Herkamire: how? 11:25:03 arke: showing blue here. 11:25:42 arke: http://wiki.irssi.org/cgi-bin/twiki/view/Irssi/Colors 11:25:57 ^C then a number 11:26:05 it shows funky on the input line, but shows correctly in the channel 11:26:14 arke: that might just be how irssi does bold though. 11:27:10 bold is ^B 11:27:17 1hi 11:27:20 2hi 11:27:24 2hi 11:27:27 3hi 11:27:30 4hi 11:27:32 ;) 11:31:27 4red 11:34:15 --- quit: qFox ("this.is.not a.real.netsplit") 11:34:25 --- join: qFox (C00K13S@cp12172-a.roose1.nb.home.nl) joined #forth 11:50:50 --- quit: tathi ("leaving") 12:17:22 --- join: wossname (wossname@HSE-MTL-ppp73479.qc.sympatico.ca) joined #forth 12:43:28 --- join: tathi (~josh@pcp02123722pcs.milfrd01.pa.comcast.net) joined #forth 12:49:32 --- join: proteusguy (~proteusgu@69.79.24.31) joined #forth 12:53:37 Herkamire: sorry not being totaly clear about this color stuff, but i thought that code snippet will b enlighting enough 12:54:12 but of course it isnt. i didnt even tell the number base :) 12:55:33 onetom: I just glanced over it and it didn't make sense 12:57:20 tho thats the code what pastes the transformed colored source into the irc window ;) 12:58:19 100 $allot constant cmd 12:58:19 " screen -p 0 -X stuff '" dup cmd $cat $free cmd dup $length + constant param 12:58:19 : c!+ over c! 1+ ; : $end + 0 swap c! ; 12:58:27 i missed these lines 13:20:18 hi wossname 13:36:32 --- quit: tathi ("leaving") 13:38:30 --- quit: madwork (Read error: 110 (Connection timed out)) 13:44:37 --- quit: wossname (orwell.freenode.net irc.freenode.net) 13:44:37 --- quit: ianp (orwell.freenode.net irc.freenode.net) 13:44:37 --- quit: ChanServ (orwell.freenode.net irc.freenode.net) 13:44:38 --- quit: fridge (orwell.freenode.net irc.freenode.net) 13:44:38 --- quit: lalalim (orwell.freenode.net irc.freenode.net) 13:44:38 --- quit: SDO (orwell.freenode.net irc.freenode.net) 13:44:38 --- quit: proteusguy (orwell.freenode.net irc.freenode.net) 13:44:39 --- quit: Topaz (orwell.freenode.net irc.freenode.net) 13:47:42 --- join: ChanServ (ChanServ@services.) joined #forth 13:47:42 --- join: lalalim (~lalalim@p508ABC17.dip.t-dialin.net) joined #forth 13:47:42 --- join: SDO (~SDO@68.170.20.201) joined #forth 13:47:42 --- join: fridge (~fridge@dsl-203-33-162-85.NSW.netspace.net.au) joined #forth 13:47:42 --- mode: irc.freenode.net set +o ChanServ 13:48:16 --- join: wossname (wossname@HSE-MTL-ppp73479.qc.sympatico.ca) joined #forth 13:48:16 --- join: ianp (ian@inpuj.net) joined #forth 13:48:51 --- join: proteusguy (~proteusgu@69.79.24.31) joined #forth 13:48:51 --- join: Topaz (~top@spc1-horn1-6-0-cust217.cosh.broadband.ntl.com) joined #forth 13:58:01 --- join: Herkamir1 (~jason@h000094d30ba2.ne.client2.attbi.com) joined #forth 13:58:08 --- quit: Herkamir1 (Client Quit) 13:58:16 oops 14:07:50 --- quit: proteusguy (No route to host) 14:08:04 --- join: _proteus (~proteusgu@69.79.24.31) joined #forth 14:11:30 7w 19 14:12:22 mur: isn't it 6w20 though? I believe that was 0the attack for the Silver F0rost Blade.... 14:12:51 typo 14:13:14 ;) 14:13:51 3 14:15:08 hmm 14:15:36 i wish i had something in my head 14:16:12 don't we all, mur? 14:20:43 --- quit: wossname (";lA") 14:24:15 why does pygmyforth use PUSH and POP instead of >R and R>? 14:24:49 machine forth instructions? 14:24:51 i think its closer to the machine 14:25:05 since the return stack would be the hw stack? 14:25:09 you can always make aliases for them :) 14:34:12 thats why i dont use pygmy 14:34:40 that and it uses blocks (ick) 14:34:56 other than that pygmy is some awesome code! 14:36:49 you don' like blocks? 14:37:00 no 14:37:04 not for source files 14:37:43 you have to have your sources all stretched out horizontally leaving no room for ANY comments unless you fragment your sources by interleaving source and comments 14:37:49 code code code code code code codde 14:37:50 code code code code code code codde 14:37:55 comment comment comment 14:37:57 code code code code code code codde 14:37:58 comment comment comment 14:37:59 comment comment comment 14:38:03 looks like SHIT 14:38:57 --- join: warpzero (~warpzero@mi015.dn178.umontana.edu) joined #forth 14:39:22 I4_wrk: how about 14:39:24 code 14:39:25 comment 14:39:27 code 14:39:28 comment 14:39:29 bad 14:39:31 code 14:39:33 comment 14:39:36 ? 14:39:38 :) 14:39:39 it fragments the code up 14:39:50 it should. 14:39:51 use shadow blocks 14:39:55 leave just CODE to the left and comments to the right 14:40:00 hey guys 14:40:01 have pg up/pg down browse through source blocks 14:40:02 shaddow blocks are a horrible idea 14:40:05 each little thing should use its own little block, with its corresponding shadow block. 14:40:23 you have to keep switching from code to comments. my way you get both code and comments on the same page at the same time and they dont interfear with each other 14:40:32 you can chose to ignore either column 14:40:56 theres a reason newspapers publish articles in tall thin columns, its easier to scan down and speed read them 14:41:40 slava commented on my source files the other day... which looks better. blocks with shaddows or my sources ? 14:42:17 isforth has block files btw (but ive not fully tested the code) 14:42:33 im not sure about loading a block etc, probably doesnt work 14:43:56 I always figured you should display the shadow block to the right of the source block 14:44:37 there's certainly plenty of room on my screen 14:44:44 :) 14:44:54 I almost forgot about that. 14:45:00 blocks are just so "last century" 14:45:03 quite a while ago I planned out my screen usage 14:45:40 split most of the screen in half, so there are two big areas side by side taking up the top 3/4 of the screen 14:45:54 then the bottom can be used for text output/history 14:46:02 and a row somewhere for status information 14:46:35 aaarrrrg. mysql won't let me set a default for a TEXT field 14:46:52 it's right in the manual that you can't 14:47:09 I quit ;) 14:47:29 lol 14:47:40 is it just mysql or is it a SQL thin? 14:47:59 make it a binary field and just make sure you never put anything but TEXT in it :) 14:50:20 TEXT (just a case insensitive BLOB) is a field for large amounts of data 14:50:27 i think there must be some better way to organize source. there's a few nice things about blocks but they're too simple 14:50:49 I'm looking for better ways to organize source too 14:51:10 I'll get coding on my next idea as soon as I can make up my mind on how the db should work 14:53:43 here is the main() function of the new factor interpreter coded in C: 14:53:44 init_arena(); 14:53:44 load_image("factor.image"); 14:53:44 init_environment(); 14:53:45 run(); 14:53:46 source files NEED to be in flat files so that they can be editied with ANY editor on any system 14:54:14 no they don't 14:55:04 there's plenty of systems that get along fine without doing it that way 14:55:28 but you cant share the code 14:55:35 yes I can 14:55:35 they work on "that" system only 14:55:37 I do so regularly 14:55:50 not unless you convert it to a flat file 14:55:58 and why add an extra step just to share your sources 14:56:13 smalltalk 14:56:21 so I can avoid 8 extra steps to edit/parse etc 14:57:28 not using text makes my system much simpler 14:57:46 it's easy enough to output a text version of sources 14:57:55 in many cases I just copy from the terminal 14:58:23 colorforth has a couple utilities to convert blocks of source to html 14:58:50 it is not my intention to write large hunks of code that people can use in other forths as is. 14:59:30 to do that my forth would have to be too conventional 14:59:38 and would lose most of it's value 14:59:57 I want people to learn from the way it works, and perhaps find an idea that they'd like to use 15:00:24 the code won't work on other forths, so it doesn't matter if it's in a format you can paste it there. 15:02:56 it is important to be that it is in a format where people can easily browse and learn about it 15:03:08 which flat text files aren't all that good at imo 15:03:44 I've started writing some code to translate herkforth code to html that will display in color with everything being a link to it's definition. 15:07:29 Herkamire: cool 15:07:31 Herkamire: i have the same thing but by decomping definitions in the currently running image 15:15:39 excellent. image loading/saving seems to work for simple cases at least. 15:17:11 I compile to native ppc code, so decompiling is tricky 15:17:27 ah 15:17:35 (and pointless, since I have the source) 15:18:12 --- join: doublec (~doublec@202.36.204.41) joined #forth 15:20:56 hi doublec 15:21:05 hi slava 15:21:18 slava, I got some initial support for callbacks now. 15:21:58 "Press me" [ run-something ] quot-href 15:22:02 the C interpreter now successfully loads an image. 15:22:15 That will put an anchor link that when pressed runs the code then returns back to display the calling page. 15:22:27 cool 15:22:29 call, the c interpreter has made a lot of progress then! 15:22:39 I struck a problem with 'workspaces' in 0.60.1 though 15:22:45 what is it? 15:23:13 --- join: crc (crc@0-1pool176-28.nas6.philadelphia1.pa.us.da.qwest.net) joined #forth 15:23:16 I'm sending it in an email now...it's easy to explain that way 15:25:11 slava, just sent 15:25:30 basically starting an interpreter pointing to an existing filestore database gives errors. 15:27:04 i'll take a look. 15:27:10 btw the C interpreter will have a much simpler persistence system. 15:27:26 it loads/saves images, which are basically memory dumps with relocation done on load 15:28:26 cool 15:28:58 An advantage of the C interpreter is being able to run it on smaller devices (pda and phones come to mind). 15:33:07 doublec: i'm going to write a cross-compiler now 15:33:55 slava, to compile to C code? 15:44:15 --- quit: SDO (Read error: 110 (Connection timed out)) 15:48:33 doublec: no 15:48:37 doublec: to produce images 15:49:49 --- part: crc left #forth 15:52:21 slava, oh I see. So you'll be able to cross compile to ARM on an intel machine? Nice. 15:59:55 bye 15:59:56 work 16:04:28 --- quit: warpzero ("Tried to warn you about Chino and Daddy Gee, but I can't seem to get to you through the U.S. Mail.") 16:13:35 doublec: images depend on byte order and word size 16:13:43 although i'll lift the first restriction 16:15:44 doublec: grab the latest jedit.org/factor/CFactor.zip 16:16:45 slava, will do thanks. 16:19:04 slava, I get errors running build.sh when trying to compile some of the files. 16:19:16 shuffle.c:6: error: conflicting types for `primitive_drop' 16:19:17 stack.h:4: error: previous declaration of `primitive_drop' 16:19:17 shuffle.c: In function `primitive_drop': 16:19:17 shuffle.c:7: error: too many arguments to function `dpop' 16:19:17 shuffle.c: At top level: 16:19:19 shuffle.c:11: error: conflicting types for `primitive_dup' 16:19:21 stack.h:2: error: previous declaration of `primitive_dup' 16:19:23 shuffle.c: In function `primitive_dup': 16:19:25 shu 16:19:37 I'm using gcc 3.3, do I need 3.4? 16:19:38 what gcc release? 16:20:00 it compiles here with 3.4 and 2.96 16:20:17 i'll do some investigating... 16:20:31 oh my fault 16:20:34 zip file includes obsolete sources 16:20:38 ok 16:20:39 shuffle.c is not part if the system anymore 16:21:13 ok get it again 16:22:01 ok that worked, thanks. 16:22:10 its very crude 16:22:13 try this: 16:22:22 ./f a -- running it with any cli arg will write factor.iamge 16:22:33 ./f -- running with no arg loads factor.image and executes the bootstrap quotation 16:22:39 in this case, the bootstrap quotation is [ 30 fib ] 16:22:59 cool, runs fine. 16:23:07 now try 30 fib in java factor 16:23:20 --- join: madgarden (~madgarden@Kitchener-HSE-ppp3576399.sympatico.ca) joined #forth 16:23:33 hi madgarden 16:23:42 hi ya, slava. 16:23:46 quite a bit faster in C isn't it 16:24:02 doublec: look at run.c 16:24:34 madgarden: where in canada are you? 16:24:44 madgarden: youre making a C forth no? 16:25:22 I'm in Kitchener, ON. And yea, I've got a C Forth-like system. 16:25:40 http://sourceforge.net/projects/forthy 16:26:19 slava, so env.boot should contain the boot quotation that gets run on load of the image? 16:26:29 doublec: yup -- see image.c, load_image() 16:27:56 doublec: note that right now 'env' is a global variable but at some stage it will become a macro or a parameter that's passed around 16:28:30 If you want multiple VM instances, that's a good idea. 16:28:52 or threading 16:28:58 doublec: language change! 16:29:33 doublec: FactorArrayStack is now FactorArray -- stack-push/pop is now array-push/pop, and there is array-nth and array-length words 16:30:24 slava, ok I'll make a note of that. 16:30:38 it means you can use arrays now basically. 16:31:04 slava, globals are also bad one some platforms like Symbian where you can't have global or static variables. 16:31:36 (Symbian being a phone OS) 16:33:14 doublec: on second thought -- a few 'array' words exist for working with bare java arrays, so i'm naming the new concept 'vectors' 16:33:31 5 over vector-push 16:33:51 slava, ok. 16:34:28 slava, how do push/pop on vectors compare to cons/car on lists for efficiency? 16:34:57 (ie. do the vectors grow and copy when reaching a certain length) 16:35:37 a pop is just a array fetch + pointer decrement 16:35:45 a push is a possible array doubling, + pointer increment 16:36:08 the benefit here is vector-nth for random access, and constant-time vector-length 16:37:07 --- join: blockhead (default@dialin-646-tnt.nyc.bestweb.net) joined #forth 16:37:34 definitely 16:40:32 doublec: i'd like to use your cont-responder for the wiki-editor. 16:40:36 --- nick: _proteus -> proteusguy 16:40:40 doublec: to avoid the explicit post request handler, and edit? urls 16:41:27 slava, it should work fine for that. It really needs a means of expiring the saved continuations though or memory will run out eventually. 16:41:42 slava, which is my next task. 16:41:50 I'm uploading the newer version now. 16:42:59 www.double.co.nz/factor/cont.txt and www.double.co.nz/factor/cont-responder.factor 16:43:13 This has the support for anchors to quotations 16:43:20 also what if people forge the continuation ids 16:43:28 i know its almost impossible but you should check for ip address too 16:43:56 brb 16:44:01 Yeah, that's the plan. Ideally the continuation id would be a cryptographically secure random number too 16:45:03 --- quit: madgarden ("*frotz*") 16:45:56 --- join: madgarden (~madgarden@Kitchener-HSE-ppp3576399.sympatico.ca) joined #forth 16:50:58 I also want to allow attaching callbacks to form input elements and buttons. This allows you to run code when select lists are chosen, data is entered in text fields, etc. It makes creating re-usable widgets quite easy. 16:51:23 that sounds really cool 16:51:42 ideally you'd create forms from s-expressions... 16:51:49 yes. 16:52:11 although I'm torn between generating everything into a string of html that gets sent in one go, or streaming the html as needed. 16:52:32 doublec: ? 16:52:34 streaming means it renders in the browser immediately and you can do nifty tricks with 'publish/subscribe' or javascript rpc things. 16:52:52 yes I use at the moment. 16:53:04 But that builds a string up which gets sent in one go. 16:53:23 (which is what I want it to do of course) 16:53:31 but streaming directly to the socket has some advantages 16:53:49 : with-string-stream ( quot -- string ) 16:53:49 #! Call the quotation with standard output bound to a string output 16:53:49 #! stream. Return the string on exit. 16:53:49 [ 16:53:49 "stdio" put call "stdio" get stream>str 16:53:50 ] bind ; 16:53:54 is what I use 16:54:30 maybe its better to have with-stream ( stream quot -- ) 16:54:36 which rebinds stdio and runs the quotation 16:54:46 good idea 16:54:48 at the mo we have with-html-stream with almost identical code 16:55:26 do you think s-expression based building of html would be a good fit with factor? 16:55:41 or sticking with building things up via [ ... ] form , etc 17:01:07 by s-expression building i mean the [ ... ] form :) 17:01:35 cool. I was wondering why you would be advocating (... ) :) 17:01:39 new functions: logor lognot logand 17:01:45 bitwise operations 17:01:46 How would attributes be handled in that form? 17:01:58 never mind 17:02:02 depends 17:02:08 taken from the stack i expect :) 17:02:09 items on the stack I suppose 17:02:18 :) 17:02:52 at one stage i want to get a 'real' server that can run the factor httpd for us to play with 17:02:59 so that the factor homepage can be hosted there 17:03:21 cool 17:04:10 I have a 'user mode linux' server I use (which I got from www.linode.com). It runs factor quite well. 17:07:24 slava, try: http://www.modalwebserver.co.nz/inspect/ 17:07:29 This is running on the UML server 17:07:44 ah cool 17:08:31 It's not running to a db though as it's using 0.60.1 where I'm having that problem. 17:10:02 UML introduces very little overhead in itself. There are several hosting services that give people virtual machines under UML. 17:10:13 They'll put 8 or 10 users on one CPU. 17:10:35 yep. Quite cheap too. 17:11:02 the main cost tends to be if you want more memory. 17:11:27 --- quit: proteusguy (Read error: 54 (Connection reset by peer)) 17:11:34 Yah. If you want performance, you need at least as much real memory as the number of UML sessions memory added up. 17:11:54 --- join: proteusguy (~proteusgu@69.79.24.31) joined #forth 17:12:03 yes. linode.com guarantees that they have enough real memory for each UML session on the host IIRC. 17:12:25 If you have 25 UML sessions on a 512 MB box, and each UML session is configured for 512MB, it'll swap like a sumnabitch (assuming all 25 UML machines are making memory requests). 17:13:12 i/o is also a problem sometimes. If some of the UML session are pounding the disk then it can affect the others a bit. 17:13:27 I played around with that a little here. I had 8 UML machines running at one time, each with 512MB on a box with 1GB. I wrote something that allocated a huge honking array, and randomly skipped through on 4K boundaries. It thrashed. Badly. 17:25:09 A nice gforth feature would be 'include help.fs help ' to display help on a given word while in the interpeter. 17:27:15 or show documentation comments in 'see' :) 17:27:45 1; 17:32:43 jc thats been on my mental todo list for isforth from day 1 17:33:04 you can ask futhin about that cuz he requested it and i already told him its already planned lol 17:34:33 Kewl. 17:35:03 --- join: solar_angel (~jenni@Toronto-HSE-ppp3685160.sympatico.ca) joined #forth 17:35:05 And did I just find a buglet in gforth-0.5.0? 1 2 3 4 5 5 pick returns 0. Should give a stack underflow, me thinks. 17:35:53 bbl 17:36:42 jc - forth (even gforth) isn't a safe language 17:36:49 catching a stack underflow is tricky business. 17:37:02 and gforth doesn't have the benefit of a protected page or segment protection 17:38:25 I know Forth isn't a safe language. But gforth is usually pretty good about detecting stack underflows, in my experience. 17:38:27 doublec: look at this: 17:38:28 9] cross-compile vector>list . 17:38:28 [ 252579084 0 0 0 32 6 4 5 ] 17:38:47 doublec: this is the minimal image that boots and does nothing :) 17:39:01 howdy solar_angel 17:39:04 hi slava. 17:40:10 solar_angel: i'm making my language self-hosted. having java as a host platform got to be a pain 17:40:39 java as a host platform? ick. 17:45:11 sweeet. PicForth doesn't have 2swap. 17:45:13 solar_angel: please explain why intel decided to be retarded and went with little endian. its complicating the cross compiler :) 17:45:39 I don't think little endian is retarded. 17:45:43 little endian isn't retarded. 17:45:44 slava. they did it for one GOOD reason 17:45:47 it's quite useful for type conversion 17:45:47 to PISS US OFF!!!! 17:45:53 slava: it has its moments 17:46:02 typing is a crutch for poor programmers 17:46:04 Actually, there are hardware design reasons that make little endian a good choice. 17:46:05 -- chuck moore 17:46:11 far and few between, but still moments 17:46:53 Humans are writing numbers backwards. 17:46:59 But I'm sure once the realized they inconvienenced you, they'll fix it :) 17:47:07 Hehehe 17:48:07 How is typing a crutch? Was he thinking we'd have voice activated computers by now? Direct neural interfaces? DWIM machines? 17:48:19 robert actually when you add two numbers you should start at the upper end and work down 17:48:19 jc: typing as in data types not keyboard 17:48:24 I know :) 17:48:28 jc: dip switches to endter binary codes, of course :D 17:48:44 thats a much more economical method and you can stop half way and have an appriximation :) 17:49:22 I carried my IMSAI into the house yesterday. I almost plugged it in, but I need to pull out all the boards to make the caps aren't dried out and go *kerblooey*. The only switches nicer than those on an IMSAI are those on a PDP-11. 17:49:52 hrm... i should get one of the PDP-11's running sometime. 17:50:17 Hell, I'll drive up to Canada and pick on up, if it's an 11-74 17:50:46 i've mostly spent time with the "luggable" PDP-11's. 17:50:51 they're some sort of weird clone machine 17:50:58 Gotta URL to one? 17:51:16 nope. i've never seen them anywhere other than in front of me. 17:51:45 Whgat's the name/model? 17:52:06 i don't recall.. and i don't want to go dig one out :P 17:52:14 *please*? 17:52:20 lol 17:53:14 fedex one to him 17:53:16 :) 17:56:00 nope :) 18:01:37 I rule! 18:02:04 fedex one to me ????? 18:02:05 hehe 18:02:06 smooch! 18:02:58 * Robert fedexes an ENIAC clone to I440r 18:03:14 :) 18:03:34 ill take the analytical engine too please :) 18:04:03 babbage was a piss poor coder tho, he kept redesigning his engine 18:04:13 and having to start over. thats what killed it 18:04:50 actually, the difference engine works 18:04:53 it's been built, lately. 18:04:58 i know 18:05:09 Out of lego, or something. 18:05:14 constructix? 18:05:21 Some kinda sheet metal stuff. 18:05:22 his initial design would have probably worked too but he kept making changes to parts taht had already been built 18:05:41 his backers abandoned him 18:06:28 http://www.digibarn.com/collections/calculators/wolverine-adding-machine/TN_toy-computer2.JPG REal computer 18:07:33 I rule! 18:07:40 oh, I said that already 18:08:03 I'm all excited because I just made $8.85 playing fiddle on the street 18:09:09 lol 18:09:14 did you play well? 18:09:23 or were they just trying to make you shut up ? 18:09:25 heh 18:09:31 i suck at guitar right now, been too long 18:09:51 JESUS CHRIST. Not only does PicForth not have 2swap, it doesn't have pick. 18:09:59 lol 18:10:08 youda thunk pickforth would have PICK!!!! 18:10:13 Yah! 18:10:15 lol 18:10:18 feh: who needs pick :D 18:10:22 lol 18:10:28 pickforth obviously :) 18:10:32 what stack ops are the most important? 18:10:39 2swap is easily written 18:10:41 Right now, pick. 18:10:48 You wish it was. 18:10:48 rot over swap drop dup 18:11:16 jc: don't make me dig up the code :D 18:11:29 Hm. 18:11:43 swap over drop dup, rot nip 18:11:44 How is the last dup going to give you anything valid? 18:11:54 i'm going to do 'pick' on an AVR using the indirect-addressing-with-offset opcode 18:11:56 speedy 18:12:05 Hehe 18:12:07 Doing anything efficiently on a PIC is a bitch. :) 18:12:14 yup. 18:12:19 And AVR even beats x86 when it comes to addressing 18:12:26 6809++ 18:12:49 Anyway, I'd like one of Zuse's machines. :) 18:12:56 I want to find someone with a couple 1805 or 1806 chips that don't realize what they have. 18:13:04 some of these AVR forth words are surprisingly short 18:13:05 hehe 18:13:13 jc: What are those? 18:13:18 'add' in two opcodes 18:13:18 "no really, they're useless, can i have them?" >:) 18:13:40 Topaz: Yeah, since you have several register pairs with auto-inc/decrementing 18:13:42 They're members of the 1802 family (Cosmac Elf) that had some extra instructions to support Forth more natively. See http://www.cosmacelf.com 18:13:52 Topaz: Pretty amazing. 18:13:52 ah, yeah 18:13:58 two for add? :\ 18:14:31 only a 8-bit add though 18:14:33 Is this with or without stack cache? 18:14:37 but it is only a 8-bit proc 18:14:37 TOS cache 18:14:40 TOS in register 18:14:58 oh 8bit cpu? 18:15:12 how many bits per instruction? 18:15:12 Microcontroller. 18:15:15 16 18:15:19 hu? 18:15:19 ld temp, Z+ 18:15:27 add tos, temp 18:15:31 (that's the add :D) 18:15:37 Hehe. 18:15:47 How far along are you with that? 18:16:17 --- quit: qFox ("this.is.not a.real.netsplit") 18:16:17 But then again, I tend to give up on high-level (as in, above assembly language) languages and just write it all in assembly language. 18:16:27 i've implemented colon, with some basic optimisation, and 'add', 'if/else/then', 'begin/loop', and, hmm, that's about it 18:16:28 I am *so* over that. 18:16:36 oh, and 'code', so you can define words in assembly 18:16:42 (with a basic assembler, which is also rather incomplete) 18:16:51 Is it compiled to machine code, or are you running an actual interpeter? 18:16:58 : 2swap ( n1hi n1lo n2hi n2lo -- n2hi n2lo n1hi n1lo ) 18:17:00 compiled to machine code (STC) 18:17:03 >R ( n1hi n1lo n2hi ) 18:17:09 rot rot ( n2hi n1hi n1lo ) 18:17:16 R> ( n2hi n1hi n1lo n2lo ) 18:17:23 rot rot ( n2hi n2lo n1hi n1lo ) 18:17:24 ; 18:17:31 cute :) 18:17:31 (untested, from memory) 18:17:38 could be more ffeicient, but ti works 18:17:50 (well, it *shoudl* work) 18:17:54 rot rot is -rot, is it not? 18:18:02 right, but -rot is nto in all forhts 18:18:14 so I wrote it as rot rot 18:18:15 -rot I've actually got. 18:18:21 good: -rot is handy 18:18:37 blockhead: Ouch 18:18:38 i miss my old optimizer. 18:18:50 blockhead: Using lots of "rot"s looks painful. 18:18:50 ROT would usually compile to no machine instructions. 18:19:21 because of that, i defined -ROT to simply be ROT ROT. 18:19:25 which was still no instructions 18:19:27 I lied. No rot, no -rot. It justhadn't gotten that far to get the errors. 18:19:43 Robert: I am more than open for more efficeint implementations :D 18:20:09 blockhead: Well, implementing basic stack manipulation words in Forth makes me scream in pain. 18:20:19 High-level Forth.- 18:20:22 heh. 18:20:36 Robert - you'd be in lots of pain if you saw my old definitions with the optimizer then 18:20:45 but the funny part is that most of them compile to no instructions, even so 18:20:48 Robert: well, when you find yourslef using a forht that doens;t have 2swap, it's what you gotta do :D 18:20:59 solar_angel: Obviously that's not what I meant. 18:21:16 blockhead: No, no.. :) 18:21:22 blockhead: You rewrite the Forth ;) 18:21:48 Robert: time permitting, yes :D 18:21:51 i don't think i've ever had to use 2swap. 18:22:03 solar_angel: me neither 18:22:12 2over I use a lot 18:22:21 2over and even 3over i've used from time to time 18:22:24 but 2swap is a rare one 18:23:23 then again, my stc forth has a really efficient R> and >R 18:23:59 R> and >R are kind of crucial (well, at least for me) 18:24:04 Yes, R> and >R are nice. 18:24:37 i've hardly ever had to use R> and >R... 18:24:55 but the ones in my FORTH are generally more efficient even than a ROT, so i use them. 18:25:05 solar_angel: I guess it's a style thing, or the way you think? 18:25:20 The problem with me is that even when I tell myself to do it the way a mathematician would - writing elegant definitions in Forth, building on other Forth definitions, I end up trying to save one clock cycle in the start-up code using machine language. 18:25:24 * blockhead finds that >R and >R saves a lot of trouble 18:25:50 the way i think, i think... i very seldom have to juggle ths stack. 18:26:06 Robert: you would absolutely hate my forth :D (lots of secondary words, very few primary (machien code) words) 18:26:16 Well 18:26:19 I like beaty 18:26:22 beauty 18:26:39 slava, the cross-compile looks good. Nice and small empty image :) 18:26:40 I like being able to get it working :D I *am* a blockhead after all :D 18:26:43 But on the other hand, I can't stand it if I know there's something ugly begind it 18:27:04 And if there is, I might as well do some ugly optimization tricks. 18:27:16 Which kind of is beautiful itself. 18:27:19 So... 18:27:37 hehehe 18:27:41 never use roll :D 18:27:48 roll ? 18:28:02 roll?!??!! 18:28:10 i don't even implement that one, on principle. 18:28:10 I'm not sure if it is a standard word or not, but it can get fugly 18:28:25 I've heard of it. 18:28:28 But I mean... 18:28:32 the source code for e forth has a comment: "never use roll" (right next to the source for roll) 18:28:32 my FORTH is quite dire, given that's hard to work out where the FORTH stops and the emulator starts 18:28:38 If you need more than the basic stack words, something's gone wrong. 18:28:47 what does roll do? 18:28:48 Robert: word! 18:28:58 Topaz: you don't wanna know 18:29:03 OK, now, nobody look at my Forth code. ;) 18:29:05 :D 18:29:23 Topaz: it's like a ROT, but for N elements 18:29:33 i have FORTH code being called from an interrupt context. now that's funny. 18:29:42 solar_angel: cool! 18:30:03 blockhead - my FORTH is bootable. 18:30:10 it's an OS, actually. 18:30:15 a section of "evil" code from my forth: : -rot rot rot ; 18:30:25 solar_angel: that's even cooler that it boots! 18:30:46 blockhead - now that's evil, unless you have an optimizer like my old one which transparently expands that to no code. 18:30:57 it boots quite well, actually 18:31:09 some memory manglement issues left to resolve... but it's coming. 18:31:09 solar_angel: this is my first forth. My primary concern is to (a) get it runnign at all and (b) there i sno B 18:31:17 *nods* 18:31:28 this is in a way my first FORTH... and in a way, my fifth or sixth. 18:31:30 memory managemnet problems? just live in a 64 k world :D 18:31:47 blockhead: That's how I end up doing things. 18:31:54 blockhead: Fast, or not at all. 18:32:52 heh. 18:32:58 Robert: I'm not a grear programmer. I can't sweat fast, because I'de never get anything working ever 18:33:18 sometimes I get stuff to run fast, but usually ona rewrite a year or so later 18:33:23 :) 18:33:39 my pitch shifter is fast, but that's in c not forth. :D 18:34:09 I and another guy are having a coding contest for this 4-bit (simulated) computer, with a 4-bit RAM address space and 4-bit words. 18:34:20 Which means, 8 bytes of RAM. 18:34:29 * blockhead faints 18:34:35 Will it run Windows? 18:35:01 lol 18:35:08 8-bit code memory address space, 8-bit instructions (including jumps). 18:35:15 i have a fun architecture... 32-bit machine with 4-bit instructions. 18:35:36 solar_angel: 8-bit machine with 3-bit instructions. 18:35:41 solar_angel: what do you do with the extra (32-4) bits? 18:35:51 jc: Yes. 18:36:03 blockhead - instruction words are 8 instructions per word. 18:36:09 jc: Windows XP, with a heavy theme, will run perfectly on it. 18:36:42 * blockhead looks confused 18:37:27 it turns out that 1.9999999992gb of the windows xp installation is just needless bloat 18:37:55 Topaz: Suprise! 18:38:00 Topaz: this differs from previous versions? :D 18:38:07 --- quit: solar_angel ("*later*") 18:40:33 As long as your windows are 1 pixel x 1 pixel (aka, a single LED), it'll run fine. 18:41:19 jc: One LED is enough to send morse code. 18:41:32 infact, with testing, it was discovered that windows didn't need a CPU at all, and a battery and switch would suffice 18:43:03 4-bit port of Windows.. mm.. 18:43:47 i'd quite like to make a magnetic drum computer out of discrete transistors 18:44:03 LOL 18:45:00 uhhhh.... 18:45:21 How's that work, exactly? 18:45:44 http://wombat.doc.ic.ac.uk/foldoc/foldoc.cgi?The+story+of+Mel,+a+Real+Programmer 18:46:09 --- quit: proteusguy ("Leaving") 18:46:39 Topaz: Yes... 18:46:44 Topaz: That would be pretty neat. 18:47:07 i could run it with the case off, and have it sitting on the desk whirring around at 10hz, or however fast i can clock it ;) 18:47:07 Topaz: Do you know some tricks to get away with few enough transistors for that to be possible? 18:47:30 It would be so sexy. 18:47:31 not that i've researched :D 18:47:38 i'm anticipating requiring a couple of thousand of them 18:47:41 but i may go the SMT route 18:47:44 for comedy value 18:48:13 I'm still unclear on the concept. 18:48:48 they use the drum as memory storage, and quite possible program as well, i think 18:49:01 and the processor clock is synchronised to the data reads off the drum 18:49:06 Hm. 18:49:19 Right. I'm familiar with the actual product. 18:49:19 (i think) 18:49:28 I'm unclear on how you plan to implement this. 18:49:33 Topaz: The Manchester University says their first transistor computer used around 150 (very unreliable) Ge transistors. 18:49:38 Since magnetic drums are just about impossible to come by. 18:49:38 ping doublec 18:49:40 as you have probably gathered, i haven't thought this through :D 18:49:48 yeah, that's the tricky bit 18:50:00 i was rather hoping i could acquire a functional magnetic drum storage unit 18:50:16 Build a punch card reader. 18:50:17 Those things were unstable as hell. That's why they didn't last long. 18:50:48 hi slava 18:50:50 punch cards would be amusing, though i still need something suitably bizarre to use as RAM 18:52:53 Topaz: A RAM built out of BJTs is exotic enough, I think. 18:53:21 Topaz: Especially since you can connect the LEDs directly to your RAM bits. 18:53:30 there is some very cheap stuff on ebay 18:53:32 Topaz: Which means you can easily see what's going on in the computer. 18:53:33 http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&category=36332&item=3822249681&rd=1 18:53:36 Such as? 18:53:48 Sorry, web browser takes an hour to launch here. :) 18:53:55 i could have a LED on every single RAM bit, would be quite amusing 18:54:06 a PCB covered in twinkly lights 18:54:11 though i'd rather use the LCDs to make something more fun ;) 18:54:13 How much RAM do you need for a useable computer? 18:54:18 like a wearable display 18:54:29 I'd say a few bytes. 18:54:38 *shrug*, 20-30 bytes would be lots 18:54:41 That makes like an 8x8 LED display. 18:54:58 Let's see how much I can write for this 4-bit thingie. 18:55:08 and of course, it'd be a FORTH-intended proc :) 18:55:15 ie, hardware stacks 18:55:24 Hehe. 18:55:43 I'm doing a register machine. Since the address space is 4-bit, that's not too hard. 18:56:21 --- quit: doublec ("Leaving") 18:56:32 this would need a work register or two, i would imagine 18:56:33 Actually it's a part of my make-evil-little-computer project. 18:56:44 Yes 18:56:48 this thing would probably be anything but little, but would be a fun task 18:56:53 The first two registers have kind of a special status. 18:56:56 Hehe 18:57:05 Little, as in "not huge". 18:57:05 250mhz... That should be fast enough for this. 18:57:08 and amusingly might actually clock pretty quickly 18:57:31 i might squeeze 10-20mhz out of modern transistors 18:57:45 Hehe. 18:57:50 Better get a good PSU ;) 18:58:21 though i refuse to design anything using PNP transistors ;) 18:58:25 I think your biggest problem is going to be capacitance, slowing down the switching time. If you have long logic chains, you'll have to slow the clock for propogation. 18:58:44 yeah 18:58:55 ie, ramp up the clock until it breaks :D 18:59:22 Mix the old and new. Use a Xilinx, code the processor, and then find some old core memory out of a PDP-8 or a DG Nova to use for storage. 18:59:31 http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&category=36332&item=3822351606&rd=1 18:59:34 Hehehe 18:59:34 *lots* :D 18:59:47 heh, if i could get hold of a xilinx, i'd be over the moon 19:00:35 Topaz: Neat. :) 19:00:36 Unless you want something like an XE4000, they're easy to find. I dunno how many gates you need, but things like the 2084s are common as dirt. 19:00:40 Strip some old equipment. 19:00:51 Topaz: But you can get new ones on mouser.com for about the same price. 19:01:03 Even lower I think. 19:01:11 BC54* are cheap there. 19:02:00 2n2222a, 2n3904, 2n3906 are some of the most common transistors there are. 19:02:18 BC547s are the cheapest here 19:02:55 Where's 'here'? 19:02:59 UK 19:03:18 1.7p each if you buy enough, hmm 19:03:22 Transistors over there drive on the wrong side of the bus? :) 19:03:40 heh, just electronics suppliers aren't particularly cheap here 19:04:13 xilinx advertise extensively their latest '$10 ASIC-killers', yet you can't get them for less than $300 here in any volume 19:04:49 jc: I checked with Mouser.com, and BC54* seem to be even cheaper (while at the same time having better specs) than any other of the common transistors. 19:05:28 interesting 19:05:41 Yes, I didn't expect that. 19:05:46 But I didn't complain :) 19:06:27 Lattice has some nice parts, and free tools. 19:12:05 anyway, bed 19:13:09 Night 19:13:58 --- join: kc5tja (~kc5tja@66-74-218-202.san.rr.com) joined #forth 19:14:07 --- mode: ChanServ set +o kc5tja 19:15:27 --- quit: I440r (Read error: 110 (Connection timed out)) 19:16:13 Hi kc5tja 19:16:25 re 19:16:39 hey kc5tja 19:16:49 I want to make a simple calculator out of hoses and valves 19:16:52 and run water through it 19:17:02 Herkamire: neat! 19:17:03 Hehe. :) 19:17:24 I haven't decided what the power source should be 19:17:38 pressure source, you mean :D 19:17:41 --- join: I440r (~mark4@216-110-82-1.gen.twtelecom.net) joined #forth 19:17:42 maybe hang a bucket of water 6 feet up 19:18:07 kc5tja: Since you're into digital design, I thought I'd ask you a silly question... Where can I find information about how to design gates, adders, counters (etc., various digital functions) using as few transistors (bipolar) as possible? 19:18:08 Kinetic art. 19:18:25 Herkamire: That would be pretty nice 19:18:41 The water company could probably take care of the pressure part for you. :) 19:18:46 (for a small fee...) 19:18:47 Most introductory logic texts explain how to make adders and the like out of ordinary gates. 19:18:53 kc5tja! 19:19:01 kc5tja: Right. But is there no short cuts? 19:19:04 kc5tja: i've been playing with pygmyforth. 19:19:23 are* 19:19:24 Robert: Not really. No. 19:19:34 You're bounded by the laws of physics. 19:19:41 Robert: yeah, I might make it hook up to a garden hose 19:19:58 slava: Cool. I downloaded DOSBox and tested it out last night before I went to bed. AWESOME product. Blows dosemu clean out of the water I think. 19:20:24 bonus if it squirts water around :) 19:20:50 kc5tja: Heh, right. Well, thanks anyway... 19:21:24 --- quit: Topaz (Remote closed the connection) 19:21:36 I just need to figure a cheap way to make/buy transisters 19:22:02 so preshure on one hose closes a valve on another 19:23:09 could be expensive. 19:23:21 I want to at least do a 3 bit adder 19:27:09 kc5tja: i'm running pygmy in dosbox 19:28:52 :) 19:29:45 Herkamire: It ought to be an interesting project. I think the key to making a water transistor is that fast-moving water has less pressure than high-pressure water. 19:31:28 me tries to parse that 19:31:53 blockhead: It's called "Bernoulli's Effect", also erroneously called the Venturi Effect. 19:32:04 kc5tja: fast-moving water has less pressure than high-pressure water 19:32:12 blockhead: Yes. 19:32:23 kc5tja: did you mean "fast-moving water has less pressure than slow-moving water" 19:32:35 Oops, yes. Sorry, even I missed that. 19:32:39 ok 19:32:46 ok, the cross-compiler successfully produced a VM image that outputs the number 30 and exits. 19:33:24 [ 252579084 0 0 18 24 6 4 5 2 120 11 ] 19:33:31 that is the image, in human-readable from :) 19:35:41 Heheh :) 19:36:06 120 is the number 30 -- the lowest 2 bits are the tag, and 00 is an integer. 19:40:12 kc5tja: yeah, I'm guessing it will take some waiting before all the transisters flip to the correct position 19:41:17 if I use 1/4" internal clear plastic tubing, and lay it all out on a board... 19:41:36 it might take a whole seccond for the add to finish 19:48:34 That's not human readable, if it's decimal. IT MUST BE HEX. 19:48:50 ok, with my first stab at it, I need 5 ANDs and 3 XORs 19:49:42 r... my first guess for what I need. 19:54:02 --- join: tathi (~josh@pcp02123722pcs.milfrd01.pa.comcast.net) joined #forth 19:56:34 kc5tja: in your Kestrel emulator, do all the tests in asm-test.fs pass for you? 19:56:58 tathi: Yes. 19:57:01 hmm. 19:57:09 I don't release anything unless all the tests pass. 19:57:35 Because the branch stuff isn't working right here, and looking at the code, it doesn't look like it should. 19:58:09 tathi: What tests are failing? 19:58:13 t59 19:58:22 it's advancing before doing the branch 19:58:27 (also after, of course) 19:58:33 What is "it"? 19:58:40 oh, sorry. 19:59:02 0 org nop, nop, nop, $A jz, nop, 19:59:18 No, I meant what the pronoun "it" was referring to. But that's OK. I see the problem. 19:59:24 That's odd that it works for me. 19:59:32 t59 tests to see that the three nops and the jz are in the same word. 19:59:36 * kc5tja tries something to get the bug reproduced... 19:59:39 And looking at the code... 20:00:00 : branch, ( ea n -- ) 20:00:01 ?advance keepTrack slot @ instruction! ea! advance ; 20:00:11 Oh, yeah, you're right. 20:00:14 I AM able to reproduce it. 20:00:18 ?advance looks like it is supposed to advance _except_ if you're on slot 0. 20:00:24 I must have skipped the unit test for v0.1.6. 20:00:28 OK. 20:00:33 Shame on me. 20:00:37 Was wondering if I was going crazy there. :) 20:00:42 Yeah. 20:00:49 See, you did find a bug. But it's not in the code. :) 20:00:55 It's in the unit tests. 20:00:59 ? 20:01:04 Unit tests can be buggy too. 20:02:01 0 org nop, nop, nop, $A jz, *should* fit in one word. 20:02:14 'nn all 20:02:22 3 nops 20:02:25 --- quit: blockhead ("laugha while you can, monkey boy") 20:02:29 jz opcode 20:02:32 jz operand 20:02:36 that's 5 by my count. 20:03:22 5*6=30 20:03:27 Am I missing something? 20:04:14 Oh. 20:04:29 you're only assembling branches in slot 0. 20:04:40 Rather than doing the check to see if it fits in the remaining slots. 20:04:41 yeah. I ran into too many assembler-related bugs otherwise. 20:04:43 Doh. 20:04:45 my bad. 20:04:54 And I forgot to update the unit tests apparently. 20:05:25 * kc5tja is making a new upload for you to grab. 20:05:27 just a second. 20:05:37 tathi: Or, do you have darcs? 20:05:50 Nope, GHC doesn't work on PPC 20:06:08 Hmm, actually I should check that again -- it didn't last time I wanted it... 20:06:13 Actually, it does. But it's a bear to get it to compile. 20:06:35 tathi: Are you using MacOS X or PPC/Linux? 20:07:16 linux 20:07:23 I'm not a BSD fan. 20:08:01 (well, I shouldn't say that, as I haven't taken the time to get to know BSD well) 20:08:19 their page says powerpc-apple-darwin works, but not powerpc-apple-linux. 20:08:23 Hmm... 20:09:13 --- join: doublec (~doublec@coretech.co.nz) joined #forth 20:09:27 * kc5tja nods 20:09:28 who's page? 20:09:42 GHC 20:09:50 Glasgow Haskell Compiler 20:09:52 slava, nice job on the cross compiler 20:09:57 darcs is written in Haskell 20:10:44 oh yeah, portage was funny about ghc 20:11:17 kc5tja: anyway, I'm not clear on what the emulator is supposed to do. 20:11:24 recent binary version is x86 only. 20:11:52 recent source version (apparently) works on ppc, but requires the binary version to be installed first 20:12:22 the run word in emu.fs opens an SDL window, but then appears to do nothing. 20:12:22 the older binary distro (which is compatible with ppc) satisfies the dependancy in the new source version 20:12:56 Herkamire: so you got ghc working on your machine? 20:13:08 no, I just figured out why it was getting confused 20:13:42 iirc emerge -pv ghc had the right idea 20:13:59 kc5tja: but I didn't really look at that, I pretty much stopped once I figured out the problem with asm-test.fs 20:14:05 but emerge -pv darcs couldn't get the dependancies for ghc straight 20:14:19 I don't think I tried installing it 20:14:22 OK, new release is up. 20:14:23 0.1.7 20:15:20 tathi: To get, say, color-test-2 running, you should launch "gforth color-test-2.ef", then type "reset run" at the OK prompt. 20:15:23 I had a similar problem with darcs on gentoo and ended up installing from source 20:15:31 That *should* (in a perfect world) get the window to display. 20:15:38 kc5tja: ah. I was missing the reset. 20:15:40 I'll try that. 20:16:31 dosbox looks fun 20:16:37 cool. 20:16:48 Note that keyboard input must go through the console window used to launch gforth -- it does NOT go through the SDL window yet. This will be fixed in the future; it's a crutch for laziness. :D 20:16:48 color-test-2 displays something, anyway. 20:17:15 Use Q, W, and E to *increase* the Red, Green, and Blue values. Use A, S, and D to decrease them. 20:17:20 And that's all it does. :D 20:17:24 Nothing spectacular. 20:17:48 And I have no idea how many frames per second your machine is displaying compared to mine. Your box is probably a LOT faster than mine. 20:18:19 no, actually, I had to turn the calibration value down. 20:18:34 It's NOT faster? 20:18:40 What CPU do you have? 20:18:41 4139 20:18:57 :( 20:19:01 Motorola 7410 (G4) at 533 MHz. 20:19:04 That sucks. :( 20:19:09 (well, two of them, but...) 20:19:14 What are you running it on? 20:19:14 Oh, the clock speed might be why. I'm at 800MHz here. 20:19:53 AMD Athlon @ 800MHz. 20:20:42 also I'm not sure what threading model it's using. 20:21:07 GForth you mean? I would think it's direct threaded, but I can't be sure without actually looking at how it was configured at build-time. 20:21:18 yeah. 20:21:33 I saw in the configure output that it had a couple of options, but don't remember which it decided to use. 20:22:03 by the time I finished hacking the configure script to get fflib working, I just let gentoo configure and build the thing. 20:22:36 Heheh :D 20:22:45 --- join: solar_angel (~jenni@Toronto-HSE-ppp3685160.sympatico.ca) joined #forth 20:23:43 Well, apparently gcc's "long long" didn't work on PPC in version 2.95.2, so the dope simply hardcoded it to emulate double cell numbers on PPC. 20:24:00 Whoops. That sucks. :( 20:24:06 Yeah, I compiled my GForth under GCC 3.x 20:24:12 yup. 20:24:16 I forget exactly what version. I think I have 3.1.2 or something like that. 20:24:23 But the emulation code doesn't work now, apparently. 20:24:27 Fortunately, I don't use 64-bit wide numbers. :D 20:24:45 Yeah, me neither, but the ffcall primitives wanted support for them. 20:25:16 Happy happy, joy joy! 20:26:10 Ah well, I got it working eventually. 20:26:48 I also had to tell it to load the pthread library, as that's not statically linked into my SDL 20:26:51 But that was pretty obvious. 20:27:27 gforth: relocation error: /usr/lib/libSDL.so: undefined symbol: pthread_mutexattr_init 20:27:33 Hehe :D 20:28:09 Hey, can I ask you a favor? Can you send me a quick e-mail of the steps you took to get the thing to compile? I'd like to post that on my website for those who use Macs with Linux. Maybe it'll be useful to those who run OS X too, I don't know. 20:28:13 But it can't hurt. 20:28:43 Yeah, sure. 20:40:20 Cool, thanks. 20:40:31 Sorry, I'm (ironically) trying to help someone get it working under OS X right now. :D 20:40:45 This includes compiling fflib and gforth from original sources. 20:40:52 Ah. 20:41:27 I just had gentoo build fflib, don't know what that's like. 20:41:49 As for gforth, I just removed two lines from configure.in and re-ran autoconf... 20:42:11 specifically these two: 20:42:13 #long long is broken on (at least) gcc-2.95.* for PPC 20:42:13 test x$ac_cv_sizeof_long_long = x && ac_cv_sizeof_long_long=0 20:42:55 If you can write that in an e-mail, that'd be most appreciative. 20:43:04 There's no way I will remember that here in IRC. 20:43:24 yup. 20:45:05 Now all you got to do is get Herkamire trying it out. :D 20:45:31 I'll probably ask for the instructions at some point 20:46:00 You don't know how greatly relieved I am to see that this thing runs under PowerPC. 20:46:09 :) 20:46:24 I honestly thought it would break in some obtuse, unknowable way. 20:46:34 Well, the colors aren't right :) 20:46:45 tathi: What do you mean? 20:46:46 my display is ARGB or something screwy like that. 20:46:49 Can you post a screen shot? 20:47:08 so color-test-2 gives blank blue green instead of rgb 20:47:10 tathi: I asked for a 256-color software-emulated surface. 20:47:16 Oh, huh. 20:47:49 tathi: OOOPS!!! I know the bug! 20:48:22 It's in the code that calls SDL_SetColors -- I build the table assuming little-endian numbers. Sorry. 20:48:33 I'll have to fix that in a bit. I'm going to grab some food first. 20:49:27 graphics bugs are so much more fun to fix than bugs that make it crash 20:49:35 Yeah 20:50:00 "Wohh, that's funky :)... ok now why's it doing that?" 20:50:11 :P 20:50:31 like when my mandebrot in herkforth was sideways :) 20:50:41 Well, hopefully, with few exceptions, after this graphics bug is fixed, all that remains will be the implementation of the Forth environment for the kestrel itself. 20:50:46 And that means mostly MachineForth coding. 20:50:53 http://qualdan.com/forth/color-test-2.png 20:51:03 yeah 20:51:58 Yeah, that looks like an endian-related color palette error. 20:53:45 I'll be right back. Off to the supermarket 20:54:25 progress -- cross compiler now produces a 260 byte image that computes 30 - 1. 20:54:38 or 30 pred where : pred 1 - ; is also cross-compiled into the image 20:58:51 slave, nice. 21:04:11 well, I now have 2swap, rot, -rot, and pick. 21:04:36 s/slave/slava 21:04:37 Do I add nip? 21:04:40 yes, but do you have rpick? 21:04:45 nip is useful. 21:04:47 i use nip a lot 21:04:53 it's just "swap drop" though 21:05:01 but depending on the architecture, sometimes it's worth defining 21:05:21 Actually, it's popw inc ,f fsr pushw 21:05:43 ick, which arch is that? 21:05:50 er, popw fsr ,f inc pushw 21:05:51 PIC 21:06:18 wait... which pic? 21:06:21 the 18f? 21:06:42 16f 21:07:05 oh. 21:07:48 okay, i'm officially confused... popw and pushw? 21:08:11 They're macros. If W is in TOS, they don't do anything. Else they do what they need to do. 21:08:22 oh, ok then. 21:08:59 OK, nip is added, and works. 21:09:57 gpsim is reasonably useful for testing this stuff. 21:11:01 why not just use mary? 21:12:34 2.5 Why not use Mary? Mary was a great inspiration source, I even kept some of the names from it. However, no code has been reused, as both Forth do not have the same goal. 21:12:49 ah 21:12:52 alrightie then. 21:12:52 I dunno. Because I started playing with PicForth before I head of it. 21:12:58 Gotta URL to mary? 21:13:23 http://mary.pepix.net/ 21:15:06 Jebus, the last active development was in 2000. 21:15:32 And it only supports the C61, C63 and F84. 21:16:10 that part is easy to fix 21:18:29 --- quit: solar_angel ("later.") 21:19:46 I think at this point, PicForth is a little more advanced. 21:19:59 And more importantly, it already supports the 16F877, which I have several tubes of. 21:23:42 There's something about Mary... 21:32:49 "The rules are important. The first part was written by normal people and makes sense. The other part was written by lawyers." 21:33:05 http://www.maddesigncontest.com/index.asp?distributors=5 NEC microcontroller contest 21:37:49 hello 21:38:01 kc5tja: got a question. 21:38:11 kc5tja: 0-60/400rpm -> 16 21:38:23 kc5tja: 0-60/5000rpm -> 18 21:38:25 wtf!? 21:42:02 arke: What? 21:42:14 Those numbers don't mean anything to me. 21:47:57 kc5tja: I meant that when I go 0-60, flooriung, in my car, and I shift at 4000rpm, i get there in 16 seconds 21:48:06 shifting at 5000 rpm takes 18 seconds though 21:48:44 --- quit: tathi ("bed") 21:48:50 arke: What is the red-line on your car? 21:48:54 0-60 in 16 seconds? What are you driving, a Geo Metro? 21:49:08 jc: Not much far off. 21:49:28 jc: It's a Dodge Colt Vista. 21:49:33 OMG 21:49:46 Family car, but hatch-back for extra space to store stuff. 21:49:51 Did you get that free when you bought a real car? 21:49:58 jc: Dude, chill. 21:50:04 hee 21:50:29 Do you remember when they were giving away a Yugo when you bought a Caddy, a few years ago? 21:50:35 jc: I'm sure if he were to drop an SRT-4 in the engine compartment, he'll smoke your butt.. :D 21:50:42 jc: No. 21:50:48 kc5tja: 6500 but I don't want to try to reach that. 21:51:11 He probably could. But I bet no matter what he drops in there, he can't tow a 7500lb load. 21:51:20 jc: and stop making fun of my car, my car wil smoke your car anyday. so STFU noob. 21:51:34 jc: I don't think a Colt Vista weighs that much, not with an 88HP engine stock. 21:51:58 kc5tja: website said 2.5k ounds 21:52:29 I've been meaning to buy an accelerometer and check the 0 to 60 on the cars. The quickest one is probably the RS 2.5, but it's not stellar. Somewhere in the 8's, I'm guessing. 21:53:00 arke: The reason earlier shifting reduces some time is because the car accelerates faster in higher gears. 21:53:18 What's an RS 2.5? 21:53:23 That's another number that means nothing to me. 21:53:31 Subaru Impreza. The low end of the RS 2.5/WRX/STi series. 21:53:36 Ah 21:53:48 * kc5tja gets around 8.9 to 9.2 seconds in my car. 21:54:01 1986 Mazda RX-7 GXL, 150HP engine, 3150lbs. 21:54:07 That's some go. 21:54:08 ...with a slipping clutch, AND AT ;) 21:54:16 Yeah, true. 21:54:25 But I doubt it'll go much faster than that once I get that fixed. 21:54:41 The car is specced only to go 0-60 in 9.1 seconds. 21:54:50 There's a lot of gearheads that have serious tweaked RX-7s. 21:54:53 I attribute faster speeds due to down-hills. :) 21:54:59 kc5tja: :) 21:55:03 jc: Mine is bone stock. 21:55:08 ok -- cross compiler is more or less functional. i can now compile a variety of simple words. 21:55:20 for example, the following image computes the 30th fibonacci number, my fav. benchmark :-) 21:55:21 [ 252579084 0 0 434 440 6 4 5 1 11 1 11 11 1 11 2 11 11 1 11 3 11 11 1 11 4 11 11 1 11 5 11 11 1 11 6 11 11 1 11 7 11 11 1 11 8 11 11 2 37 11 2 57 11 2 357 190 2 401 202 2 157 214 2 357 226 2 137 238 2 401 250 2 262 178 2 4 11 2 117 286 2 298 274 2 97 310 2 4 322 2 137 334 1 11 0 346 11 2 77 11 2 4 378 1 11 0 390 11 2 357 11 2 120 422 ] 21:55:22 bleh. I smoked a mustang in my moms car the other day. 21:55:22 My point more is that if you choose to tweak it, you have a lot of options. 21:55:32 he wasn't expecting it, so I just kinda ... well ... manually shifted ;) 21:55:50 jc: But if I wanted to, and had the cash, I could drop in a 13B-RE and get 180HP. Or, a 13B-REW and get 280HP. :) 21:56:16 arke: The Mustang driver wasn't trying very hard then. :) 21:56:54 slava, that's great progress 21:56:58 From '91 to '93 the roadmasters had the 350ci 180HP TBI engine. The '94 to '96 has an LT1 with a 260HP EFI LT-1 engine. I'm going to investigate the possibility of putting an Edlebrock or somesuch EFI system on it. Assuming it's not in the $2000 range. 21:57:40 Mine's a '93. TBI is just one of those unnatural ideas that GM came up with. 21:57:53 jc: Well, I could also tweak the 13B NA in my car to produce over 400HP, but that'd seriously cut the life of the engine. I'd rather just spend the money on a good 13B-REW. 21:58:45 And it'd make it street illegal too. :) It definitely won't pass smog. 21:59:07 I have a 'net friend who did a bunch of stuff to his. I don't remember the year, but I think his has a stock engine, also. I know he did the exhaust, and some other bolt on type things. I'll have to ask him what he finally got out of it. 21:59:43 On my car, if I swap the exhaust for free-flowing headers and remove the cats, I can get 190HP out of the engine. 21:59:44 I was looking at the 3 and 4 rotor designs when he was doing some of this stuff. Rotaries are damn neat. 22:00:03 But, then the car becomes totally loud and obnoxious, and rather smelly. Not my idea of cool. 22:00:13 Hell yes they are. :D 22:00:32 No, loud under normal operating conditions is not cool. Standing on it and having the pipes open up, that's OK. But basically, I hate loud vehicles. 22:00:35 Especially Harlyes. 22:00:40 Even if they do less work per intake charge, the geek factor is enormous. :D 22:01:00 jc: Well, rotaries are very quiet for their power output. 22:01:03 When I was younger, it took some real work to wrap my head around how the damn things even worked. 22:01:13 Compare an uncorked rotary to an uncorked LT1, and you'll see what I mean. 22:01:18 (and probably feel it too) 22:01:50 That whole center line gear thing will make you go nuts if you stare at it too long. 22:01:57 And I did drive the car with the free-flowing exhaust when I first looked at it. 22:02:08 Fun fun. And very quiet. 22:02:12 BUT, it wasn't street legal. 22:02:29 Center-line gear? 22:02:35 You mean the "stationary" gear in the rotary? 22:02:39 There are experimental aircraft people who use rotaries because of the power to weight ration, and it's very easy to couple the prop to the drive shaft. 22:03:03 Yea, that's it. stationary gear. I dont' remember what all the pieces are called, I can just visualize them. 22:03:05 doublec: get the latest jedit.org/factor/CFactor.zip if you want to look at it 22:03:20 I tried building my own simple rotary to see how that thing worked. You can't really appreciate it until you try to build a small model. 22:03:38 pictures? 22:04:00 I never took any, and it really wasn't worth keeping anyway. 22:04:03 It never ran very well. 22:04:21 I am planning on making another one though. This time, instead of foam core, I am thinking of using papier mache. 22:04:23 I guess the biggest problem with the rotaries, long term, is still the cylinder tip seals, right? 22:04:35 Apex seals. 22:04:41 And no, they aren't a problem anymore. 22:04:42 Yea, those. 22:04:52 They haven't been since the first-generation RX-7 came out. 22:05:13 The 2nd generation RX-7's rotary-related problems were all due to *water* seals on the *sides* of the rotors. 22:05:21 Huh. I thought they only recently, if at all, had materials that would really survive the high temperature and pressure, especially in the racing world. 22:05:45 3rd generation RX-7s have a slightly better design, but its problem is heat. They pack a 280HP engine in with twin sequential turbos, in a space smaller than any other car at the time. 22:05:58 jc: No, they've been solved for a long time. 22:06:17 The 13B RENESIS, however, is a return to the 12A build geometry. 22:06:20 I don't like turbos. I'll take a supercharger any day. 22:06:29 Turbos give WAY bigger boosts. 22:06:39 And they don't leech power from the shaft. 22:06:55 slava, thanks will do 22:07:08 Centrifugal (sp?) supers have solved that problem. And you don't have the bearing issues that crop up with turbos. 22:07:12 And considering the rotary's weak point is off-the-line, you'll never, ever see a supercharger on a rotary. 22:07:34 jc: Centrifugal supers still draw power from the shaft. 22:07:45 Yes, but it's very minor, compared to roots chargers. 22:07:48 Turbos employ waste heat to provide additional compression. 22:08:12 doublec: it needs the latest java code for the vector and bitwise ops 22:08:24 doublec: i'll fix the bug you found in the db and upload 0.60.2. 22:08:30 And unless you've got a really small impeller, you've got lag. Sorry, I've done some research, and at least for the V8 type engines, super chargers are THE way to go, in the last 2-3 years. 22:09:05 And they dont' require intercoolers. 22:09:17 jc: Well, consider a couple of things. First of all, a V8 isn't a rotary. A V8 has its greatest torque on the low-end. Second, you're still wasting incredible amounts of heat out the tail pope. 22:09:22 pipe even 22:09:51 The problem is that any of that heat that you couple back into the intake means a reduced air charge. Heat is not your friend. 22:10:00 A rotary's torque increases linearly with its RPM (up to the choke point). At low RPMs, a rotary really doesn't have that much power on the shaft. 22:10:01 ack. 22:10:12 jc: You're confusing things. 22:10:21 The *exhaust* heat is not coupled back into the intake charge. 22:10:43 Indicrectly, it most certainly is. 22:10:47 No. 22:10:51 Look at the P-V chart. 22:11:01 Maybe *some* of it is, but nowhere near the amount you are making it out to be. 22:11:04 When you have a glowing red turbo, it IS heating the intake air. In addition to the heat generated by the compression. 22:11:07 And if it is intercooled, it's effectively zero. 22:12:04 jc: If you have a glowing red turbo, you're also using it at boost levels far beyond normal engine operating parameters. So it doesn't matter if you compensate for volumetric losses with increased boost. 22:12:25 I have *never* seen a turbo, single or twin, parallel or sequential, glow red hot in normal (even street race) conditions. 22:12:28 Never. 22:12:54 And for what it's worth, the exhaust manifold of a rotary can go far beyond red hot. :) 22:13:02 Think *white*. :) 22:13:42 And that just goes to show you how much waste heat a rotary produces, and why a turbo is *vastly* superior for forced induction on a rotary. 22:14:34 I don't claim to know about turbos on rotaries, or what the power curve looks like, but I do know on conventional engines, there's a reason more and more manufactures are moving away from turbos and towards super chargers. And why if I put anything not normally aspirated on there, it ain't gonna be a turbo. 22:15:32 To each his own. 22:15:36 I would much rather have a turbo. 22:16:29 MazdaSpeed is finally considering a supercharged rotary for the RX-8, but the supercharger is NOT tied to the engine's drive shaft. 22:16:49 It's powered by an electric motor, and can therefore change speeds as the engine RPMs change to deliver best efficiency throughout its RPM range. 22:17:13 That's something I've been advocating for years now (it's about time someone picked up on it). 22:17:22 ;) 22:17:29 ack 22:17:34 mky fucking back is killing me 22:18:46 I wonder what the motor current looks like for an electric supercharger. 22:18:47 Considering the 13B RENESIS gives 240HP N/A (damn, I wish I had one -- it's basically a 12A engine that is double the power, and just as solidly built!), a supercharger that could be driven at turbocharger speeds would easily give that engine another 120HP easy. 22:19:31 oooh 22:19:34 i get it 22:19:51 now i know why pistons have low torque and rotaries high-end torque 22:20:08 One of the nice things about centrifugal SC's is that if they fail, they fail open. Unlike a roots style, which a lockup can cause your engine to suck the head gaskets into the cylinders. 22:20:31 rotaries have an almost constant momentum/inertia pull on them, due to its circular nature. 22:20:50 pistons lose more to inertia as their rpm gets higher 22:21:05 arke: Not quite. 22:21:17 arke: Pistons lose torque at high end because they can't breath very well. 22:21:38 Rotaries actually breath easier at higher speeds. 22:21:55 er... 22:22:07 well, aren't they both reasons? :) 22:22:26 Also, rotary geometry is such that the cold side of the engine stays cold (or, more accurately, coldER), and the ignition side of the engine stays warm. 22:22:51 In a piston engine, after the engine warms up, the cylinder is hot, which means it gets loss volumetric efficiency than a rotary 22:23:16 And depending on the engine, your valves don't always close as fast as you would like. The whole rocker mechanism is somewhat flawed. In fact, I wonder when they'll go to electric valves. 22:23:25 I wouldn't say inertia really has anything to do with the differences between the engine's torque figures. 22:24:08 well, as a piston moves up, it has more inertia/momentum, and thus it takes more to stop it and put it back into reverse. 22:24:28 arke: Hmm...that is true. I didn't think of that. 22:24:40 yay! :) 22:24:42 And a rotary also uses centripetal force to hold its apex seals against the rotor. 22:24:53 So at lower RPMs, a rotary actually has less compression than it does at high RPMs. 22:25:22 not to mention rotaries has less moveable parts 22:25:25 (proof: take an RX-7 cold, put it into neutral, and spin the engine shaft -- you'll find it will spin VERY readily.) 22:25:35 i guess the only reason they still make pistons is because of tradition ;) 22:26:19 And patents. 22:26:35 Well, the rotary is also demonstrably less fuel efficient than a piston engine OF TODAY. 22:26:53 I want to emphasize this, because back when rotaries were first introduced, they were actually more efficient. 22:27:10 its because they've optimized the SHIT out of pistons 22:27:13 Yep. 22:27:21 There is, I think, a lot of room for optimization on rotaries too. 22:27:30 But there is no market for it, and so, it'll never get done. 22:27:40 it will eventually. 22:27:41 ;) 22:27:47 jet engines use rotaries 22:27:58 I think making the engine seal tight as a plug at zero RPMs while still not scraping the rotor coatings off at high RPMs will produce a VASTLY higher fuel economy rotary. 22:28:18 I wonder how much the piston mass accounts for loss. Piston diameter is probably a bigger issue, because the contact area increases faster than the mass, so you probably lose more to friction than inertia. 22:28:30 arke: Well, jet engines are gas turbines. They are naturally rotary. And they are horrible in fuel economy -- NOTHING is sealed in those engines. :D 22:28:34 Well, not in the critical path at least. 22:29:10 i wonder why they don't CVT some of those planes. 22:29:11 jc: Inertia would be what kills high speed operation. 22:29:20 Also consider the connection rods and such too. 22:29:21 They're horrible in fuel economy under varying loads. They do very nicely for powering constant loads. 22:29:46 jc: They're not THAT bad under varying loads. 22:29:48 I'm not saying it's not a factor, I'm saying I wonder if friction losses account for more loss. 22:30:08 A recouperated gas turbine can get 22 to 25MPG back in the late 70s, which is comparable to a rotary. 22:30:20 (evidence: Chrysler's gas turbine car specs) 22:30:39 hrm. 22:30:52 whats teh difference between a turnine and a rotary and a piston? 22:31:03 http://www.velocityjrnl.com/jrnl/1958/vmd1210ov.html 22:31:25 slava, the Factor at jedit.org doesn't have 'vector'? 22:31:31 Well, I don't know, but here is one thing to consider. Double the engine speed, and it will take 4x the power to move that piston, and the con-rod. And every time you double the speed, you quadruple the amount of force that the con-rod has to withstand too. And remember too that intake ports on a cylinder are very small compared to what is possible on a rotary too. 22:31:46 doublec: yes i haven't uploaded the new one yet 22:31:55 doublec: i just thought you might want to see the cross compiler code :) 22:32:00 doublec: i'll upload when i fix the db bug you found. 22:32:47 slava, cool, I just thought I might have been doing something wrong. It all looks great btw 22:33:00 jc: Gotta love the wheel placement on that thing. I bet it doesn't do corners very well. :D 22:33:14 Likely not. 22:33:19 That being said, I enjoy making paper models of turbines. 22:33:26 Especially Tesla turbines. 22:33:28 I love 'em. 22:33:52 doublec: i want to go to sleep so i'll fix the db bug tomorrow. anyway i'm uploading 0.60.2 with the vector and bitwise words 22:34:06 slava, cool. thx. 22:34:14 doublec: its up. 22:34:20 doublec: you can try the cross compiler 22:34:29 doublec: first edit the image output path in cross-compiler-test.factor 22:34:40 doublec: then load cross-compiler.factor followed by cross-compiler-test.factor 22:34:47 and you can change the latter file to create a different image. 22:35:07 slava, cool thanks. go it. 22:35:12 slava, I mean, got it. 22:35:12 you can compile any words from the host factor into the target image that can be expressed using the primitives in the target image. 22:35:24 The last paper Tesla turbine I made had a quarter inch soda straw for air intake, and took compressed air via breath (e.g., I blew into the straw). It developed 500mW of power. By my calculations, across the circumference of the turbine, AND at the low RPMs it operated at, that paper turbine could easily have developed half a horse power. Then consider that, like all rotaries, it gets more power the faster it goes... There is no real telling wha 22:35:26 doublec: right now, the only primitives are drop dup swap + - call ifte <= 22:35:46 doublec: of course this will grow soon -- and the stack ops will become shuffle words not hand-coded primitives 22:35:52 You're using mIRC, aren't you? 22:36:02 jc: Me? no. I use irssi 22:36:09 * kc5tja is a Linux user, not Windows. 22:36:20 Ah. mIRC is famous for wacking lines. 22:36:38 Where did it chop off? 22:36:45 I didn't know irssi was guilty of that, too. xchat handles it responsibly. 22:36:47 Actually, sometimes it's the client that chops the lines too. 22:36:51 "telling wha" 22:36:59 Oh, you got everything then. 22:37:07 The last sentence was "There is no real telling what it could do." 22:37:48 You have an air compressor available? You could really fire that mother up at 100 PSI @ 18 CFM. 22:39:42 "Build a Tesla Turbine Engine (300 Hp) which is no bigger than a man?s hat. This engine can fit in the palm of your hand and can produce 300 Hp at 2,000 RPM?s! It is powered by air or compressed steam. This engine can be easy to build and geared down to power a home generator or a car or an electric car. We know that this can be an over unity Engine with as much free energy as you will ever need. " 22:39:45 I wish I did. 22:39:47 *snort* 22:40:27 jc: The quote is correct. The problem is, it misses the fact that you need a compressor, and some heat source to drive it with. These are common misconceptions of the Tesla turbine crowd. 22:40:41 And that obviously won't fit in a hat. :) 22:40:48 And it's over unity. 22:40:56 Another claim that is false is that it is over unity. 22:40:59 Darn you beat me to it. 22:41:16 A Tesla turbine, so far as I can tell, behaves exactly like a regular, bladed, radial turbine. 22:41:51 Did you find plans somewhere, or just reverse engineer it from diagrams? 22:41:53 Low-end torque suffers a bit (due to lack of impulse effect on the blades), but otherwise, is quite comparable. 22:41:59 Reverse engineered. 22:42:08 But the plans are available. 22:42:25 They're just stacks of discs separated by about 800um (approximately 1/20th of an inch). 22:42:35 --- quit: doublec ("Leaving") 22:42:35 (for air; wider for water, IIRC). 22:42:56 Oh, and Tesla's claim that they are self regulating is patently false too. 22:43:11 (Much of what Tesla claimed about them is false, despite the sheer ingenuity of the concept). 22:43:12 pwnage. 22:43:15 hrm. 22:43:29 you think I could build a turbine with things I find around the house? :) 22:43:32 * kc5tja would love to build a gokart around one, using compressed air as the source. 22:44:02 I wonder if CDs would work as the blades? 22:44:02 arke: I built my paper turbine to prove the concept couldn't work, and was shocked when it DID work. Since then, I've been using paper for all my turbines. 22:44:18 jc: Yes, but don't over-spin the CDs; they tend to rupture at high speeds. :) 22:44:26 heh, I've seen the photos. 22:44:56 kc5tja: !!! 22:45:08 kc5tja: can you send me some instructions or such? 22:45:10 * kc5tja has always been meaning to make an air compressor/blower using a Tesla pump too, so that I don't have to abuse my lungs to try new designs with. 22:46:17 :) 22:46:31 arke: I have some pictures that I took for that purpose, because you asked about it before. 22:47:01 But my batteries are dead in the camera. I have to get more batteries. It'll have to wait for a while until I can finish off all the rest of my more important debts first. 22:47:26 http://phoenixnavigation.com/ptbc/home.htm 22:48:21 * jc hits up 4 different Radio Shacks for the 'Battery every month' club. 22:48:34 http://phoenixnavigation.com/ptbc/toc.htm -- Click on "Samuel Falvo's Paper Turbine". that's my 500mW "Chicken and Broccoli" turbine. 22:48:52 http://phoenixnavigation.com/ptbc/articles/ptbc30.htm Hah! CD turbine. 22:49:44 However, the pictures of my C&B turbine were before I put it on ball bearings, which is when I did the power experiment. 22:51:45 hmm. 22:51:55 kc5tja: will you help me build one of those? :) 22:52:01 kc5tja: what sort of materials do I need? 22:52:07 i have cardboard and straws... 22:52:11 and lots of puter paper 22:52:23 stiff paper, like paperboard. 22:52:44 A compass for drawing out some circles, and an X-Acto knife (or something similar) for cutting out the exhaust ports. 22:53:08 it has to be stiff? 22:53:13 "_ 22:53:14 :) 22:53:17 So where's the exhaust port in the AOL CD turbine? 22:53:25 jc: Yes. Notice the holes around the hub. 22:53:27 I have that. 22:53:39 arke: Yes, it has to be stiff enough to hold its shape roughly. 22:53:48 Note that warpage is normal over time!! 22:53:49 I saw them, but they don't appear to go through, like the hub hole. Hmm. 22:53:51 kc5tja: any specific place I need to put them paper spacers 22:54:42 arke: in between the discs, preferably where they'll balance as much load as possible, and evenly spaced. Experience will tell you where these points are. It's hard to describe, and even harder to express in text. 22:55:23 kc5tja: hrm. I think I see what you mean. 22:56:35 Are ideal rotors as smooth as possible, or do modern rotors prefer to have a pattern or grooving on them? 22:56:54 The flatter, smoother, shinier, the better. 22:57:01 kc5tja: why can't one just glue the things together? :) 22:57:07 Which means paper SUCKS for this purpose. 22:57:15 Yet, it still works well enough to demonstrate with. 22:57:21 arke: ??? 22:57:32 arke: I do glue things together. I'm not understanding. 22:57:37 kc5tja: the discs. 22:57:47 kc5tja: why do you need the spaces? 22:57:51 They ARE glued together. 22:57:58 So the air can flow between the sheets. 22:58:31 arke: Take a spoon and dangle it under some running water. Note how the water follows the curvature of the spoon. 22:58:37 kc5tja: yeah 22:58:40 arke: It's that principle that we're trying to exploit. 22:58:57 And the more "spoons" you have, the more output torque you can have. 22:59:13 So the ideal rotor assembly should be extremely stiff, polished, as thin as possible (within the constraints of structural integrity), and as many as possible (given the intake port width) 22:59:35 You want each disc to be spaced just far apart enough to permit boundary-layer effect to happen but not to choke it. You also don't want them too far apart because then you get slip (like clutch slip). 22:59:40 with ~800um spacing. 23:00:08 jc: 800um spacing is for air. If you intend on using steam, liquid water, etc., the spacing will be different. Otherwise, yes. 23:00:48 And ideally, there would be no spacers, or they would be as close to the hub as possible. 23:00:54 1000mm = 1 um, right? 23:01:00 er, other way around 23:01:00 no. 23:01:04 1000mm == 1m 23:01:05 1000um = 1mm? 23:01:19 I know mm and up :) 23:01:24 that was a typo 23:02:20 arke: 1mm = 1000um 23:02:29 thats what I thought. 23:02:37 So I need to space them 'bout a mm apart 23:02:38 jc: Ideally, there would be no spacers since they do interfere with exhaust air flow, correct. 23:02:57 And yes, "real" turbines have spacers in the form of star washers that go around the hub. 23:03:02 1 or 2 pieces of computer paper should work, right? 23:03:20 You know, 1/16" kerf 12" circular saw blades would be about perfect, if you could remove the teeth. 23:03:26 I would like to point out that my spacers are compromises: they serve the purpose of the retainer rivets, but since I lack star washers in a paper design, I just double-dutied the spacers. 23:03:48 hrm. 23:03:53 Everything about my turbine design is a compromise. 23:03:56 Paper is a rough surface. 23:04:02 My spacers are woefully sub-optimal. 23:04:03 --- join: Klaw (~anonymous@ip68-228-92-218.oc.oc.cox.net) joined #forth 23:04:07 I could create one with purely computer paper then. And lots of glue. 23:04:09 There is no sealing between intake and exhaust. 23:04:16 It's made of paper. :) 23:04:17 etc. 23:04:24 :) 23:04:30 And yet, it still developed a very appreciable amount of power. 23:04:36 I was deeply impressed. 23:04:42 what are the semi circle holes for? 23:04:53 arke: Umm..exhaust? Air has to go somewhere, right? 23:05:02 ok. 23:05:15 except for the intake, I want tokinda seal around the disks, right? 23:05:46 Ideally, yes. Most real-world TTs have labyrinth seals to help keep air flow going through the turbine surfaces, rather than around them. 23:06:07 However, another approach is to just add more discs that aren't "wetted" with intake flow. So that any "overflow" spreads over into the other discs. 23:06:27 cool. 23:06:28 But this is sub-optimal in practice, because at low flow velocities, this results in some of your exhaust getting back-pumped into the intake. Sucky. 23:06:30 is that what you do? 23:06:40 Yes, I take the "more discs" approach because it's easy to implement. 23:06:45 Yet another compromise. :D 23:06:49 ;) 23:07:05 So as you can see, TTs can be optimized to hell and back too. 23:07:06 scissors, check. glue, check. Computer paper, check. circular object, check. 23:07:09 time to get to work :) 23:07:14 Heheh :D 23:07:28 kc5tja: when do you plan to go to bed? 23:07:48 BTW, 800um is *about* the width of three sheets of computer paper glued together. So each "spacer" should be about two to three sheets thick. 23:07:57 arke: Soon. I have to work tomorrow. 23:07:58 Why? 23:07:59 ok. 23:08:23 I mean, I love doing this stuff. 23:08:26 kc5tja: well, i was thinking I could buiild this really quick, and then have you help me ebug a bit :) 23:08:30 debug* 23:08:33 It is actually very relaxing to me to build model turbines. 23:08:34 I still fail to understand how the exhaust is effecively vented in the AOL CD design. 23:08:54 It seems it doesn't "drain" well. 23:09:24 It probably doesn't drain as well as it could. 23:09:45 But what happens is the air at the hub is still under some slight pressure. So it escapes through the holes. 23:09:47 Is the ideal exhaust port some number of degrees offset from the intake port? 23:10:26 jc: Ideally, the exhaust port would be completely circular around the hub, for the free-est (freest? freeest?) air flow possible. 23:10:45 Otherwise, it doesn't matter. The turbine will be spinning anyway. 23:10:54 In fact, it almost seems you'd want finger seals at 0 degrees and 180 degrees. You'd pump air in the top on one side, and exhaust at the bottom. The other side of the blades would be the opposite. 23:11:11 No. 23:11:20 Air comes in circumfrentially and tangentially. 23:11:31 It *spirals* towards the exhaust ports. 23:11:57 first sheet drying 23:12:04 Ah. So the ideal exhaust port is at the hub? 23:12:09 Correct. 23:12:37 BTW, these make great pumps too. Attach a motor to one of these things, and spin it up reasonably fast, and you'll feel some serious air flow. :) 23:12:40 I wonder what the ideal exhaust cutout size in the blade would be. 23:13:10 Empirical evidence suggests 1/3rd the area of the rotor surface area should be dedicated to exhaust for moderate sized turbines. 23:13:21 (moderate sized being between 4" and 10" in size) 23:13:24 That's quite a bit. 23:13:40 well, the smaller the exhaust, the more efficiency you gain because gas has more room to spiral. 23:13:43 That means removing most of the inner rotor area. 23:13:48 BUT, it's choked, so you won't necessarily get the horse poer. 23:14:02 Well, my turbine uses 1/3rd exhaust area rule. 23:14:08 And it's decently sized. 23:14:12 2nd sheet done. 23:14:21 arke: How many sheets are you planning on? 23:14:28 I'm guessing that each sheet should provide 2 disks and several spacers. 23:14:32 kc5tja: dunno. 23:14:41 Your exhaust cutout appears to be 1/3 the radius, but not 1/3 the area. 23:14:56 arke: I did eight, personally, just because it seemed like a good number at the time, and it fit the width of the straw well. 23:15:13 :) 23:15:17 maybe I should use stiff paper 23:15:22 and not glue CP together 23:15:25 oh well. 23:15:36 jc: It comes out to be 1/3rd the area as well. 23:16:06 4" rotor diameter, with a 1" hub size. 23:17:18 I don't think it's a general rule of thumb, but it happened to work out for that particular set of dimensions. 23:17:33 3rd sheet done 23:18:40 Looks like Teslas original design placed the exhaust port nominally 270 degrees out from the intake port, and used exterior exhasting. Not saying that's ideal, just that's how he built his engine. 23:19:25 4th sheet done. 23:19:37 I think I'll start creating disk layers now. 23:19:49 Yeah. He was into steam big-time back then, and loved to use external condensers on the exhaust port to induce huge vacuums. 23:20:06 That's likely how he got the 300HP out of a 9.75" rotor size. 23:20:22 Though, if a bladed turbine can get 1.5MW (yes, MW) out of a 14" diameter rotor size, I can easily see 300HP in a 9" rotor. :) 23:20:52 oooh nice 23:20:58 I can fit 3 disks on a sheet 23:22:11 :) 23:23:16 http://phoenixnavigation.com/ptbc/articles/ptbc12a.htm -- Here's a gas-powered Tesla turbine, though I know absolutely nothing about it, what kind of power he's getting, etc. But at least there are pictures. :) 23:23:26 (I love how the intake port is red hot too) 23:24:04 :) 23:24:16 wow, my friend is gonna love this 23:24:39 :) 23:25:10 got 3 discs cut out 23:28:10 It scares me to be around people like that. 23:28:39 like who? 23:28:40 I'm sure he knew what he was doing. 23:29:53 Anyway, I've often day-dreamed of building an HPV hovercraft too -- person pedals, spins a Tesla pump, and air from the pump is used to hover with. 23:30:09 :) 23:30:14 6 discs 23:30:28 Cool. 23:30:30 I'm gonna go with 9 discs 23:30:34 Well, I think I'm going to go to bed. 23:30:38 nooo! :) 23:30:40 Oh, trying to one-up me on the torque, eh? 23:30:51 :) 23:30:53 of course! 23:30:58 I am much l33t3r than you are! 23:31:00 any day! 23:31:01 ;) 23:31:16 See, now you're going to have to make me introduce the all new and improved PT-4, with 12 discs. :) 23:31:22 hovercrafts take a lot less power than I used to think 23:31:23 And two inlet straws, side by side. 23:31:31 grrr 23:31:33 Herkamire: ? 23:31:53 my cousins built one with a crappy lawn mower engine 23:32:05 arke: Actually, I did run some experiments with the PT-3, with two straws. Man, besides RAPIDLY exhausting your lung capacity, it sure spins that freakin' rotor up FAST. 23:32:08 Lots more torque. 23:32:17 :) 23:32:35 Herkamire: Even a crappy lawn mower engine is around 2HP to 4HP. Human legs is about 75W -- 1/10th HP. :) 23:32:48 (though it can get up to 1HP peak under certain circumstances) 23:33:08 that would be tough to get working 23:33:18 Herkamire: It's been done before. 23:33:33 I think less than a third of the area the fan blew went under for lift 23:33:39 cool :) 23:33:55 Herkamire: Really? 23:34:00 That doesn't seem like much... 23:34:12 I always believed that HCs were way more fuel economical than cars. 23:34:17 I wonder if that actually is true. 23:34:32 I always thought they were much less :) 23:34:49 We'd have to see. 23:35:16 I would love to play with one again 23:35:19 They might have worse economy at idle, but at "freeway", it could be better. 23:35:31 I got to ride my cousins'. 23:35:35 such a weird thing 23:35:53 What was it like? 23:35:59 8'x4' 23:36:01 I never ridden in an HC before. 23:36:02 one preson 23:36:13 9 discs. 23:36:17 the direction you lean made more difference than the way you stear 23:36:26 Now, I get to create the shaft hole, and stick my pencil through it. 23:36:35 arke: Right. 23:36:45 (stearing stick aimed two big louvers behind the fan that would direct the wind left or right 23:36:53 after that, I'm creating the stabilizers/spacers and gluing them on. 23:37:04 lean left and most of the air coming out from under will exit on the right 23:37:26 Herkamire: Right -- and Newtonian mechanics dictates that you'll move left accordingly. 23:37:53 it took a while to get it so you used the leaning and the stick together 23:38:07 it's soooo different than a wheeled vehicle 23:38:19 I'd like to ride one some day. 23:38:25 definitely 23:38:42 they said over and over that the hard part of building it was getting the stuff close to the fan 23:38:48 I mean, they can easily do things a normal car can't, like strafe. :) 23:39:03 :) 23:39:15 No more parallel parking issues! Just lean right and park. Done. 23:39:15 :) 23:39:18 but there's weird things too, like (in this one anyway) you can't stop the foreward thrust 23:39:43 to stop you spin around so you're going backwards and kill the engine when you stop 23:39:59 Right. 23:40:00 (unless you're on the water, in which case you just kill the engine) 23:40:22 Herkamire: cousin = tathi? 23:40:30 See, I'm not really into hovering over water personally. I'm more interested in terrestrial travel. 23:40:39 arke: yeah, and his 4 brothers 23:40:56 kc5tja: yeah, it was more fun on the parking lot 23:41:17 it's just that the river was a convienient wide open place where people don't mind us careening about 23:41:29 it was slower on water 23:43:09 * kc5tja nods 23:43:50 how come'? 23:43:59 See, if I were to make a vehicle, any kind of vehicle, I would make it so you could stop. 23:44:19 arke: Water is flexible. Some of the energy of the air flow goes into moving the water instead of moving you. 23:44:44 ok 23:44:53 Same basic reason why riding on partially inflated tires is slower than riding on fully inflated tires. :) 23:45:04 :) 23:46:57 ls 23:46:58 oops 23:47:04 yeah, bedtime for me I can see. 23:47:34 nooo ;) 23:47:45 Dude, I'm typing ls into an IRC window. 23:47:52 And I have to wake up in seven hours. 23:48:16 ;) 23:48:18 of course. 23:48:20 go to sleep. 23:48:26 I'll talk to you in 22 hours :) 23:48:26 --- join: zardon_ (~zardon@S0106000d6151238b.gv.shawcable.net) joined #forth 23:50:09 Hehhe 23:50:15 --- quit: kc5tja ("THX QSO ES 73 DE KC5TJA/6 CL ES QRT AR SK") 23:56:07 --- quit: zardon (Read error: 60 (Operation timed out)) 23:59:59 --- log: ended forth/04.06.24