00:00:00 --- log: started forth/06.06.13 01:53:57 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-181-094.pools.arcor-ip.net) joined #forth 02:02:11 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 02:02:17 --- nick: snoopy_1711 -> Snoopy42 02:13:54 --- join: segher_ (n=segher@dslb-084-056-174-184.pools.arcor-ip.net) joined #forth 02:20:55 --- join: Intoxicator (n=l@159-134-144-72.as1.mvw.galway.eircom.net) joined #forth 02:21:58 --- quit: segher__ (Read error: 110 (Connection timed out)) 03:13:43 --- part: Intoxicator left #forth 05:28:46 --- join: timlarson_ (n=timlarso@65.116.199.19) joined #forth 05:38:02 --- join: PoppaVic (n=pete@0-1pool75-138.nas24.chicago4.il.us.da.qwest.net) joined #forth 05:50:21 --- join: madwork (n=foo@derby.metrics.com) joined #forth 06:16:49 --- join: timlarson____ (n=timlarso@65.116.199.19) joined #forth 06:17:45 --- quit: timlarson_ (Nick collision from services.) 06:18:19 --- join: timlarson_ (n=timlarso@65.116.199.19) joined #forth 06:18:25 --- quit: timlarson_ (Nick collision from services.) 06:18:36 --- nick: timlarson____ -> timlarson_ 06:19:01 --- join: timlarson____ (n=timlarso@65.116.199.19) joined #forth 06:21:54 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 07:23:52 --- join: snowrichard (n=richard@adsl-69-155-177-157.dsl.lgvwtx.swbell.net) joined #forth 07:24:51 hello 07:49:48 --- quit: madwork (Read error: 104 (Connection reset by peer)) 08:07:08 --- join: madwork (n=foo@derby.metrics.com) joined #forth 08:27:55 --- quit: snowrichard ("Leaving") 08:46:17 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #forth 09:25:39 --- quit: PoppaVic ("Pulls the pin...") 10:26:45 --- quit: tathi ("leaving") 12:01:46 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 12:32:51 --- quit: mikael (Remote closed the connection) 13:21:27 --- quit: Cheery ("Leaving") 13:27:04 --- quit: timlarson_ ("Leaving") 13:29:12 --- quit: timlarson____ (Read error: 104 (Connection reset by peer)) 14:25:39 --- join: joe_k (i=joe@adsl-65-67-81-98.dsl.ltrkar.swbell.net) joined #forth 14:48:50 --- join: I440r (n=mark4@24-177-235-246.dhcp.gnvl.sc.charter.com) joined #forth 14:52:42 ok who are hobart, joe_k nighty_ and ohub ? 14:52:44 :) 14:59:47 who am I? 15:01:32 good evening everyone 15:08:00 i dont know :) 15:08:26 your new to #forth since ive been in here 15:08:54 i am a person interested in forth 15:09:37 and even have a vm-based version of forth half-written for PIC16 ;) 15:11:32 cool 15:11:41 im thinking about writing a pic based forth :) 15:12:07 im the original founder of this channel but i dont onw it now. i never really managed it anyway :) 15:12:10 its everyones now 15:12:32 and i never pass up a chance to plug isforth.clss.net :) 15:16:11 im currently working on the debugger for isforth 15:17:57 hope you dont mind lurkers because i am about to lurk 15:18:04 heading home for the day ;) 15:18:12 lol i have a rule 15:18:23 lurking is fine 15:18:27 you can lurk and talk about ANY topic :) 15:18:44 #forth has traditionally NOT been anally retentive about these things 15:18:47 hmm, even C and Java? 15:18:49 heh 15:18:49 :) 15:19:03 remember. i DO own a gun :) 15:19:30 I know 15:19:44 I do too, though you're probably a better shot than I am 15:20:48 what gun do you own :) 15:21:15 my groupings have improved in the last year 15:22:53 and with a full mag i cah hit a 12 inch target with my 45 at 100 yards at least once :) 15:24:44 just a marlin 60SS .22 rifle 15:24:57 mostly for occasional fun at a nearby range 15:25:08 it has been a while since I last used it though :( 15:27:49 i have two 1911's, two model 1907 32 savages and an erma luger in .22 (all handguns) 15:28:17 plus an adl 700 in 30-06, a savage 111 in 270 and an ar-15 in 223 :) 15:47:19 --- quit: tathi ("running errors") 16:01:31 I440r: isforth for freebsd does not like my xterms... 16:07:55 erm 16:08:00 use eterm :) 16:08:07 what is $TERM set to 16:08:17 xterms work fine on the linux version 16:08:27 are you in an xterm inside a screen session? 16:08:32 isforth doesnt like screen 16:08:33 at all 16:25:15 $TERM="xterm" 16:25:21 ok 16:25:24 No screen session, just running under X11 16:25:31 where is your terminfo database 16:25:38 int should be in /etc/terminfo 16:27:01 I have /etc/termcap 16:27:06 no /etc/terminfo 16:27:17 theres your problem 16:27:21 do you have ncurses installed ? 16:28:01 yes 16:28:18 then bsd does it wrong :P 16:28:24 where is your terminfo database? 16:28:28 in /usr somewhere ? 16:29:51 --- join: nighty__ (n=nighty@sushi.rural-networks.com) joined #forth 16:30:19 --- quit: nighty_ (Read error: 104 (Connection reset by peer)) 16:30:37 in /usr/compat/linux/usr/share there is a terminfo directory 16:31:26 --- quit: I440r (Excess Flood) 16:32:09 --- join: I440r (n=mark4@24-177-235-246.dhcp.gnvl.sc.charter.com) joined #forth 16:32:34 doh. what did i say last ? 16:32:36 just that one... 16:32:40 in /usr somewhere ? 16:32:47 and I replied: 16:33:03 in /usr/compat/linux/usr/share there is a terminfo directory 16:33:14 then i said 16:33:25 make a link to it in /etc 16:33:42 so yo have a /etc/terminfo pointing to it 16:34:39 works now, thanks 16:35:06 :) 16:39:45 what u doing in isforth ? 16:39:49 anything interesting ? 16:40:44 i wonder what the average number of bacteria per c^3 there are in indoor air 16:40:50 err, cm^3 16:49:40 JasonWoof: answering your question above, Which forth... windows? The best description is from the book. 16:51:01 "The windows package I present here uses the f83 dialect of Forth developed by Laxen and Perry. The program is based aupon and inspired by the article titled " A Simple Window Package," by Edward Mitchell, 16:51:09 I440r: just increasing my library of forths 16:51:15 :) 16:52:03 ... which appeared in the January 1984 issue of Dr. Dobb's Journal. 16:52:29 JasonWoof: the actual code uses some 8088 assembly, some dos mem management, and BIOS. 16:52:43 to do windowing ? 16:52:45 Along with the forth of course. 16:52:53 Hi Mark. 16:52:58 hi 16:53:22 Ya, I was looking for some way to help with the Fowser project, and found a neat windowing system. 16:53:41 try isforth 16:53:50 I think, with some help, I can update this for gforth. 16:53:59 oh sorry, we've agreed to use gforth. 16:54:00 isforths windowing is pretty neat but probably not easy to use if your not familiar with it 16:54:07 gforth sux :P 16:54:09 I see. 16:54:10 lol 16:54:17 It would be good to study. 16:54:28 Where can I get a copy of isForth? 16:54:41 isforths windowing does the same as ncurses with optimized updates 16:54:43 isforth.clss.net 16:55:16 it only draws the changes and it blasts the entire display as a single string 16:59:06 if u wanna port the code to gforth you can do so :) 16:59:24 its in src/terminal 17:00:28 if u need ANY help understanding it u can email me 17:00:37 address is in the README 17:07:14 Thanks Mark. That should help alot in getting something going a little quicker. :) 17:18:58 ill be releasing the isforth debugger soon and it uses the windowing stuff 17:19:05 but u can try 17:19:21 ./isforth -fload src/examples/window.f 17:19:47 but that code isnt very well constructed 17:26:18 hi I440r 17:27:19 hi slava :) 17:27:25 what's up? 17:27:59 not much, trying to put the finishing touches on the isforth debugger :) 17:28:02 cool 17:28:07 what kind of debugger? does it single-step? 17:28:18 it single crashes at the moment lol 17:31:56 it has a memory watch window, displays of both stacks and will have breakpoints etc 17:32:09 cool 17:32:11 it will have fast run and auto stepping etc 17:32:28 you should have a stack display in the interactive interpreter too 17:32:36 .s 17:32:56 fpc had a thing where if you pushed both shift buttons it would do a drop down stack display from the status bar 17:32:56 I know, but like a status line thing 17:33:12 its possible :) 17:33:31 oh yea - the debugger will also have a separate screen for application code output!!! 17:33:49 as long as it doesnt modify emit that is 17:34:16 is it multithreaded? what if the user code hangs? 17:34:50 its not multi threaded - i cant figure out how to get signals working in isforth so i havent even started on threading :) 17:35:12 top of stack on entry into a signal handler IS NOT the return address 17:35:25 but ebp points to it, I would imagine 17:36:07 how so ? 17:36:15 isn't it a C stack frame? 17:36:20 there's a siginfo struct passed in 17:36:29 ooohhhh i wonder 17:38:55 whats the x86 opcode for a ret instruction ? 17:39:19 195 17:39:24 c3 hex 17:40:11 i'm debugging my GC 17:40:14 a recent change introduced a problem 17:48:33 --- join: ttuttle (n=tom@unaffiliated/ttuttle) joined #forth 17:48:38 Quartus: Hey. 17:48:43 Quartus: Global descriptor tables are annoying., 17:49:23 slava ok i cant figure how to exit from a signal handler in isforth :P 17:50:03 I440r: reboot? 17:50:47 eh ? 17:50:51 I440r: I dunno. 17:50:57 no im trying to figure how to get signal handlers in isforth 17:51:01 my forth compiler for linux 17:51:11 I440r: What are you writing it in? 17:51:16 the handler runs but i cant figure how to exit 17:51:17 in forth 17:51:22 I440r: Okay. 17:51:28 I440r: Exit the program or the handler? 17:51:35 the handler 17:51:45 ive NO idea where the return address is 17:51:49 sp doesnt point to it 17:51:58 erm esp i mean 17:52:02 and ebp doesnt seem to either 17:52:28 I440r: Did you pop off the argument (signal number) to the signal handler first before checking for the return address? 17:52:57 erm 17:53:18 I440r: When a signal occurs, isn't there one argument to the signal handler routine? The number of the signal? 17:53:18 doesnt help 17:53:21 I440r: ok 17:53:44 I440r: sorry 17:54:23 2 48 syscall 17:54:23 create doret -5 allot $c3 c, 17:54:23 : winch 2r> 2drop ." we got a winch" cr r> dup doret ; 17:54:23 ' winch 28 17:54:23 : blah ." blah" cr begin key? until key drop ; 17:54:46 thats my code 17:55:01 i get the winch but it segfaults no matter how i try to exit 18:04:45 --- quit: ttuttle ("Lost terminal") 18:29:05 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 18:52:19 --- quit: uiuiuiu (Remote closed the connection) 18:52:23 --- join: uiuiuiu (i=ian@dslb-084-056-225-236.pools.arcor-ip.net) joined #forth 19:31:39 --- join: ttuttle (n=tom@unaffiliated/ttuttle) joined #forth 19:31:46 Quartus: Hey, I got a problem with my assembly program. 19:32:26 Quartus: The C part of it calls an assembly routine to install a new GDT. But when that function tries to return to the C function, the stack segment is fubared, and it hangs. 19:49:37 --- quit: I440r ("Leaving") 19:59:42 --- quit: ttuttle ("leaving") 20:02:03 --- quit: tathi ("and now to sleep") 20:56:07 --- quit: virl (Remote closed the connection) 23:59:59 --- log: ended forth/06.06.13