[Oberon] Numerical CASE Statements in Project Oberon

[John Stout]

Jan

Yes, that's the one although my copy is on faded line printer paper!

I'm interested in your email about code generation: what does Module.Load patch and to what?

I've just bought an OberonStation and am getting to grips with it. I think the first task is to get another nRF24L01+ system working so that I can transfer stuff to and from it.

John


----------------------------------------------------------------------

Message: 1
Date: Mon, 23 Nov 2015 12:09:45 +0200
From: Jan de Kruyf <jan.de.kruyf at gmail.com>
To: ETH Oberon and related systems <oberon at lists.inf.ethz.ch>
Subject: Re: [Oberon] Numerical CASE Statements in Project Oberon
Message-ID:
        <CAA85NCh6R8Xf-Tp53sFF0=F_5rnH7WXoeTyeDQss-eDMsVMaLg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Is it this one John?

http://homepages.cwi.nl/~steven/pascal/

There are links there to a 76 version from eth.

j.


On Mon, Nov 23, 2015 at 9:47 AM, John Stout <JSS at kgv.ac.uk> wrote:

> Well, I should have done a bit more research before making my comments,
> and/or done all the exercises in Compiler Construction, which would have
> lead me to Professor Wirth's preferred implementation for CASE.
>
> I have the source code for the Pascal P4 compiler from 1976 (courtesy of
> Lancaster University) and that uses this system, although it does place a
> maximum of 1000 on the number of cases.
>
> John

[King George V Logo]
John Stout
Management Information Systems Coordinator
Tel: 01704 530601
E-Mail: JSS at kgv.ac.uk
Web: www.kgv.ac.uk


Information contained in this e-mail is intended for the use of the addressee only and is confidential.  Any dissemination, distribution, copying or use of this communication without prior permission of the addresseeis strictly prohibited.

Every effort has been made to ensure that any attachment to this mail does not contain virus. King George V College has taken every reasonable precaution to minimise this risk, neither it nor the sender can accept liability for any damage which you sustain as a result of software viruses. You should carry outyour own virus checks before opening any attachments.

[Think Before You Print]