Xref: utzoo comp.sys.amiga:41686 comp.sys.amiga.tech:7595
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ames!ncar!tank!eecae!cps3xx!usenet
From: usenet@cps3xx.UUCP (Usenet file owner)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: Wish for 1.4 (re fork*)
Keywords: announcing, first list in Nov
Message-ID: <4989@cps3xx.UUCP>
Date: 15 Oct 89 17:15:53 GMT
References: <13920002@hpfelg.HP.COM> <4340@sugar.hackercorp.com> <8154@cbmvax.UUCP> <4352@sugar.hackercorp.com>
Reply-To: porkka@frith.UUCP (Joe Porkka)
Organization: Michigan State University
Lines: 23

In article <4352@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes:
->In article <8154@cbmvax.UUCP> jesup@cbmvax.UUCP (Randell Jesup) writes:
->> In article <4340@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes:
->> >The ability to run BCPL commands is only needed if there are BCPL commands
->> >shipped with 1.4.
->
->> 	No, we MUST support 1.3/1.2 WB disks under 1.4.  Many commercial
->> programs are shipped with such things on them.  We may not support them
->> forever, though.
->
->You're right. Sigh... all is not lost, though. The System() call can use
->a new interface and abandon BCPL programs, if the existing Execute() call
->remains (which it will have to do, for compatibility), and the standard CLI
->uses it. However, a new shell (AmigaShell 2.0?) should be at liberty to
->abandon BCPL. Not so?

You are still gonna get zapped sooner or later.

Question to CBM> Is there an easy way to tell a CBM BCPL executable
from most other stuff? I imagine all (or most) BCPL programs
from CBM all start out the same way. Sooo, a System() call
could detect this, and return an error instead of a GURU.
 Joe Porkka   porkka@frith.egr.msu.edu