Path: utzoo!attcan!uunet!cadnetix.COM!cadnetix!rusty From: rusty@cadnetix.COM (Rusty) Newsgroups: comp.sys.ibm.pc Subject: Re: Re: Re: Keyboard "fix" TSRs Message-ID: <3135@cadnetix.COM> Date: 29 Jun 88 21:59:32 GMT References: <45919AHS@PSUVM> Sender: news@cadnetix.COM Reply-To: rusty@cadnetix.COM (Rusty) Organization: Cadnetix Corp., Boulder, CO Lines: 39 In a series of articles AHS%psuvm.bitnet@rutgers.edu and toma@tekgvs.TEK.COM (Tom Almy) have a 'discussion' (near flame-war) about Tom's code. Well, folks, welcome to Forth. Just about the only ways to pass things around in forth are 1) pass it on the (computation) stack 2) pass it following the 'call' to the routine (an example of this is the doconst, dovar, etc words used when making your own constants, as is thepair for compiling words, as well as ." (print a string)). I will NOT go into a remedial course on forth and TIL (or even Threaded compiled languages, if such a thing exists), suffice it to say that the structure of forth makes dissasembly somewhat less than helpful. Fortunately for those trying to look at Tom's code, a lot of the thread has been un-threaded. Otherwise you would see something like: L123: jmp (or, even better, a return) Data, routine1 data, routine2 ; or whatever your favorite assembler structure. data, routine3 routine1: data, routine2 data, routine1 data, routine8 data,routine3 routine2: Isn't TIL FUN? Rusty Carruth N7IKQ DOMAIN: rusty@cadnetix.com Cadnetix Corp. UUCP: cadnetix!rusty 5775 Flatiron Pkwy. {uunet,boulder,nbires}!cadnetix!rusty Boulder, CO 80301 (303) 444-8075