Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!wuarchive!udel!rochester!pt.cs.cmu.edu!dsl.pitt.edu!pitt!willett!ForthNet From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie) Newsgroups: comp.lang.forth Subject: Experimental Ideas Message-ID: <1970.UUL1.3#5129@willett.pgh.pa.us> Date: 8 Nov 90 04:13:20 GMT Organization: String, Scotch tape, and Paperclips. (in Pgh, PA) Lines: 43 Date: 10-19-90 (12:42) Number: 140 of 157 (Echo) To: ALL Refer#: NONE From: RON TOLER Read: HAS REPLIES Subj: CODE & PROC 3.2+ Status: PUBLIC MESSAGE Conf: FORTH (58) Read Type: GENERAL (+) I'm attempting to figure out some of the details involved with 3.2 + assembler codeing using CODE and PROC statements. All I seem to be able to do so far is to lock up my PC. I've used 3.1 assembler previously but only for short task CODE statements with all data on the stack and available to the CODE procedure. I could use some pointers on two things in the 3.2+ assembler. First: Calling PROC . PROC +TEST AX, # 0001 ADD BX, # 0000 ADC RETF END-PROC . VARIABLE TEST+ +TEST TEST+ ! . CODE ++TEST AX POP BX POP TEST+ CALLFI BX PUSH AX PUSH NEXT, END-CODE . This is my basic trial code in which I have been using as described in a comment form 9-12-89 in using CALLFI and RETF via a variable. Is there something majorly wrong or is there some syntax incorrect. Debugging is impossible when all variations on a theme lock up the PC. . The other thing is VARIABLE access via the CODE statements. Examples that I have also seem to access strange locations. Any help would be greatly appreciated. NET/Mail : LMI Forth Board, Los Angeles, CA (213) 306-3530 <<<>>> ----- This message came from GEnie via willett through a semi-automated process. Report problems to: dwp@willett.pgh.pa.us or uunet!willett!dwp