00:00:00 --- log: started forth/02.09.25 00:22:35 --- join: Serg_Penguin (~Z@nat-ch1.nat.comex.ru) joined #forth 00:44:30 --- quit: Serg_Penguin () 01:08:30 --- join: Serg_Penguin (~Z@nat-ch1.nat.comex.ru) joined #forth 01:30:09 --- quit: Serg_Penguin (Read error: 104 (Connection reset by peer)) 01:31:54 --- join: LuckyPhil (~phowlett@CPE-203-45-248-201.qld.bigpond.net.au) joined #forth 01:33:20 --- quit: LuckyPhil (Client Quit) 02:15:01 Hrm. 03:28:18 --- join: Serg_Penguin (~Z@nat-ch1.nat.comex.ru) joined #forth 03:28:30 hi 03:43:01 zzzz. 03:44:56 --- join: LuckyPhil (~phowlett@CPE-203-45-248-201.qld.bigpond.net.au) joined #forth 03:45:09 hi LuckyPhil 03:45:16 Hello again Serg 03:45:24 i tryed enth yesterday 03:45:38 how did it go? 03:46:27 I've spent some time playing with Enth today as well 03:48:33 it would be much more usef00l ih have hdd/fat driver and be loada by LILO 03:48:45 i'll try today w/ lilo 03:49:05 but ide/fat driver is too much challenge for me 03:49:24 or maybe only block-wise IDE 03:50:11 but ist suxx 03:50:24 it suxx - blockwise 03:51:04 yes, hd would be nice. 03:51:22 why does it suck blockwise? I would thikn that it is rather eligant. 03:53:26 what is nicer to remember : e\dvl\frt\enth\src.asm or 'blocks 1234, 567-5689, 7813' ???? 03:54:36 you could assign a number to a variable, and reference the block there, but each to their own I suppose 03:55:59 and how much 'variables' will u need for OS like DOS ? like unix ? 03:56:34 u will probably store 'em in some block - but it's filesystem, very primitive ! 03:56:42 probably lots :) 03:56:51 and how will u interact w/ other world ? 03:57:19 if u downloaded kewl src and wanna try it in enth ? 03:57:23 it would be nice to have enth boot up and run from hd, but it is a little beyond me to change it to do that 03:57:51 you can use the same argument for other forths, like colorforth 03:58:16 just try to load it w/ some universal bootloader, i'll try LILO and WinXP's one 03:58:20 you can transfer blocks from one floppy to a file, and back again. its rather easy to do. rawrite can do it 03:59:57 if we make it boot from LILO and read/write fat32, we can call it an OS, cool ? 04:00:18 and, second, generating forth by ASM is no good 04:00:39 gcc can compile itself, why forth cannot ? 04:01:15 if one will have self-hosting forth OS, even 'OS' - it will be great 04:01:44 self-hosting = no need in other comp or OS to develop itself 04:03:14 enth is still early days, its not a fully blown os. 04:04:34 but one should 1) write nasm in forth ( enth ) 2) write forth in forth, not in asm 04:04:55 idling - dinner time.. brb 04:05:03 ok 04:05:14 just change nick to show it 04:05:21 --- nick: Serg_Penguin -> Serg_idle 04:05:28 --- nick: Serg_idle -> Serg_penguin 04:13:30 bank 04:13:33 back 04:15:05 --- quit: LuckyPhil () 04:19:36 --- quit: Serg_penguin (Read error: 104 (Connection reset by peer)) 04:30:38 --- join: Speuler (~l@p3EE2949F.dip.t-dialin.net) joined #forth 04:43:02 --- join: Serg_Penguin (~Z@nat-ch1.nat.comex.ru) joined #forth 04:43:09 re hi 04:44:24 g'd morning 04:44:51 hi 04:45:28 wht do u work on now ? 04:45:39 me ? 04:45:47 you :) 04:46:02 forth specific, or general ? 04:46:04 me - RU unicode decoder in gp-forth 04:46:07 both 04:46:41 forth: multi level marketing system administration program 04:47:27 yo-ho-ho ! i have the worst exoerience w/ MLM men, thunder and gallows ! 04:48:27 general: public display presentation system, setting up web/mail/stream hosting service 04:51:40 as a victim ? 04:52:50 i call it mlm because it most closely describes the cash flow 04:52:59 as a would-be member :( 04:53:12 but there are actually services 04:54:11 one can profit from it even without bringing new people in 04:55:42 ('m not the initiator, but the software modeller) 04:56:03 i think it's badly unfair ( or at least people adv'ed it to me are unfair ) and i dunno discuss it. period. 04:57:45 ok. this is mlm, but not a "get rich quickly"-scheme 04:59:49 what forth do u use ? 05:00:28 gforth for now 05:01:50 can it make standalone .exe ? 05:02:17 what's an .exe ? 05:02:53 some kind of windows jargon ? 05:23:56 executable file, binary code 05:34:41 --- join: cleverdra (julianf@0-1pool37-241.nas2.florence1.sc.us.da.qwest.net) joined #forth 05:43:30 z 05:48:17 ah. 05:48:54 don't know whether gforth does that for windows. for linux. it writes loadable images. 05:49:35 but i may just chmod the forth source, and have it executable that way 05:50:20 That's often best. 05:51:41 given compilation speed nowadays, there's hardly a disadvantage anymore to compiling during program start 05:52:25 given Forth compilation speed, particularly. 05:52:28 but it simplifies modification of the program 05:52:54 yes =) Cuts at least three steps out of a simple change. 05:53:41 * Speuler lazy too 05:54:26 well no. i avoid repetetive task. 05:55:12 just say 'lazy'; we know what you mean =) 05:55:15 sometimes, i run a "watch -n 1 forthprog" (on non-interaktive programs) 05:55:36 so it keeps restarting by itself 05:56:08 just save source, and the new version executes already 05:57:46 theory: you must be a lazy programmer to write compact code 05:58:10 motirically lazy :) 05:58:48 like, typing w/ one hand cause head rests on the other 05:59:23 ever tryed dvorak kbd layout ? 05:59:37 is it worth buying stickers ? 06:00:05 nope. but for one-hand typing, it seems suboptimal 06:00:32 you tend to move hand left-right-left-right 06:00:59 it has 3 variants - two, left and right hand 06:04:45 a cw pad (morse key), the ultimate one-hand keyboard ? 06:06:11 too slow 06:06:15 --- join: jacereda (~jacereda@VA1-1G-u-0041.mc.onolab.com) joined #forth 06:07:26 better: a few pads for _simultaneous pressing_ 06:07:55 --- join: tathi (~josh@wsip68-15-54-54.ri.ri.cox.net) joined #forth 06:08:10 --- join: Herkamire (~jason@wsip68-15-54-54.ri.ri.cox.net) joined #forth 06:08:28 but best ham operators outrun typycal programmers in chars per minute 06:09:11 that's because typical programmers suck :) 06:09:19 you mean in spelling out their handle, vs programmers' written code? 06:09:59 My bet is that most everyone who can type at all will beat a typical programmer in chars per minute -- if the programmer is programming. 06:10:18 heh 06:11:14 anyone who averages at least an hour a day on a computer should invest the time of learning to touch type in Dvorak. 06:15:00 -> cleverdra i mean beat at peak values, not average for hour 06:15:34 what is faster to type IMMEDIATE - kbd, cw autokey, multi-press pad ? 06:16:24 and what is faster to type : c@+ dup c@ swap 1+ ; ? 06:18:28 --- quit: Speuler (Read error: 60 (Operation timed out)) 06:34:53 z 06:39:35 Serg_Penguin: its not easy 2 b a "best ham operator", but its easy 2 b a reasonable "typical programmer" typing speed-wise 06:41:45 besides, after a certain speed, it's sort of like, "why bother?" 06:42:06 I've never felt like it was worth it to push my top speed past about 75wpm or so 06:42:13 and I only rarely type even that fast 06:44:07 yeah, with programming you don't need to be Really fast, but you should definately be able to touch type, and you should learn where the symbols are (that you use) 06:44:47 typing 90wpm is probably only usefull for writing documentation :) 06:45:04 (which we should definately DO) 06:45:27 Programmers should just start by becoming addicted to IRC and Muds and other games where typing speed is useful (such as the old Subspace, even) -- then, when they get around to programming, they'll have 100+WPM like me =) 06:47:12 dunno, seems like even on IRC and MUDs most people aren't very good typists 06:47:34 I recomend the discworld.imaginary.com :) excelent MUD 06:47:45 most people I've played MUDs with have lots of aliases and stuff, while I tend to type things out by hand 06:47:52 and I can _still_ do things faster than they can... 06:48:38 A programmatic mud-client with a VI-like interface is probably the best way to go, speed-wise. 06:51:05 --- join: LuckyPhil (~phowlett@CPE-203-45-248-201.qld.bigpond.net.au) joined #forth 06:51:29 Hello again 06:51:56 hello Lucky. 06:52:05 how about fun typing tutor programs like Mavis Baekon 06:52:38 s/Baekon/Beacon/ 06:52:53 In my freshman year of highschool, we had a mandatory keyboarding/word-processing course that involved Mavis Beacon. 06:54:03 I liked all the graphs you could get from that program 06:54:18 almost as good as Eudora's usage graphs :) 06:54:32 What kind of graphs? 06:56:07 how fast you typed each letter 06:56:11 --- quit: TreyB () 06:56:32 how often you got a letter wrong, what letter combinations you got wrong most... 06:56:45 version I used had graphs of how fast you were and how many errors by finger, by key, etc 06:57:14 recovery speed after making various errors... 06:57:36 --- part: LuckyPhil left #forth 07:05:24 * Herkamire decides to try gtypist 07:17:04 --- quit: Serg_Penguin (Read error: 104 (Connection reset by peer)) 07:29:55 --- join: Chef_ (~sam@m222.net81-65-249.noos.fr) joined #forth 07:32:47 --- join: TreyB (~trey@cpe-66-87-192-27.tx.sprintbbd.net) joined #forth 09:02:52 what about keycombinations like alt-tab? 09:03:09 who could u handle them w a morse key? 09:22:40 --- join: NoamTuring (xru52729fj@ip6-92.vancbc01g01.dialup.ca.telus.com) joined #forth 09:24:29 --- part: NoamTuring left #forth 10:17:45 --- join: I440r (~mark4@1Cust186.tnt2.bloomington.in.da.uu.net) joined #forth 10:24:49 Hey... 10:25:05 What are the permissions I give to the "allocate" word in IsForth? 10:25:20 * Robert will brb, food. 10:28:00 read write execute 10:28:11 actually tho if you give read perms you have execute perms 10:28:22 they are big flags 10:28:27 bit 0 is read i think 10:28:30 bit 1 is write 10:28:35 bit 2 is execute 10:28:43 i might have those mixed up tho heh 10:29:29 btw, the c header files in /usr/include/blah/foo/fud/... defines the flag values of 298467593784652389475629378465789234 different things 10:29:33 im not defining ANY 10:30:25 i usually just pass 7 for teh permissions BUT you might want to map a file with READ ONLY perms so... 10:34:25 --- quit: cleverdra (Read error: 110 (Connection timed out)) 10:35:35 --- join: cleverdra (julianf@0-1pool36-171.nas2.florence1.sc.us.da.qwest.net) joined #forth 10:41:35 I440r: OK. thanks. 11:14:34 how does a forth word have permissions?? 11:15:31 Hehe. 11:15:36 It's a memory allocation word. 11:15:49 And you have to set the permissions of the page you allocate. 11:16:03 ahh :) 11:16:30 I thought x86 didn't differentiate between readable and executable 11:16:56 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 11:18:47 isn't that how a ton of the security holes work? (you manage to get apache or some such to cache some of your data in memory, then when it crashes it sometimes branches to your data) 11:18:47 Hey! They're trash-talking FORTH in #osdev! Let's get them! 11:19:22 Herkamire: I think you can have read-only or read-write-only pages. Not sure. 11:19:32 Kitanin: Eat them. 11:20:18 --- join: lodda (~lodda@p508FCBCB.dip.t-dialin.net) joined #forth 11:20:19 hehe 11:20:29 ho lodda 11:20:32 just want to look if this chan exist... 11:20:38 * Kitanin isn't _that_ hungry... 11:21:22 I440r: does x86 really have seperate memory protection for reading and executing (ie can something be readable but not executable) 11:21:39 no 11:21:51 on an x86 if you have read perms you have execute perms 11:22:24 that's too bad 11:22:51 linux would be way more secure if they were seperate like on PPC 11:23:56 although you have to do a bit more to make self modifying programs work on PPC (set to executable, and flush the caches after you change it) 11:28:36 Herk: Nice understatement there. ``A bit more work''? :-) 11:29:52 I440r: Is that read-only? 11:30:02 heh 11:30:10 I440r: I remember having to set a page to +w before being able to execute code in it. 11:30:18 tathi :) 11:30:43 er 11:30:46 +x of course. 11:31:00 Hmm... or maybe that was to write to it. 11:31:04 +w will automatically be +x on x86 11:31:06 * Robert has a really bad memory. 11:31:15 Bleh. 11:31:24 Stupid x86 then :) 11:31:28 me too, i think i keep getting parity errors :) 11:31:39 * Robert pats his AVR with no memory protection at all. 11:32:26 isforth breaks the memory protection ruls of linux 11:32:35 i have code and data in the same memory 11:32:45 all isforths memory is read, write, execute 11:33:10 I had to write a linker script to get that on PPC :( 11:33:29 hehe 11:33:34 sys_mprotect :) 11:34:27 oh 11:34:44 I meant for the code/data that's in the binary, wanted that to load up rwx 11:35:16 oh isforths executable doesnt load up as r/w/x 11:35:37 i do a sys-break out to one meg then sys mprotect the whole fscking lot to r/w/x 11:35:50 ah, gotcha 11:36:44 im just reating linux as my bios 11:37:09 mischan 11:37:12 err, was that supposed to be to here? 11:37:40 no it was a mischan heh 11:38:36 --- quit: jacereda (Remote closed the connection) 11:42:35 Robert: Well, Chuck Moore dislikes ANS FORTH, at least. :-) 11:42:49 Heh, sure. 11:43:02 That's hell of a difference, tell the kiddies in #osdev that ;) 11:43:45 No thanks. They'll misquote me. :-) 11:44:32 so do i 11:44:34 chuck is right 11:44:37 ans is NOT forth 11:46:04 Some people can't get that Forth isn't a normal, standardized "language". 11:47:32 well, i understand that forth has no syntax, but i can't get the use of so much felxibility. when i have a problem i can't solve in C, i do it in asm. if i can't solve it in asm, i give up. 11:49:22 Hm. 11:49:44 forth is for people like us who can't stand a type-checking "patronizing C compiler that acts like your mother." :) 11:49:54 I first try in C, and if I make it, I implement it in Forth or assembly. 11:50:20 tathi: Amen... That's why we also enjoy assembly language :P 11:50:28 yup yup 11:51:17 Forth is just a game of bored programmers, who don't want really to program but want to show that they can do whatever they "want" IMHO (Robert is a good example) 11:54:19 www.forth.org 11:54:22 Check "Forth in space". 11:54:47 I doubt they just play with fancy space toys. 11:56:14 brb 11:56:19 --- quit: lodda ("leaving") 11:58:29 Robert: The problem with : bye recurse ; is that it's not actually _doing_ anything. :-) 11:59:39 Nevermind. I'd paused the display in #osdev. 12:00:27 :) 12:00:49 Crashing the Forth is doing something. Maybe less constructive than most other things :) 12:02:13 : bye [compile] recurse ; immediate 12:02:18 ' recurse alias bye 12:02:22 heh 12:02:47 0 constant 5 12:02:54 I440r: Ew. 12:03:17 lol 12:03:43 sure would mess with the newbies :) 12:04:35 It will screw the mind of anyone. 12:04:39 Hmm.. 12:04:42 Hrm... gforth is giving me a ``compile-only'' error on the second bit. 12:04:57 Let's play 1984. 12:05:02 : + 2drop 5 ; 12:05:05 2 2 + . 12:05:08 5 12:05:13 >:) 12:10:16 : ignorance postpone strength ; immediate 12:10:27 :-D 12:11:21 in like 1978 my dad showed me a forth dinensions that had a forth joke in it 12:11:28 it had a picture of a pub with a sign reading 12:11:30 do drop >in 12:11:33 21 < abort 12:11:53 even tho i didnt realy understand forth too well back then i understood the joke :) 12:12:04 nobody writes jokes in c:) 12:12:07 Heh. 12:12:15 i invented... 12:12:15 I440r: Then what's UNIX? 12:12:18 C is a part of the IRC jargon, dammit :P 12:12:20 Heh. 12:12:25 : sleep bed go tuck light off ; immediate 12:12:30 oopts you got me there :P 12:13:53 --- part: Kitanin left #forth 12:14:02 --- join: Kitanin (~clark@SCF61185.ab.hsia.telus.net) joined #forth 12:18:29 wb :) 13:03:48 I440r: Do you have any word for memory copying using assembly code in IsForth? 13:04:03 I440r: That's one task that _really_ shouldn't be done in high-level forth :P 13:04:12 Memory/string copying. 13:17:26 "move" ? 13:19:05 cmove 13:19:09 cmove> 13:19:17 its coded 13:20:30 --- quit: cleverdra ("Leaving") 13:21:08 * Robert checks. 13:21:39 its in memory.1 13:24:35 if your memory block is multiples of 4 bytes you can use dmove to move one dword at a time 13:25:03 dmove was made to move the contents of one variable into another variable 13:25:11 its like source @ destination ! 13:29:29 Yeah, I saw it. 13:29:48 Thankya. 13:30:02 : copy-string over c@ cmove ; 13:30:03 :) 13:30:31 doing a high level loop with dmoves might even be faster than cmove 13:30:54 Hrm... well, cmove is smaller :P 13:31:31 heh 13:31:54 cmove> allows you to move overlapping memory blocks 14:01:06 --- join: jacereda (~jacereda@VA1-1G-u-0041.mc.onolab.com) joined #forth 14:01:15 Hi jacereda. 14:01:19 hi 14:04:25 is the french guy from http://jpb.forth.free.fr/ around here? 14:07:48 Depends on who you mean. :) 14:08:01 Chef_ is from Paris, IIRC. 14:29:16 --- join: jamc (~user@as3-6-8.asp.s.bonet.se) joined #forth 14:35:50 hey, do you know which sort of cable did crowkiller use to connect to the gba? 14:48:29 Hejsan jamc :) 14:48:40 tjaba 14:48:41 jacereda: No idea. 14:56:12 --- join: tcn (tcn@tc4-login19.megatrondata.com) joined #forth 14:59:46 Good evening.. anyone here? 14:59:53 not me 14:59:56 im somewhere else 15:00:11 whussup :) 15:03:02 Back 15:03:14 Hi Robert, yup, I'm from Paris, hi I440r 15:03:15 wb :) 15:03:19 Chef_: hi! 15:03:25 Hi 1tom :) 15:03:32 anyone got any decent linked list words in forth ? 15:03:41 something simple 15:03:47 if not ill go code it heh 15:03:48 jacerada: I've never meet the author of jpbforth on this channel 15:04:03 I440r: just write it :) 15:04:17 I440r: decent linked list? You've got to be kidding, this is a one-liner :) 15:04:28 variable tail 15:04:56 :) 15:05:07 : add-to-list ( addr -- ) here swap , tail @ , tail ! ; 15:05:16 err no. you cant have a single variable holding the tail 15:05:25 because you can have MANY different linked lists 15:05:25 : do-something ( xt -- ) 15:05:28 Chef_: 0.14! jeeezuzs fkcin christ :D i can hardly keep u w ya, maaan 15:06:10 >r tail @ begin dup while dup @ r@ execute cell+ @ repeat r> 2drop ; 15:06:19 onetom :))) 15:06:26 chef u misunderstand 15:06:31 I440r: sure, just give an extra parameter 15:06:46 jacereda: neither i 15:06:50 onetom: :-) The new example "checker.fs" was fun to do, for a friend of mine 15:07:11 checker.fs ? 15:07:16 jacereda: just (fu)thin has found the link 2 his stuff & mentioned it here, but nothin else 15:07:16 a checkers game ? 15:07:18 In PicForth.fs 15:07:27 I440r: nope, something to check inputs :) 15:07:33 I440r: I may need a better name for this one :-) 15:07:42 oh heh 15:07:53 brb 15:08:05 nah - checker is good heh 15:08:06 Chef_: how long do u plan 2 hang around here 2night? 15:08:18 you could call it input-tester or something overly verbose like that :) 15:08:21 onetom: I never know in advance 15:08:30 onetom: maybe one minute, maybe ten hours 15:08:56 --- quit: tathi ("leaving") 15:10:38 I440r: ok, in 0.15 it will be renamed as "controller.fs", less ambiguous ;) 15:11:33 Enough PicForth for today, let's play with the bot now :) 15:13:13 --- quit: Herkamire ("mooooo") 15:13:52 Mmm... Has anyone already used COMPARE in Forth? 15:14:38 It does not do what I expect, so I do probably have wrong expectations. S" foo" 2DUP COMPARE holds false... 15:15:32 Oh... Forget it, found it, it's like strcmp() in C 15:19:23 chef_, you said something about the author of jpbforth? is he the guy who linked to the gba? 15:19:59 gba? 15:20:26 * Chef_ is happy, the bot "Forther" can reload itself and execute new code without disconnecting (Forth is great!) 15:20:57 S" is an abomination 15:21:11 i wont suppoort that sort of thing in isforth 15:21:17 s" xyzzy" interpret 15:21:18 ugh 15:21:27 (you mean "evaluate", not "interpret") 15:21:29 yea 15:21:33 In PicForth, s" stores in EEPROM 15:21:37 chef, did you said? jacerada: I've never meet the author of jpbforth on this channel 15:21:37 which is quite logical 15:21:44 anywhere you see 15:21:44 " 15:21:46 jacerada: yup, I did say that 15:21:51 s" lots of forth words in here" 15:21:57 you you should do 15:22:01 chef, what's jpbforth? 15:22:04 : foo lots of forth words in here ; 15:22:39 jacerada: a french Forth implementation. I thought you were looking for this guy 15:22:53 s" is on the same order of abomination as postpone :P 15:22:56 jacerada: you wrote: is the french guy from http://jpb.forth.free.fr/ around here? 15:22:57 chef_, ah, yes 15:23:02 jacerada :) 15:23:30 I440r: it depends, in my case, I love it (see the bot which can recompile and reexecute itself) 15:23:30 chef, the whole thing is incredible, that guy has put some effort there 15:24:02 jacerada: yup, and he is still active, I have subscribed to his mailing-list, and he is closely working with an engineering school in Switzerland for the Forth hardware 15:24:09 chef, but i would not like to modify his code :-) 15:24:45 * onetom is back & busy readin 0.14 15:24:59 (& having a dinner :) 15:25:29 onetom :) 15:29:11 --- quit: tcn () 15:29:11 i dont feel too good 15:29:18 i been playing hexen ii 15:29:25 and it always gives me motion sickness 15:29:25 quake and heretic never did 15:29:53 Don't play Metal Gear Solid II on PS2 then :) 15:30:22 lol 15:32:54 Chef_: http://novtan.bio.u-szeged.hu:8081/~root/picforth.html 15:33:11 Chef_: what about the look of the example code? 15:33:46 (page loading... slowly...) 15:33:51 Chef_: ive just put tag around the src 15:34:36 "The document contains no data" 15:34:42 I guess my browser is timeouting 15:34:50 Unable to read from socket: Connection reset by peer 15:34:56 k, forget it 15:34:59 "TCP connection to 'novtan.bio.u-szeged.hu:8081' failed: Connection reset by peer. " 15:35:04 Read error (Connection reset by peer) in headers. 15:35:11 Yup, idem with wget 15:35:32 onetom, you said it was thin the guy who linked to the gba? 15:37:01 onetom, ok, forget that sentence 15:37:25 onetom, i need some more coffee 15:38:00 "Kind of the hill" episode over, good book in progress, see you soon, I'm putting myself away 15:38:11 :) 15:38:12 * Chef_ is away: Yeah, I left that computer! 15:38:13 jacereda: no, he has just told us about that jpb... link 15:38:53 have you seen the code? 15:38:58 of jpb? 15:39:52 this guy is brilliant, but his code is... erm... different 15:40:42 browsed quickly... looked not very well factored 15:41:14 yes, that's what i mean 15:43:00 i can read much better his 68k than his forth 15:45:21 jamc: what r u talking about? 15:45:44 jamc: the picforth.fs? if so, i can agree :) 15:46:04 jamc: but despite of that ist a fabulous work! 15:46:36 i guess he means jpb 15:47:01 http://jpb.forth.free.fr/logiciels/ 15:47:12 that's what I meant, yeah 15:48:10 onetom, I haven't seen picforth.fs, but it is better factored. I bet you a beer 15:49:39 jacereda: better than what? 15:50:05 ah, got it 15:50:48 :) 15:50:55 take a look at the calculator or the xmodem 15:50:59 for instance 15:52:36 damn! the vt100 is even better! 15:54:36 wow! "6 pick" in http://jpb.forth.free.fr/logiciels/gif.txt 15:57:02 bah that was not surprising... "9 pick" in http://jpb.forth.free.fr/logiciels/coeur_forth/test_vga.txt and not a single stack comment 15:57:23 lol 15:57:23 lol 15:59:15 yaaayyy, it looks like crap @ 1st glance 15:59:42 * Kitanin feels the urge to hit jpb with a BLOCK... 16:00:04 but the guy is very productive judging for the page 16:00:18 1 could think it is optimized 4 speed, so there is a lot of unrolled things in, but no 16:00:41 its just simply a horror dream of a mad forther ;) 16:00:44 when he needs speed he resorts to asm 16:00:49 look at the square root 16:01:08 No. And you can't make me. :-) 16:01:08 yeah, ive checked the sources earlier 16:01:30 Kitanin: lollll 16:01:41