[Oberon] Project Oberon, 2013 Edition
sinu.nayak2001 at gmail.com
Tue Apr 1 08:03:06 CEST 2014
I agree on this not only once, but twice.
It really makes sense to keep code out of book text now.
It makes life lot easier in code navigating.
The question came to my mind, just to re-confirm that, we still follow our words on designing a system that can be fit in a single book; studied, understood and maintained by a single person.
With thanks and best regards,
On 04/01/2014 03:00 AM, Chris Burrows wrote:
>> -----Original Message-----
>> From: Srinivas Nayak [mailto:sinu.nayak2001 at gmail.com]
>> Sent: Monday, 31 March 2014 11:30 PM
>> To: ETH Oberon and related systems
>> Subject: Re: [Oberon] Project Oberon, 2013 Edition
>> Dear All,
>> Surprisingly, in 2013 edition, the book body doesn't contain full source
>> sections of the system, as used to be in old editions.
>> Any idea why?
> 22 years have gone by and the world has changed a lot since then. When the
> original edition of Project Oberon was first published the internet wasn't
> widely available and the main way of distributing source code was on a
> floppy disk (often different for different host computers) by postal mail so
> it made sense to include the listings in the book.
> Later Oberon books included a CD (The Oberon Companion) or a floppy disk
> (Compiler Construction) with the printed copy of the book.
> Nowadays it is most convenient to have both the book available as a PDF file
> for browsing and the source code to be available in a machine-readable form
> so that it can be viewed / navigated in a syntax-aware IDE or compiled. You
> then only need snippets of code in the book where it is necessary to
> illustrate particular details,
> Chris Burrows
> CFB Software
> Astrobe: Oberon Development System for ARM7 and Cortex-M3
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
More information about the Oberon