Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site utcsri.UUCP
Path: utzoo!utcsri!greg
From: greg@utcsri.UUCP (Gregory Smith)
Newsgroups: net.lang,net.lang.c
Subject: Re: Threading in C (Re: RRe: What's so good about FORTH?
Message-ID: <3111@utcsri.UUCP>
Date: Wed, 16-Jul-86 10:01:46 EDT
Article-I.D.: utcsri.3111
Posted: Wed Jul 16 10:01:46 1986
Date-Received: Wed, 16-Jul-86 10:24:31 EDT
References: <201@pyuxv.UUCP> <3700003@uiucdcsp> <132@vaxb.calgary.UUCP> <223@cci632.UUCP>
Reply-To: greg@utcsri.UUCP (Gregory Smith)
Organization: CSRI, University of Toronto
Lines: 17
Keywords: FORTH, threaded-code
Summary: Two stacks not essential

In article <223@cci632.UUCP> rb@ccird1.UUCP (Rex Ballard) writes:
>There seems to be a little confusion about threading here.  All that is
>*really* required for threading is a parameter stack that is separate
>from the program/return stack.
>
The DEC PDP-11 FORTRAN compiler can produce threaded code, and only uses
the hardware stack. If you want the language to be stack-based ( from
the point of view of the programmer, i.e. expressions in RPN ) and you
want data pushed by a caller to be poppable by the callee, then separate
stacks are the best way to do it. That is a characteristic of forth, but
I don't think that it is a characteristic of threaded code.

-- 
"You'll need more than a Tylenol if you don't tell me where my father is!"
						- The Ice Pirates
----------------------------------------------------------------------
Greg Smith     University of Toronto      UUCP: ..utzoo!utcsri!greg