In article <44e9c976.329081656@[EMAIL PROTECTED]
>,
Stephen Pelc <stephenXXX@[EMAIL PROTECTED]
> wrote:
>ThrowIors.txt
>Stephen Pelc, 21 August 2006
>
>Rationale
>=========
>
>Problem
>-------
>Error codes returned by some words, e.g. ALLOCATE are not specified,
>and an application has no entitlement to use them as THROW codes.
>The leads to very clumsy code of the form:
>
> ALLOCATE IF <lit> THROW ENDIF
>
>or
>
>: ?THROW \ ior throwcode --
> SWAP IF THROW ELSE DROP THEN ;
>
> ALLOCATE <lit> ?THROW
>
>However, we also see many instances of code such as
>
> ALLOCATE THROW
>
>which leads to silent aborts when a system issues -1 THROW (as
>it is currently entitled to) or incorrect error messages.
I'm so strongly in favor of throwable io-codes that I sacrificed
ISO-compatibility in this respect in ciforth.
>--
>Stephen Pelc, stephenXXX@[EMAIL PROTECTED]
Albert
--
--
Albert van der Horst, UTRECHT,THE NETHERLANDS
Economic growth -- like all pyramid schemes -- ultimately falters.
albert@[EMAIL PROTECTED]
http://home.hccnet.nl/a.w.m.van.der.horst
|
