00:00:00 --- log: started forth/04.09.05 00:07:13 --- quit: Sonarman (Read error: 104 (Connection reset by peer)) 00:15:50 --- quit: Herkamire ("good niiight") 00:33:19 --- quit: kc5tja ("THX QSO ES 73 KC5TJA/6 CL ES QRT AR SK") 03:19:02 --- join: crc (crc@38-pool1.ras11.nynyc-t.alerondial.net) joined #forth 04:25:18 --- join: FlamingRain (Ecoder@c-24-129-95-254.se.client2.attbi.com) joined #forth 04:37:14 --- quit: FlamingRain (Read error: 104 (Connection reset by peer)) 04:37:25 --- join: FlamingRain (Ecoder@c-24-129-95-254.se.client2.attbi.com) joined #forth 04:39:03 --- quit: FlamingRain (Client Quit) 05:12:14 --- join: FlamingRain (Ecoder@c-24-129-95-254.se.client2.attbi.com) joined #forth 05:14:44 --- quit: crc ("Time for bed... Goodnight!") 05:15:48 --- join: Topaz (~top@spc1-horn1-6-0-cust117.cosh.broadband.ntl.com) joined #forth 06:59:21 --- quit: slava (Read error: 110 (Connection timed out)) 08:33:26 grr slava's gone and his server is down. lol 08:33:34 1: slava took his machine down 08:33:41 2: someone took slavas machine down 08:33:49 3: slavas machine took itself down 08:33:51 lol 08:38:41 --- quit: FlamingRain (Connection timed out) 09:02:32 --- join: kc5tja (~kc5tja@66-74-218-202.san.rr.com) joined #forth 09:02:33 --- mode: ChanServ set +o kc5tja 09:20:03 `hah i just had a primer go kerbanga on me while seating it lol 09:20:12 last 2 that went off just went perfizzle 09:20:20 this one went BANG in a big way! 09:49:23 grrr slava wake uo and bring your box back online man 09:49:24 doh! 11:26:33 --- join: cccr (wossname@HSE-MTL-ppp77358.qc.sympatico.ca) joined #forth 11:27:11 --- nick: cccr -> wossname 12:08:34 --- join: slava (~slava@CPE00096ba44261-CM000e5cdfda14.cpe.net.cable.rogers.com) joined #forth 12:10:59 ft slava lol 12:11:06 ft what happned to your server heh 12:12:51 --- quit: wossname ("what") 12:23:45 hi 12:23:52 I440r, its back up now 12:24:01 cool 12:24:05 i need to know something tho 12:24:19 but i cant remember the name of the equate 12:24:20 lol 12:24:41 the wha? 12:25:32 #define lol 12:25:38 erm hang on 12:26:09 TIOCGWINSZ 12:26:15 i think thats right 12:26:20 i need to know its valye 12:26:54 grep foo /usr/include/* 12:27:06 or find /usr/include -name \*.h -exec grep -l TIOCGWINSZ {} \; 12:27:07 it uses the _IOR macro 12:27:08 grr 12:28:30 that fscking macro does NOTHING except obfuscate the shit 12:29:09 i agree 12:29:31 write a C prog that prints its value 12:29:50 grr i hate that lol 12:29:54 im crap at c 12:30:03 how hard can it be 12:30:06 there has to be an easier way 12:30:06 #include 12:30:13 main() { printf("%d\n",TIOCGWINSZ); } 12:30:13 its not in stdio is it ? 12:30:20 #include 12:30:23 lol 12:32:13 sys/ttycom.h:#define 12:33:21 0x40087468 12:33:27 ok 12:33:34 you should've guessed that 12:33:39 lol 12:33:44 laughing rl here 12:34:16 i wonder how hard it would be to port your ncurses code to factor 12:34:34 oh btw 12:34:41 when i exit isforth, it doesn't reset the colors back to the default 12:34:44 ok. copy isforth out again 12:34:47 then extend 12:34:49 and ./isforth 12:35:32 yay it wokez 12:35:34 works* 12:35:35 woohoo!!!!!!!!!!!!!!!!!! 12:35:36 do this 12:35:43 ./isforth -fload src/examples/windwow.f 12:35:56 do THAT with ncurses :) 12:35:58 no such file 12:36:09 oh i'm writing -float 12:36:10 hehe 12:36:11 src/examples/window.f 12:36:21 ./isforth -fload src/examples/window.f 12:36:34 i think my terminal has bugs 12:36:38 let me try in console 12:36:53 use tab completion 12:37:22 its kinda messed up 12:37:36 make your terminal 100 by 36 and it isnt 12:37:43 lol 12:37:43 oh 12:37:53 i keep meaning to UN-hardcode taht 12:38:20 that some crazy 3d shit 12:38:31 3d ? 12:38:36 oh lol 12:38:37 yea 12:38:37 well how one window is in front then it goes behind 12:38:40 hehehe 12:38:42 the windows can be in front or behind 12:38:43 yeah, neat 12:39:13 now i'm going to type a command that begins with pkg_deinstall gf guess the rest of the line 12:39:32 hrm.... freebsd ??? :) 12:39:37 gforth :) 12:39:39 nah i might leave it there 12:39:44 but isforth will be the default :) 12:39:51 heh 12:39:55 can you fix the thing on exit tho 12:39:58 gforth can still do things i cant do yet 12:40:00 can it reset to previous colors in some ways? 12:40:09 resetting terminal to its default ? 12:40:21 i keep fergettin to do that too lol 12:40:29 look in src/terminal/* 12:41:02 actually, to do that ill need to add something to default 12:41:05 and to "atexit" 12:41:08 not a big deal 12:41:13 if i can figure out what lol 12:41:32 what is pluck? 12:41:40 copy third item to top 12:41:46 oh 12:41:48 i call that pick :) 12:42:03 err no 12:42:05 i don't have a pick ( n -- nth ) i think that's lame 12:42:07 wait lol 12:42:12 i have both pick AND pluck 12:42:18 i ferget which is which lol 12:43:02 i'm gonna be studying your ncurses code 12:43:06 it should be easy to port 12:43:33 i learned 99% of what i needed to know for that by reading the man page for term 12:43:41 oh really 12:43:52 there was only one thing i didnt get from the man page 12:44:00 so i got the termcap and terminfo book 12:44:17 that was to do with the translation thats required when you use the ibm box char stuff 12:46:22 took about 4 hours to code the initial run :) 12:46:32 many weeks to iron out the bugs tho and there are still some in there 12:46:38 try running isforth in a screen 12:46:47 im 50/50 as to weather thats an isforth bug or a screen bug 12:47:01 a LOT of apps break with screen 12:47:06 try running mc in screen 12:47:35 yea well i never use screen 12:48:23 i still have to fix the time shit 12:48:27 yea 12:48:41 which means i should parse timezone stuff 12:49:53 I use screen extensively. 12:50:01 I'm using it right now to yak on IRC, for example. 12:50:07 hi kc5tja 12:50:09 :) 12:50:16 Though, I have to admit, I have never, ever, ever, ever, ever, ever liked 'mc'. Ever. 12:50:23 i like mc 12:50:44 mc is just such an utterly *pale* imitation of a true dual-pane file manager, and frankly, it has actually never really worked for me. It doesn't at all map to how I think about file management. 12:51:04 RTFMing hasn't helped either. 12:51:19 I consider mc to be hostile and destructive to productivity as a result. For me at least. 12:54:57 man this is soooo freekin cool :) 12:55:07 isforth now runs 100% nativly under freebsd hehe 12:55:13 only ONE thing left to fix i think 12:55:20 thats a gettimeofday call 13:02:04 --- join: wossname (wossname@HSE-MTL-ppp66224.qc.sympatico.ca) joined #forth 13:02:32 what... no /proc/cpuinfo ??? lol 13:03:38 hehehe 13:03:42 you have to use syscalls 13:04:20 lol 13:04:25 how fast is your cpu 13:04:32 1.8ghz on the machine you're at 13:04:34 2.8ghz on mine 13:05:16 do a time ./extend 13:05:17 :) 13:05:30 0.131u 0.011s 0:00.16 87.5% 56+1348k 0+0io 0pf+0w 13:06:09 real 0m0.133s 13:06:09 user 0m0.117s 13:06:09 sys 0m0.014s 13:06:12 is what i got 14:00:01 --- join: tathi (~josh@pcp02123722pcs.milfrd01.pa.comcast.net) joined #forth 14:01:23 --- join: ADD-101 (XINU@12-222-128-22.client.insightBB.com) joined #forth 14:01:31 tathi did you have to modify gettimeofday ? 14:01:36 in the extensions i mean 14:01:44 thats the ONLY thing wrong with the freebsd version now 14:02:00 oh and ive no idea why my svn server is offline. i have to put a monitor on the damned thing 14:16:07 I440r: Because you're running LInux instead of FreeBSD. :) 14:16:34 --- join: randolm (wossname@HSE-MTL-ppp73481.qc.sympatico.ca) joined #forth 14:16:41 I440r: I haven't done anything to gettimeofday 14:18:05 tathi can you compile the extensions ? 14:18:09 prolly not 14:18:16 you didnt do fsave yet lol 14:18:18 fergot about that 14:19:13 hang on :) 14:19:35 im fixin my time stuff first then ill put the fbsd version where youc an get it 14:20:07 fsave works fine on PPC, I think. 14:20:37 tathi: You're running a PowerPC version of isForth? 14:20:50 kc5tja: I've been half-heartedly porting it. 14:20:58 I have it fairly close to working. 14:20:59 Ahh. :) Cool. 14:21:09 --- join: FlamingRain (~Ecoder@c-24-129-95-254.se.client2.attbi.com) joined #forth 14:21:10 * kc5tja will have to find someone to port FTS/Forth for Linux when it's done then. >:) 14:22:40 :) 14:23:22 heh 14:23:43 stop being half heared grrr :P 14:23:47 * I440r thwaps tathi 14:24:07 I was wondering if you were going to notice that :) 14:24:18 lol 14:25:36 Well, today is turning out to be significantly more busy than I would like. 14:25:57 I really do want to spend more time coding on FTS/Forth than solving st00p1d customer support issues. 14:30:46 --- quit: wossname (Connection timed out) 14:33:27 --- quit: randolm (Read error: 104 (Connection reset by peer)) 14:33:51 --- join: wossname (wossname@HSE-MTL-ppp73481.qc.sympatico.ca) joined #forth 14:34:55 slava your gettimeofday is always returning ZERO in the tv structure 14:35:03 0 tv 14:35:07 returns 0 == success 14:35:13 and tv has the result of ZERO 14:37:27 gettimeofday(): returns the number of seconds elapsed since the current time. Any value other than zero indicates severe space-time discongruities. Please contact your system administrator right away if this happens. 14:37:52 :) 14:42:14 nono number of seconds since the epoch 14:42:15 lol 14:42:27 and the syscall is working cuz it doesnt return an error 14:43:45 You missed the joke, I guess. 14:43:52 At least, I think. 14:44:30 --- quit: wossname ("mr. push up ;x;x") 14:46:54 no i saw it lol 14:46:57 i SAID lol 14:48:24 Whatever -- it's hard to tell on IRC. 14:49:36 --- quit: qFox ("meh ircii's netsplit detection appearantly sux ^^") 14:52:42 Let me completely re-iterate my utter and total hatred for Perl. 14:53:41 lol 14:54:38 How, in Perl, do I get the current date and time expressed as a string? Anyone know? 14:54:41 --- quit: FlamingRain ("Leaving") 15:05:09 --- quit: ADD-101 (Remote closed the connection) 15:05:21 Got it. 15:05:24 localtime(time()) 15:06:52 sup kc 15:07:06 thats about how you do it in C too 15:25:00 --- quit: tathi ("leaving") 15:30:03 --- quit: Topaz (burroughs.freenode.net irc.freenode.net) 15:30:03 --- quit: warpzero (burroughs.freenode.net irc.freenode.net) 15:30:03 --- quit: madwork (burroughs.freenode.net irc.freenode.net) 15:30:03 --- quit: madgarden (burroughs.freenode.net irc.freenode.net) 15:33:11 --- join: Topaz (~top@spc1-horn1-6-0-cust117.cosh.broadband.ntl.com) joined #forth 15:33:11 --- join: warpzero (~warpzero@dsl.103.mt.onewest.net) joined #forth 15:33:11 --- join: madwork (~madgarden@derby.metrics.com) joined #forth 15:33:11 --- join: madgarden (~madgarden@Toronto-HSE-ppp3707020.sympatico.ca) joined #forth 15:33:38 kc5tja, ping 15:39:13 slava 15:39:18 yes 15:39:25 gettimeofday works MUCH better when you use the correct syscall number 15:39:37 edit your src/ext/timer.f and change the 74 to 116 15:39:40 and run ./isforth 15:39:44 oh cool :) 15:39:47 the only thing wrong now is the timezone offset 15:44:25 syscalls have numbers? 15:45:08 lol 15:45:20 syscall 0 is sys_syscall 15:45:25 syscall 1 is exit ? 15:45:28 i wonder how you call syscalls from C 15:45:49 well thats what libc does hehe 15:45:58 well what if you don't want to use libc 15:46:09 what do you mean "what if" 15:46:10 lol 15:46:17 there is no reason not to use libc unless you're I440r 15:46:22 yeah there is 15:46:27 libc sux 15:46:29 nuff sed 15:46:30 :) 15:46:37 if you're writing something that isn't c 15:46:42 libc is a library for c 15:46:52 now i gotta go find out how to read timezone info grrr 15:46:58 warpzero, its just called that for historical reasons 15:47:01 warpzero, libc is the unix api 15:47:15 i'll api your unix 15:47:17 slava no. libc is the C library 15:47:20 how do you call syscalls from c 15:47:41 yes its also the unix api but unix people have their head up their ass. they ASSUME your going to do everytyhing with c 15:47:42 well, compare the effort I440r had to go through to port his forth to freebsd, with 'porting' something using libc ;-P 15:47:46 or with something that uses c 15:47:50 warpzero, inline asm 15:47:56 really 15:48:11 hey I440r 15:48:17 --- join: TheBlueWizard (TheBlueWiz@modem-066.nyc-tc03a.FCC.NET) joined #forth 15:48:17 --- mode: ChanServ set +o TheBlueWizard 15:48:34 how hard would it be to use everything from isforth EXCEPT the forth parts 15:48:46 like the syscall interfaces and library functions 15:49:07 i'm going to figure out how to do FFI 15:49:17 are there any decent wrapper libs or do i have to use dlopen() etc? 15:49:27 i want to get libX11 and libGL going 15:54:14 fuck 15:54:20 i need to get my language implemented 15:54:23 but 15:54:54 but what :0 15:54:57 if i want to implement it quickly i'd have to use c/glibc 15:55:07 nothing wrong with libc 15:55:11 don't listen to I440r :) 15:55:12 yeah there is 15:55:15 what? 15:55:21 its for c 15:55:33 that's a philosophical point 15:55:48 lisp implementations usually use it too 15:55:51 as does python 15:55:52 and perl 15:55:53 etc 15:56:06 this language needs go fast 15:56:15 what makes you think libc is slow? 15:56:18 its not a scripting language 15:56:26 do C programs go slow? 15:56:28 i mean assembly fast dude 15:56:39 you can generate all the asm you want in your compiler 15:56:52 calling libc's open() -vs- open syscall will save, what, 1 nanosecond? 15:56:55 yeah but i also need a significant RTE 15:57:00 what is RTE? 15:57:03 runtime environment? 15:57:06 yeah 15:57:14 well, look at the open source lisps 15:57:16 they use libc 15:57:25 but in sbcl and cmucl's case, the entire lisp is metacompiled 15:57:27 yeah 15:57:31 only the garbage collector is in C i think 15:57:35 the rest is in lisp 15:57:36 define metacompiled 15:57:37 and they're FAST 15:57:40 like all in lisp 15:57:45 and you use another native compiling lisp to bootstrap it 15:58:14 my language isn't self-bootstrapable 15:58:29 i'd implement it firstr 15:58:35 then worry about performance once you've identified the bottlenecks 15:58:41 premature optimization is the root of all evil 15:58:48 yeah you're probably right 15:59:14 ugh 15:59:19 this is going to be an implementation nightmare 16:00:44 you guys with your forths have it easy 16:01:08 slava whats the date and time there ? 16:01:14 > date 16:01:14 Sun Sep 5 19:00:14 EDT 2004 16:02:01 well okay slava ill do it in C/libc 16:02:03 grr why is it reporting sunday 6 sept 2004 23:00:33 16:02:10 but i'm in no way going to use autoconf 16:02:28 warpzero, me neither 16:02:57 warpzero, my C code compiles and runs WITHOUT #IFDEFS on linux, freebsd, sharp zaurus, solaris (64-bit mode), macos x, windows/cygwin... 16:03:05 warpzero, because I stick to sane, portable APIs 16:03:18 warpzero, without doing stupid tricks to increase performance by 5% at the expense of all other OSes 16:03:47 show me how to do that 16:03:54 read man pages 16:03:59 note the 'PORTABILITY' section :) 16:04:04 lol 16:04:05 if it says POSIX standard, you're all good :) 16:04:22 actually, i think my FFI will only work on freebsd, at the start anyway 16:04:50 okay hmm 16:04:58 slava thats not quite true 16:05:01 you- DO use ifdef's 16:05:08 in the heder files you include 16:05:16 I440r, yes but the headers are standard 16:05:20 i don't care what's in the headers 16:05:27 as long as they provide the handful of standard functions that I need 16:05:27 i suppose i should start with the parser 16:06:28 should i use a lex/yacc parser 16:06:39 --- join: FlamingRain (~Ecoder@c-24-129-95-254.se.client2.attbi.com) joined #forth 16:06:42 i wrote my own parser in the language itself 16:06:47 the C core doesn't parse anything 16:06:52 i can't do that? 16:06:54 it just loads an image, maps it into memory, and begins executing 16:06:58 ooh i think i know why this time and date are wrong 16:07:11 is the Linux epoch on a different date to the freebsd epoch ? 16:07:33 afaik no 16:07:37 but i could be wrong 16:08:17 slava: if i don't write a parser i won't be able to write a parser in the language either 16:08:30 argh 16:08:38 warpzero, hehe 16:08:38 isforth in linux is displaying it wrong too 16:08:50 warpzero, i wrote a java implementation first 16:08:58 EW 16:09:01 gross dude 16:09:02 warpzero, then 'meta-compiled' the first image for the C implementation 16:09:16 warpzero, now the C implementation is 'self-hosting' in a sense 16:09:21 i use quotes since the iamge doesn't contain machine code 16:09:23 but rather bytecode 16:09:27 why does my time calc think its sunday the SIXTH 16:09:33 yeah i have a bytecode too 16:09:42 doh 16:09:44 its actually nibble-width 16:09:48 warpzero, the java implementation was actually quite fast 16:09:56 warpzero, it would generate java bytecode,and the jvm would generate machien code from that 16:09:56 ew java 16:10:02 so in some cases it beats the C implementation in performance 16:10:17 only thing i don't like about java is the memory consumption 16:10:20 Lunch break. brb 16:10:23 but i have 512mb of ram *shrug* 16:10:51 i could just use a hex editor i guess 16:10:59 lol 16:11:38 kc5tja, what's a good way of doing FFI 16:11:39 slava can you take a look at src/ext/timer.f and tell me why im a day off ? 16:11:50 i mean day of the week is right but the day is off by 1 16:12:24 I440r, shit how would i know? 16:12:44 slava codes forth yes ??? 16:12:47 yes 16:12:49 but 16:12:54 well thers a bug in mine lol 16:12:58 its hard to tell what the problem is in your code 16:13:09 is 116 the right syscall #? 16:13:16 are you sure the claling convention matches libc's 16:13:36 yes and yes - the syscall is right now 16:13:44 well you're doing tv @ 16:13:49 you realize tv has two fields right :) 16:13:50 yup 16:13:54 yup 16:14:03 so you're ignoring tv_usec? 16:14:22 yes 16:14:33 i dont care about MICROSECONDS lol 16:14:41 do i ? 16:14:52 well i'm not sure if gettiemofday returns GMT or user's tz 16:15:29 gmt i believe 16:15:48 thats why the TZ (execept thats not used in fbsd) 16:15:53 its ignored 16:16:24 what is ':' 16:16:25 Sun, 06 Sep 2004 23:15:14 16:16:34 a character literal 16:16:43 oh 16:16:50 'x' is interpreted by number as being a number equal to the ascii code for x 16:16:59 it works with everything exceppt space 16:17:11 ' ' will return the code field address of the word tick :) 16:17:20 that's a bit messy :) 16:17:26 lol 16:17:31 u should be using bl anyway :P 16:17:40 ans forths use 'x 16:17:48 which is freekin fugly 16:17:49 i don't understand, does .elapsed print the current time? 16:17:51 what is stime? 16:17:54 no 16:17:57 do ./isforth 16:17:58 oh since timer-reset 16:18:00 yes 16:18:01 do timer-reset 16:18:03 right heeh 16:18:12 its similar to time foo from shell 16:18:20 timer-reset do-something .elapsed 16:18:27 yes 16:18:36 good for useless benchmarks :) hehe 16:19:52 what is your gettimeofday right now 16:19:56 3504694794 16:20:03 where ? 16:20:07 on a linux box 16:20:19 if its GMT and same epoch, they should be equal 16:20:28 time@ . gives 1094426473 16:20:29 oh that's milliseconds sorry 16:20:38 do time@ h. 16:20:46 413B9F81 16:20:50 hex is easier to read 16:21:10 413B9F2A 16:21:19 were close 16:21:28 so i say its MY bug 16:21:54 i just notiecd factor's usage of gettimeofday is wrong 16:22:45 ( 0 ) millis . 16:22:46 1094426564172 16:22:47 that's better 16:23:15 413b9fdb 16:23:19 this is C's gettimeofday 16:23:53 yup i say my syscall is working fine 16:24:00 but my date/time is fubar 16:24:05 which it didnt used to be 16:24:09 but why would it work on linux and not here 16:24:15 thats just it 16:24:22 its NOT working in linux either 16:24:24 i just checked 16:24:27 but it USED to 16:24:32 and its not failing because of an edit 16:24:43 but because of a fubar in the way i do the calculations 16:24:43 hehehe 16:24:51 that's why you should have a unit test suite 16:24:57 it was working 16:25:08 the unit test wouldnt have found a bug in working code 16:25:40 this was probably working right up until some date or other 16:25:48 and then the calculations became wrong 16:25:58 unit tests wont catch EVERYTHING 16:26:07 only time does :) 16:28:23 see http://en.wikipedia.org/wiki/Regression_testing for techniques used in debugging 16:29:19 back 16:29:59 I440r: Unit tests catch the functionality you want it to catch. If you express your requirements as verifiable, repeatable tests, then your unit tests will catch the bugs that make or break your code. 16:30:08 I've been doing it for years now. Don't tell me it doesn't work. 16:30:29 errr i NEVER EVER said it doesnt work 16:30:36 stop reading into my statements 16:30:42 stop interpreting. 16:30:44 I only read what your statements actually say. :) 16:30:49 i said it wouldnt catch everything 16:31:05 the unit test wouldnt have found a bug in working code 16:31:21 That last sentence doesn't make any sense. 16:31:31 If it's working code, it's by definition bug free, within some context. 16:31:37 the code WAS working 16:31:40 it was working perfectly 16:32:02 There you go then. 16:32:02 :) 16:32:14 unless your "unit test" can somehow guess exactly what would cause code to not work theres no way it can find this sort of bug 16:32:23 the code WAS working 16:32:27 its not been edited 16:32:32 now its not working 16:33:01 what unit would have told me my code was wrong way back when it was working perfectly 16:33:09 Then something changed and requirements were not adequately expressed as unit tests. 16:33:26 And you are correct: a higher level unit test cannot be expected to find nitty-gritty details. 16:33:33 That should be covered by lower leve unit tests. 16:33:44 sooo. a unit test boils down to your realizing everuthing that needs to be tested for 16:33:49 Once the low-level unit tests are all working, then by the laws of logical induction, you can depend on them to isolate bugs in higher-level code. 16:33:52 whose going to write unit tests for your unit tests ? 16:34:11 I440r: Dude, think for yourself man. 16:34:15 Don't even get me started on this. 16:34:19 Nobody writes tests for tests. 16:34:22 Nobody. 16:34:34 The test is, by definition, -- let me repeat this, BY DEFINITION, always correct. 16:34:47 If the test does turn out to express something incorrectly, then the requirement is misstated. 16:34:56 my point is "how do you know your tests will test for every possible failuer unless you test them" 16:34:58 Go back to the requirements, and make sure that they are adjusted accordingly. 16:35:23 so if everything passes your tests the tests are wrong 16:35:38 I440r: Go down to your local bookstore. Pick up a copy of "Test Driven Development." I am absolutely, positively not going to exhaust my time trying to explain the concept here. 16:35:41 Read for yourself. 16:35:53 I440r: What?! 16:35:56 im not saying it doesnt work. 16:36:21 im saying it cannot possibly catch every type of failure unless YOU know every possible failuer in advance 16:36:25 You are asking me hypothetical questions which (a) in practice are never an issue, and (b) are answered in that book, and (c) I've already answered them here, only to be re-asked the same questions over, in a slightly different guise. 16:36:27 an impossiblity 16:36:56 no. your twisting my arguement to suit yor own 16:36:58 your 16:37:02 Ummm......no. 16:37:06 We've had this argument before. 16:37:11 no 16:37:16 Whatever. 16:37:18 --- part: kc5tja left #forth 16:38:26 * TheBlueWizard sighs 16:39:55 show me the fucking unit test that will show me my fucking code is wrong 16:40:06 BACK when it was fucking working 16:40:39 unless you knew beforehand exactly why my code is wrong your fucking unit test wouldhnt find a fucking thing wrong with it 16:43:21 I am not going to respond because (a) I am not experienced in the (advanced) art of regression testing (and other intensive testing), and (b) your belligerent and often profane tone DOES turn me off, even if you prove to be right (and note the word "if"...totally hypothetical). I only try to contribute what I know of to here, is all. 16:45:00 I440r, unit tests don't catch all possible problems obviously 16:52:13 --- quit: FlamingRain ("Leaving") 17:00:57 --- quit: Topaz ("Leaving") 17:08:54 my arguement in full 17:09:06 kc5 simply interpreted that as "unit testing is useless" 17:09:13 thats HIS problem not mine 17:09:15 yes but they catch *some problems* 17:09:23 you cannot make a test for something you cannot anticipate 17:09:25 PREIOD 17:09:33 and you cannot anticipate everything 17:09:35 PREIOD 17:09:45 yes but that's doesn't excuse not having any tests at all 17:10:34 i didnt say i dont have any tests 17:10:43 unit testing isnt the alpha and the omega 17:10:51 i didn't say it was 17:11:20 i test my code to the umpteenth degree 17:11:41 i test for everything i can concieve as a possible problem 17:14:03 concieve of 17:14:05 even 17:24:46 --- join: tathi (~josh@pcp02123722pcs.milfrd01.pa.comcast.net) joined #forth 17:25:05 wb tathi 17:25:25 hi tathi 17:26:09 hi all 17:26:20 tathi hiya 17:26:39 had to take a break and figure out why my long division algorithm wasn't working. 17:26:50 TheBlueWizard hiya :) 17:27:11 tathi, arbitrary precision math? 17:27:55 no, just 64/32 bit 17:28:07 PPC doesn't have that in hardware. 17:28:22 bah that's easy :) 17:28:26 arbitrary precision is hard 17:28:29 And I'm porting IsForth, which needs it, so it can behave the same as on x86. 17:28:44 well, I'd never done it before. 17:29:07 and...if you just do a basic long division algorithm, I don't see that arbitrary precision would be any harder to write... 17:29:24 tathi your code can extend the 32 bit number to 64 bits and then do a 64 by 64 divide ? 17:30:12 tathi, getting good performance out of arbitrary precision is the hard part 17:30:21 I440r: err, 64 bit dividend, 32 bit divisor, giving 32 bit remainder and quotient. 17:30:31 slava: yeah. 17:30:31 yes 17:30:44 convert the 32 bit divisor into a 64 bit divisor 17:30:53 return 32 bits of remainder and quotient 17:31:25 slava: I didn't even begin to look at some of the algorithms for faster division when you get to more digits. 17:32:30 I440r: what? I thought x86 did edx:eax / ebx -> eax R edx 17:32:37 it does 17:32:52 so why convert to a 64-bit divisor? 17:32:55 but if you do a 64/64 and have a 64 rem and 64 qup 17:33:04 truncate the quo and rem to 32 :) 17:33:14 dont convert to. extend to! 17:33:21 so your not doing mixed precision 17:33:25 hey I440r can you teach me a few x86 instruction encodings 17:33:26 and then the code is slower 17:33:32 I don't see the point. 17:33:32 encodings? 17:33:34 hell no lol 17:33:41 I440r, damn i only wanted to know like 3 17:33:50 call 17:33:52 ret 17:33:53 tathi isnt it the mixed precision you were having problems with ? 17:33:54 wiat that's 2 17:33:59 oh and 17:34:04 call 17:34:04 slava look for ,call 17:34:12 I440r, in isforth? 17:34:14 dont know about indirect absolute 17:34:17 yes 17:34:21 wtf i thought you were dtc 17:34:21 its in compile.1 17:34:24 ok 17:34:28 i am direct threaded 17:34:30 I440r: PPC has a 32 / 32 -> 32 bit divide instruction. That's it. 17:34:36 Well, signed and unsigned. 17:34:44 I440r, i thought if you generate call call ret and such its STC 17:34:50 yes i know - so you have to hand code a 64 by whatever division routine 17:35:20 ok every single word in the dictionary has some machine code associated with it 17:35:33 for example the word + is ALL machine code... its a coded def 17:35:37 ok 17:35:41 a variable however starts with 17:35:43 call dovariable 17:35:58 the return address of that call is the body field address of the referenced variable!!! 17:36:08 colon definitions start with a call nest 17:36:08 ok 17:36:13 im direct threaded 17:36:39 the threading is to do with how NEXT works 17:36:49 lodsw jmp ax 17:36:51 is direct threaded 17:36:54 lodsw 17:36:56 jmp [ax] 17:36:58 is indirect 17:37:16 actually jmp [ax] doesnt exist i dont believe :) 17:37:23 lodsd jmp [eax] works tho 17:40:28 I440r, your ,call compiles a relative jump? 17:40:41 yes 17:40:46 not absolute. 17:40:49 thers no absolute jmp 17:40:54 ok 17:41:04 its relative to ip i presume :) 17:41:08 ya 17:41:19 ccomma and comma are c, and , :)? 17:41:21 relative to the address of the instruction FOLLOWING the jmp 17:41:28 yes 17:41:29 right 17:41:51 is dd a macro? 17:42:03 oh wait 17:42:04 no its a psudo opcode in the assembler 17:42:07 there's a forth version in the commets above 17:42:10 lol 17:42:22 right - some of those are wrong tho 17:42:27 i have to go over every single one of those 17:42:30 is the ,call one correct? it looks ok 17:42:32 so check :) 17:42:37 its correct 17:42:42 if my understanding of dd is right :) 17:43:06 dd assembles the next thing as a double word 17:43:08 32 bits 17:43:23 yes 17:43:30 i think people are fucked up calling a 32 bit item a word 17:43:34 yes 17:43:38 i call it a cell 17:43:39 does that make a 16 bit item a byte now ? 17:43:47 16 bits is a char 17:43:49 byte = char = 8 17:43:52 word = 16 17:43:53 unicode baby 17:43:54 unicode 17:43:57 dword = 32 17:43:59 lol 17:44:01 what is 64 17:44:03 ddword? 17:44:05 sentence? 17:44:05 quad 17:44:20 lol thats a 256 byte number 17:44:27 hehe 17:44:44 lol thats sharp humor man 17:44:50 some people wouldnt get that lol 17:45:15 its like i was listening to my blues station and the guyu was singing a song going "one and one is two, two and two is four..." 17:45:23 wtf 17:45:25 and im thinking err... no... one and one is ONE !!!! 17:45:33 if you're multiplyinh 17:45:50 ? 17:46:06 adding 17:46:11 1 + 1 = 2 17:46:16 one ANDED with 1 is 1 17:46:16 1 1 + . 2 ok 17:46:19 OH 17:46:21 damn 17:46:24 bitch 17:46:26 two ANDED with 2 is TWO!!! 17:46:29 lol 17:46:46 *snicker* 17:47:48 i can't remember why i wanted an indirect jump 17:47:52 i don't think its necessary 17:47:56 lol 17:48:02 what about ret? 17:48:05 * slava searches compiler.1 17:48:06 if you want an indirect jmp do 17:48:11 mov ebx, [eax] 17:48:14 yup 17:48:15 or erm 17:48:17 push [eax] 17:48:18 ret 17:48:22 i get the idea -- load it first ;) 17:48:24 thats how my "Execute" works 17:48:27 i know how *foo works in C i'm not that dumb :) 17:48:50 :) 17:49:07 do you ever compile ret? 17:49:16 no 17:49:18 or does your NEXT handle everything done by ret? 17:49:38 ret is used in a couple of places but its not used in the threading 17:49:52 oh wait, i remember what i needed now 17:49:56 call ; done 17:49:59 jmp 17:50:01 ret 17:50:18 is my understanding of x86 asm fucked or is call/jmp distinct? 17:50:46 in fact 17:50:48 i don't need ret 17:50:49 lol 17:50:55 call and jmp are identical except for one minor detai :) 17:51:02 call pushes the return addr :) 17:51:05 yes 17:51:11 do you compile jmp anywhere 17:51:48 hrm 17:51:49 no 17:51:52 i dont believe so 17:52:01 tho i DO assemble it (or nasm does :) 17:52:11 happen to know the encoding? :) 17:52:47 er newp 17:52:49 sorry heh 17:52:57 the nasm manual will tell ya 17:53:01 try pinfo nasm ? 17:53:10 wtf is pinfo 17:53:14 grr u only have info 17:53:17 pinfo is good 17:53:20 info sux 17:53:22 i use emacs to read info 17:53:25 pinfo is like way better 17:53:31 hmm, I remember not liking pinfo much :) 17:53:33 ill install it 17:53:44 lol 17:53:49 but then, I've gotten habituated to info, so... 17:54:07 info is like monotonic :/ 17:54:13 pinfo is in color!!! 17:54:15 hehe 17:54:19 and easier to navigate 17:54:28 color is for pussies :) real men use green on black and code machine code in hex :) 17:55:08 slava: E9 rel32 17:55:12 is jmp 17:55:16 a9 17:55:17 tathi, thanks 17:55:17 01 17:55:19 85 17:55:20 according to the Pentium manuals I have. 17:55:20 02 17:55:21 20 17:55:23 4c 17:55:24 00 17:55:31 thats lda #$01 17:55:35 sta $02 17:55:41 jsr $4c00 17:55:53 nice 17:56:05 i used to know every single 6502 opcode by heart 17:57:39 apple // forever 17:58:51 do you guys read grouphug.us 17:58:54 'About 2 years ago I started fantasizing about incest and beastiality and now I'm getting fucking grossed out by it so I'm working on stopping. Just not fantasizing about it. I'll get off to a movie with a hot celebrity in it or the guy I like or bondage. Just nothin gross anymore. I want to be different but not grossly so.' 17:59:50 its all fucked up shit that people write anonymously 17:59:59 lol 18:00:01 http://grouphug.us/confessions/934933945 18:00:10 like ive no intersete what so ever in that shit lol 18:00:18 i dont even read /. 18:00:28 http://grouphug.us/confessions/718839247 18:06:03 slava have you ever been to tahiti ? 18:06:13 no 18:06:24 ok :) 18:06:32 you? 18:06:35 closest is new zealand 18:09:48 no but i figured thats what your servers hostname is supposed to be :) 18:09:51 tawhiti hehe 18:10:06 no that's a word in maori 18:10:12 the lang of the nz natives 18:10:18 i'm not sure what it means 18:10:24 its my dad's computer 18:10:30 oh ok lol 18:10:36 i know who the maori are 18:10:39 painted face 18:10:41 my machine is claled 'emu' 18:10:43 fierce warriors 18:10:46 lol 18:10:50 yup 18:11:19 usually dance at rugby games lol 18:21:30 --- quit: tathi ("leaving") 18:24:09 mental note: dont pour powder into casing till you have inserted a primer 18:24:12 ! 18:24:18 wtf 18:24:27 what's this? 18:24:30 im hand loading 30-06 18:24:35 oh 18:24:36 hehehe 18:24:49 gotta go shoot some freebsd devs 18:24:57 this is for the messed up ioctls 18:25:02 this is for the bss requirement 18:25:30 if theres no primer in the primer pocket when you insert powerder the powder tends to flow OUT the flash hole :/ 18:25:32 lol 18:36:57 --- join: kc5tja (~kc5tja@66-74-218-202.san.rr.com) joined #forth 18:36:57 --- mode: ChanServ set +o kc5tja 18:37:32 kc5tja hiya again 18:37:36 re 18:38:49 kc5tja, in your opinion how important is unicode? 18:52:15 I do not have an opinion at this time. 18:52:47 I think it's a nice attempt, for sure. And I'd like to learn more about it at some point in the future. 18:53:06 However, all of my work is still 8-bit ASCII, since that is more than adequate to cover the written languages I intend on using. :)( 18:53:09 :) even 18:55:01 * kc5tja loves handing DDoS attacks . . . alone. 18:55:09 One earlier today literally took out the machine's network card. 18:55:40 NIC got fried? 18:56:03 NIC is fried, AND the computer refuses to boot now. 18:56:22 We think the NIC got too hot, and shorted something out, which rippled back to the northbridge chip of the computer. 18:56:25 wow 18:56:29 CPU still works fine -- we're using it in the new server. 19:01:45 --- join: FlamingRain (~Ecoder@c-24-129-95-254.se.client2.attbi.com) joined #forth 19:01:54 is FlamingRain a bot? 19:02:00 he/she/it joins and leaves and never speaks 19:02:13 As does ADD-101. 19:02:17 At least as far as I know. 19:02:17 oh no, its just a guy on like a dozen channels 19:02:24 [FlamingRain] #hprog #ypn #Math #lisp #forth #haskell #scheme #awk #javascript #php #perl #C++ #c #asm 19:02:46 nope 19:02:48 i am real 19:02:50 i come to lurk, i'm just now learning forth, don't have much to contribute and don't have any questions yet 19:02:54 FlamingRain, :) 19:03:00 didn't mean to offend 19:03:04 np 19:03:40 AACK! He's a bot gaining sentience! 19:03:41 ;D 19:03:52 i think add-101 is a bot but i knnow flaiming is real :) 19:06:53 gotta go...been stressful today...all bye! 19:07:44 Been futile all day for me. :( 19:07:54 * kc5tja can't get a handle on a single problem today. 19:07:55 Not a one. 19:08:11 Now I have to diagnose this strange MySQL/ASP problem which is really, really retarded. :( 19:11:42 :( there is no regular euphoria channel on freenode 19:11:53 euphoria the language? 19:11:55 * FlamingRain makes one 19:11:56 yeah 19:11:59 what is it like? 19:12:18 it's nice, it was my first language 19:12:25 what paradigm? 19:12:30 OOP? 19:12:40 only has 3 core data types: sequence (like a dynamic array), atom (floating-point), and integer 19:12:43 imperative 19:12:44 Isn't it functional? 19:12:52 * kc5tja heard of it, vaguely, once before. 19:12:52 Ahh. 19:13:13 Go BCPL -- only two types: 'word' and 'byte'. :) 19:13:21 Of course, Forth has those two, but I digress. :) 19:13:25 according to www.rapideuphoria.com, there is an Euphoria chat room, but I'm quite sure it isn't an IRC channel :) 19:13:28 FlamingRain, no structures? 19:13:29 i like the language simply because it was my first and it simplifies a lot of things, but, i've been moving on to other languages 19:13:41 i guess you can make structures from arrays. 19:13:44 thebluewizard: it's a malining list 19:13:53 ah...ok 19:14:00 slava: all structures you make are made from sequences 19:14:14 yes 19:14:46 i'm looking into forth now for the sole fact that it's so much different than most languages i've come across 19:15:07 Good idea. 19:15:09 i mean, there are some forth programs i've seen that are just downright sexy 19:15:11 * kc5tja really needs to get more into Lisp. 19:15:32 kc5tja, sbcl is a very high quality implementaiton 19:15:40 slava: free? 19:15:43 yes 19:15:50 its mostly written in lisp 19:15:57 meta-compiled, in some sense 19:16:09 generates native code on par with C if you have type declarations 19:16:23 off-topic: Anyone know anything about diagnosing a recurring problem between MySQL and an ASP website? 19:16:24 can anyone recommend a good forth compiler/interpreter/environment for linux? 19:16:32 (don't ask -- it's definitely NOT my preference...) 19:16:39 must go now...all bye! 19:16:44 FlamingRain, gforth, isforth 19:16:46 i've found a multitude of them, but, after reading through the specs, i can't really tell which i should try out 19:16:53 FlamingRain, there's many, yes 19:16:56 FlamingRain: gforth is awesome for learning Forth. It's relatively safe, and it's still fast enough to be of general use. 19:16:56 --- part: TheBlueWizard left #forth 19:17:06 kc5tja, what do you mean 'safe'? 19:17:14 its quite easy to crash gforth, eg 0 0 ! or something 19:17:30 slava: If you hose the dictionary or something, you can more or less limp it to a state where you can cleanly kill the program. Most of the time, at least. 19:17:40 It'll also detect most improper memory accesses. 19:18:09 has anybody seen that /. article about live perl programming for music generation in nightclubs? 19:18:23 i saw it but didn't read it 19:18:27 i don't really read much /. these days 19:18:36 they're very ignorant 19:18:43 i read through the article and it looked cool, but, i thought it was odd that they used perl for the task 19:19:02 linux is cool, bsd is not, perl/php/python/c++ is cool, lisp/java/forth is not... its very monoculture-like 19:19:38 slava: Well, that's hopefully going to change when I release FTS/Forth for L4. :) 19:19:47 hrmm, i don't understand that much, lisp/forth are very hackerish/obscure, which makes them almost directly cool in the realm of the geek 19:19:57 Lisp is hackerish? 19:20:03 very 19:20:10 I never considered it hackerish. 19:20:11 created by MIT for use on their first OS 19:20:14 It's rather anything but. 19:20:16 FlamingRain, the thing is they're not geeks or hackers they're 13 year old kids who think they're cool because they run apache and php or whatever 19:20:27 kc5tja, meaning, its easy to iteratively develop programs 19:20:31 ah, i see 19:20:35 you don't have to design up front, you gradually refactor your lisp code 19:21:08 i'm looking into a multitude of languages, including...well...basically every channel i'm in =p 19:21:21 slava: No, you can do that with Python too. Hackerish to me means that it encourages you to tweak the language itself. It openly invites so many different dialects of the language that a standard can't possibly evolve (think, Scheme). But yet, we have ANSI Common Lisp. :) 19:21:27 helps with problem-solving skills IMO 19:21:46 FlamingRain: Yes, learn as many languages as possible. :) 19:22:07 FlamingRain, i used to be a 100% java guy, then i learned lisp, prolog, forth and c, i think i'm a better programmer now :) 19:22:50 i've already got C and euphoria down, and i have dabbled in a ton of languages for different platforms, but the only other language i'm really fluent in is the Ti-Basic for my graphing calculator (hopefully i'm getting an hp48 soon so i can code in RPL instead) 19:23:01 slava, how is prolog? 19:23:25 its interesting, although i couldn't imagine actually using it for anything 19:24:07 from basic terminology, it's in the logical programming paradigm, which from my understanding means you describe what you want it to do and it figures out how to do it 19:24:16 but, i'm pretty sure i'm off by a bit there 19:24:17 well sort of 19:24:37 a simple prolog program: 19:24:45 parent(Bob,Joe); 19:24:49 parent(Bob,Jane); 19:25:02 sibling(X,Y) :- parent(Z,X), parent(Z,Y); 19:25:10 then you can type at the REPL: 19:25:14 sibling(Joe,Jane); 19:25:22 and it says Z = Bob, yes. 19:25:27 or sibling(Bob,Joe); 19:25:29 and it says no 19:25:41 you program with relations 19:25:50 a relation is either 'atomic' or its defiend in terms of other relations 19:25:56 i'm not sure if ; is the end of statement btw 19:25:57 maybe its . 19:26:02 yes its . :) 19:26:21 interesting 19:26:24 or another one; measuring the length of a list: 19:26:28 length([],1). 19:26:32 That's funny -- I remember writing something along those lines in C64 BASIC. 19:26:33 :) 19:26:40 lol 19:26:46 length([H|T],X) :- length(T,Y), X is Y+1. 19:27:14 here is how you read the code: 19:27:19 "the length of [] is always 1." 19:27:34 "the length of [H|T] is Y+1 where Y is the length of T." 19:28:05 looks kinda haskell-ish 19:28:06 you can then write at the prompt: 19:28:13 length([1,2,3],X). 19:28:14 and it says X=3 19:28:15 in the way it works at least, not syntactically 19:28:17 but you can also do: 19:28:21 length(L,2). 19:28:24 and it says [_,_] 19:28:27 where _ means 'anything' 19:28:39 whoa, that's cool 19:28:40 most prolog relations can be 'revrsed' in this way, it quite weird 19:28:55 any practical use for the reversal in most cases? 19:28:56 it doesn't always work though ; you have to know the execution model to understand when it does 19:29:08 i mean, desiging <=> relationships 19:29:24 its easy to write a parser in prolog 19:29:28 because of the automatic 'backtracking' 19:29:34 if some relation doesn't match, it goes back and tries another one 19:29:47 so you can code a parser in a form that looks sort of like the actual BNF spec of your source 19:30:16 neato 19:30:36 hrmm, any practical applications written in prolog that you know of? 19:31:08 nope 19:31:18 heh 19:31:35 woo, hurricane outside 19:31:36 its gaining popularity in web apps 19:31:42 they call it a 'rule engine' 19:31:57 Prolog has always been used as a rule engine for knowledge-based systems. 19:32:07 kc5tja, yes, but how its being hyped ;) 19:32:10 lik search engine cores? 19:32:11 s/how/now/ 19:32:13 like* 19:32:22 slava: It isn't. I haven't heard of Prolog in a long time. 19:32:49 kc5tja, its used in java circles. they embed a prolog interpreter in their java web apps 19:33:19 i never thought prolog was a compact enough system to do that with' 19:33:30 its a 'small' language 19:33:57 hrmmm 19:34:03 * FlamingRain is obviously ignorant 19:34:12 oh well, i can live with that for the most part 19:35:02 well, i'm off to eat hot-pockets and drink Mt.Dew and listen to music, later all 19:35:13 --- quit: FlamingRain ("Leaving") 19:45:41 Well, Hehehe :D 19:45:44 oops 19:45:45 :) 19:45:58 Well, I believe the core of the Prolog language is really simple. 19:46:05 And wasn't the first version of Prolog written in Lisp? 19:46:08 I can't recall. 19:55:30 Back in a bit -- facilities monitoring again. 20:50:21 ( 21 ) [ dup * ] compile-quot . 20:50:21 682893327 20:50:21 ( 22 ) 682893327 "sq" intern set-word-xt 20:50:21 ( 23 ) 5 sq . 20:50:21 25 20:50:42 that, boys and girls, is an x86 machine code version of 'sq' :) 20:50:47 CALL dup 20:50:49 JMP * 20:50:52 :) 20:51:00 Congrats. :) 20:51:12 i have to figure out how to push integers on the stack first 20:51:15 s/first/now/ 20:53:54 kc5tja, ping 20:54:02 kc5tja, if i want to use, say, eax for temporary storage, do i have to save/restore it? 20:58:32 What is it currently used for? 20:58:41 whatever C is using it for i guess 20:58:42 i have no control 20:58:54 C calls the compiled code blocks using function pointers 20:59:41 EAX is used as the lower 32-bits of the return value by C. So I guess it's OK to modify EAX without saving it first. 20:59:53 ok 20:59:56 thanks 20:59:58 I wouldn't make that assumption with any other register though, except for EDX, but even then, ONLY for functions that return 64-bit values. 21:00:24 for eg ebx i have to push/pop right? 21:03:05 Yes 21:03:30 I know GCC has "temp" registers, but on a machine so register starved as x86, I just save all registers except those absolutely necessary. 21:03:37 E.g., for functions that return void, I even push/pop EAX. :) 21:23:38 kc5tja, ping 21:23:43 pong 21:23:47 kc5tja, sorry for all these n00b asm questions, but what's the number for eax? 21:23:55 MOV reg32,imm32 ; o32 B8+r id 21:23:58 from the nasm manual. 21:24:10 is it 0? 21:24:16 The binary register ordering, from 0 to 7, is EAX, ECX, EDX, EBX, ESP, EBP, ESI, EDI. 21:24:28 ok thanks 21:24:30 i'm writing that down :) 21:24:49 or rather, defining words :) 21:25:53 --- join: AlonzoTG (~Baxter@207.140.211.88) joined #forth 21:26:04 om 21:26:28 to save you from the assembler language that is Forth, read my Sphere dox =) 21:26:36 http://users.erols.com/alangrimes/UCE/sphere.txt 21:26:41 http://users.erols.com/alangrimes/UCE/sphere.txt 21:26:41 http://users.erols.com/alangrimes/UCE/sphere.txt 21:26:42 http://users.erols.com/alangrimes/UCE/sphere.txt 21:26:42 http://users.erols.com/alangrimes/UCE/sphere.txt 21:26:42 http://users.erols.com/alangrimes/UCE/sphere.txt 21:26:58 --- mode: kc5tja set +b *!*Baxter@207.140.211.* 21:26:58 --- kick: AlonzoTG was kicked by kc5tja (Flood) 21:27:05 *sigh* 21:28:03 damn there's a bug in konqueror 21:28:10 after a while, #foo in links stops working. 21:28:13 this is SUCH a pain. 21:32:27 I don't even know what you're talking about. 21:32:28 :) 21:32:59 well, like foo.html#some_anchor 21:33:05 you click that link, and it just goes to the top of foo.html 21:33:09 even tho the anchor exists 21:33:18 Ahh 21:33:57 in gas, is this form of movl an actual instruction? 21:33:57 movl $5,(%eax) 21:34:32 or a macro? 21:35:07 oh i guess NASM calls it a store not a move. 21:37:41 That's a real instruction. 21:37:53 It moves the immediate value 5 into the memory address specified by EAX. 21:39:15 yes. i'm trying to find its encoding in the nasm manual. 21:44:05 MOV [EAX],5 21:44:14 I think that's what you're looking for? 21:44:21 yes 22:26:14 --- join: Serg_penguin (~z@212.34.52.140) joined #forth 22:26:20 hi Serg_penguin 22:27:55 hi 22:28:07 hi serg 22:28:57 hi ! 22:29:03 how's IsForth ? 22:29:14 going ok. got it running in freebsd L( 22:29:16 :) 22:29:26 and tathi has almost got it running in linux ppc 22:29:34 wow, nice ;)) 22:30:06 You know, it's when you answer yourself that you should start to worry. :) 22:30:16 * kc5tja is about ready to go home and get some sleep. Been at work all day. 22:30:47 kc5 you dont get a 3 day weekend ? 22:30:53 you were at work yesterday too 22:31:04 kc5tja, by the time you get home my compiler will be compiling simple words, contianing integer literals and calls to other primitives. 22:31:42 * I440r times slava 22:31:44 hehe 22:31:49 ready... set... GO!!! 22:32:13 * Serg_penguin thinks about DIFFERENT approach to writing FORTH 22:32:14 :) 22:32:31 just start to implement compiler 22:32:51 and implement any word what is needed by compiler, but _no_word_more_ 22:33:10 I440r, ping 22:33:19 I440r, does mov foo (%eax) take a relative address? 22:33:28 then compiler is ready, add nothing into kernel 22:33:29 in eax that is 22:33:47 all other words, even CORE - to add-on library 22:34:12 Serg_penguin: That's basically what I'm doing. 22:34:43 err u lost me 22:34:48 I440r, n/m 22:34:50 slava: That's not a proper assembly instruction. Are you referring to mov foo,(%eax)? 22:34:53 dont use evil at&t and i might understand heh 22:42:16 ( 13 ) [ 2 2 + ] compile-quot call-xt . 22:42:16 4 22:42:41 that's like, 3x faster than the interpreted 2 2 + :) 22:45:28 who wants to see the ugly-ass code that does this ;) 22:46:46 http://factor.sourceforge.net/compiler.html 22:47:51 compile-byte is like c, compile-cell is like , compile-offset is like here 22:48:00 i refuse to use c, , here since this isnt forth :) 22:48:09 and i already have a word 'here' used for a different purpose 22:49:07 --- quit: Serg_penguin () 23:00:07 Back 23:06:20 i'm very proud of my little compiler :) but now i must sleep. 23:06:33 Hehehe 23:06:51 * kc5tja is hoping to get some coding done on my Forth environment the next few days. 23:06:57 This is my last 3-day weekend for now. 23:06:57 tomorrow i'll be figuring out branches. 23:07:11 Starting monday, I'm going on graveyard shift. :( 23:08:03 Next monday, that is. 23:08:17 ouch 23:58:36 --- join: mur_ (~mur@mgw2.uiah.fi) joined #forth 23:59:59 --- log: ended forth/04.09.05