Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!willett!ForthNet
From: ForthNet@willett.UUCP (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: LMI Forth(s)
Message-ID: <272.UUL1.3#5129@willett.UUCP>
Date: 17 Jan 90 00:52:29 GMT
Organization: Latest Link in ForthNet Chain (Pittsburgh, PA)
Lines: 27


 Date: 01-16-90 (10:02)              Number: 280
   To: RAY DUNCAN                    Refer#: NONE
 From: YVES LAFOND                     Read: 01-16-90 (21:06)
 Subj: COMMENT                       Status: PUBLIC MESSAGE

 TECHNICAL SUPPORT DEMAND TO RICHARD WILTON OR ANYONE ABLE TO ANSWER!
 FROM YVES LAFOND & DENIS LAMBERT, COLLEGE OF SHERBROOKE, QC, CANADA
 WE HAVE PC/FORTH 3.2 (SERIAL 6088) AND FORTH METACOMPILER (SERIAL 470)
 PC/FORTH HAS 1 ANNOYING BEHAVIOUR: IF ANY ERROR OCCURS WHILE USING THE
 INTERPRETER, IT COMES BACK WITH DATA STACK POINTER AT THE ORIGIN, ETC.
 IT IS QUITE IRRITATING, ESPECIALLY WHILE WE ARE USING THE MULTITASK!
 WE MUST (IN FACT OUR STUDENTS!) START ALL THE TASKS ALL OVER AGAIN; AND\
 SINCE THEY'RE STUDENTS, ERRORS OCCUR QUITE OFTEN...
 HOW CAN WE CHANGE THIS BEHAVIOUR? CONSULTING THE METACOMPILER FORTH
 SOURCE CODE, ON SCREEN 65 AND 76, WE NOTICE THAT "QUIT" AND "ABORT" 
 DO A RE-INITIALIZATION OF THE STACK POINTERS. WOULD MODIFICATIONS TO 
 THOSE WORDS BE SUFFICIENT? HOW COULD WE CHANGE THAT SPECIFIC BEHAVIOUR
 OF THE ERROR HANDLING ROUTINE? WE ARE WAITING FOR AN ANSWER!
 YOURS TRULY, YVES LAFOND AND DENIS LAMBERT.
 P.S. WE WILL PHONE BACK IN A FEW DAYS TO CHECK IF ANY ANSWER IS 
 AVAILABLE.

 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: 'uunet!willett!dwp' or 'willett!dwp@gateway.sei.cmu.edu'