Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!willett!ForthNet
From: ForthNet@willett.UUCP (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: FPC forth?????????
Message-ID: <494.UUL1.3#5129@willett.UUCP>
Date: 18 Feb 90 23:41:40 GMT
Organization: Latest link in the ForthNet chain.  (Pgh, PA)
Lines: 56


 Date: 02-17-90 (08:14)              Number: 1752 (Echo)
   To: ALL                           Refer#: NONE
 From: DAVID BOYD                      Read: (N/A)
 Subj: FPC 3.50 and FSTRINGS         Status: PUBLIC MESSAGE


   I am trying to use FSTRINGS.src in FPC 3.50.

   I used a copy of f83s to clean out all the MasterForth screens
   and load screens.

   I changed the definition of _'INPC to ignore the BLK and BLOCK words

   : _'INPC ( i -- a )
   \ Returns address for offset index in the input stream.
     TIB  + ;

   It floads ok, then I fload fstest, the accompanying test file, and whe
   it gets to "Testing [$LIT]", Software reset, Reboot to Continue, ..., 

   The problem is with [$LIT].  I haven't studied any of this with enough
   depth to see just what is going on inside of FPC.  Somewhere in the
   following definition is the cause for a Software RESET.  I think it is
   being caused by the COMPILE BRANCH statement, but that is just my SWAG

     : [$LIT] ( -- string )                        \ "bracket-s-lit"
   \ Compiled string literal
     COMPILE BRANCH HERE 0 ,  \ forward branch around string
     HERE ,$ HERE ROT ! [COMPILE] LITERAL ; IMMEDIATE

      This makes it crash ---------------------------------------+
                                                                 |
   +---------------------------------------------------------+   |
   | \ Test [$LIT] ( -- string )              GTH 09/11/87   |   |
   |                                                         |   |
   | TESTING '[$LIT]'                                        |   |
   |                                                         |   |
   | : COMP$ [$LIT] 'ABCDEFGHIJKLMNOPQRSTUVWXYZ' ;  <------------+
   | COMP$ @  \ should give ( -- 26 )                        |
   | 26 CHECK '[$LIT]' REGARDING LENGTH                      |
   |                                                         |
   | S1 _CF+ COMP$ _CF+ 26 SAME?  \ should give ( -- TRUE )  |
   | TRUE CHECK '[$LIT]' REGARDING CONTENTS                  |
   |                                                         |
   | HAS '[$LIT]' ALTERED STACK?                             |
   +---------------------------------------------------------+

   What must the definition of [$LIT] be to jump around a string that is
   being compiled?

 ---
  ~ EZ 1.24 ~ I am very FORTHward in my opinions...
-----
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'