Path: utzoo!attcan!uunet!willett!ForthNet From: ForthNet@willett.UUCP (ForthNet articles from GEnie) Newsgroups: comp.lang.forth Subject: FPC forth????????? Message-ID: <643.UUL1.3#5129@willett.UUCP> Date: 12 Mar 90 04:01:12 GMT Organization: Latest link in the ForthNet chain. (Pgh, PA) Lines: 38 Date: 03-10-90 (13:55) Number: 1780 (Echo) To: ALL Refer#: NONE From: JIM BILDERBACK Read: (N/A) Subj: TECHNICAL HELP REQUEST Status: PUBLIC MESSAGE Hi folks .. hoping for FPC technical assistance . 1) regarding dis8086, I don't have a handle on the structure of forth and fpc yet but i'd like the disassembler to to show the variable / constant Name not location or value. Isn't it possible, given the location/value to somehow search the head space for a reference and thus tie in the name ?? if so can you give me some hints as to how to go about this ? speed is not an issue, i don't care if the entire head space has to be searched. 2) also on dis8086, can't a pause be built in if either the end of a definition is found (next, 1push, etc) or the another definition starts ?? I must confess that the dis8086 code looks like the finest of forth black magic to me, but i presume someone familiar with such things could offer a simple (?) solution. 3) It would be nice if the PASM and dis8086 supported V20 codes. I'm puttering with some video stuff which would benefit immensely. Certainly there are many more V20s around than 8087s , etc. and i presume testing for, and then vectoring to, an optional v20 word wouldn't take up much space, but would enhance graphics etc. considerably with the bit manipulation abilities, etc. 4) does anyone know how the stack is handled with the FPC compiler? is it like earlier .com versions of turnkey where you have to keep 64K for your application so you don't wipe out the stack area(s)? has anybody written a TSR module for the compiler? I'm trying but it is beyond my abilities, so far .. . So much for the novices .. all problems, no help. ANY HELP IS APPRECIATED .. jb ----- This message came from GEnie via willett through a semi-automated process. Report problems to: 'uunet!willett!dwp' or 'willett!dwp@gateway.sei.cmu.edu'