Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!willett!ForthNet
From: ForthNet@willett.UUCP (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: ANS TC Magnet for Interpreter
Message-ID: <750.UUL1.3#5129@willett.UUCP>
Date: 7 Apr 90 13:03:33 GMT
Organization: Latest link in the ForthNet chain.  (Pgh, PA)
Lines: 40

Category 10,  Topic 24
Message 11        Sat Apr 07, 1990
R.BERKEY [Robert]            at 02:27 PDT
 
 
 To: Jan Stout, et. al.
 Re: COMPILE , POSTPONE's rationale note, and threading terminology

Jan Stout writes, 900321:

  > 4.  COMPILE
  [ re: an implementation of COMPILE for subroutine threaders. ]

I infer that the reference is to the rationale note for POSTPONE .

There is a valid standard's issue involved, but I think the rationale note
needs work.  Based on a couple of experiences, though, getting these things
adjusted is not so easy, so you might consider sending proposals, or
opinions/concerns, to the committee.

The issue that the (indicated) implementation of COMPILE won't work with
native code compilations is an implementation problem of the tradeoffs in
selecting native code compilation, as well as a standard's issue also
involving Forth hardware; as opposed to the validity of this implementation of
COMPILE for "jsr threading", "subroutine threading without inline code
expansion or peephole optimization".

We need concensus about what these terms mean, else these confusions will
continue.  To Tom Almy: As far as I know "native code compilation" is
terminology of your origin.  To all: Forth programmers in the San Diego area,
as via Guy Kelly, were using "jsr threaded" implementations since before the
days of fig-FORTH--the reference here and above to "jsr thread" is as I have
understood Kelly to use the term.  I don't recall having heard "subroutine
threaded code", in the sense used in BASIS 11, prior to the X3.J14
deliberations.  My impression is that the BASIS 11 terminology serves no
technical purpose.

-----
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'