[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Abstract classes in Oberon / OOC

To: ooc-list@informatik.uni-kl.de
Subject: Re: Abstract classes in Oberon / OOC
From: Tim Teulings <tim@edge.ping.de>
Date: Mon, 14 Dec 1998 14:51:39 +0100
Delivered-To: jnzimmer@donau.informatik.uni-kl.de
In-Reply-To: <lazp8psrvo.fsf@oberon.i-did-not-set--mail-host-address--so-shoot-me>; from Michael van Acken on Tue, Dec 15, 1998 at 09:59:07AM +0100
Mail-Followup-To: ooc-list@informatik.uni-kl.de
References: <3.0.1.32.19981214171001.00936890@central.murdoch.edu.au> <lazp8psrvo.fsf@oberon.i-did-not-set--mail-host-address--so-shoot-me>

Hallo!

> > Comments? Language purists: please don't flame me too hard :-)

I vote for 1 if other compiler simply would ignore such (for them
unknown) flag.

> Note that making with making it a system flag issue, this is an OOC
> specific extension.  Technically we are not touching the O2 syntax,
> but we do change O2 semantics by disallowing instanciation of certain
> user defined types.

Correct. However we kick the semantics in the right direction. But it
should not be a problem. Code from other compilers does not have this
flag and will compiler. Code that has this flag, will compile correctly
under oo2c and will run ok using other compilers (if they ignore the
flag) if the code run under oo2c.

--
Gru...
       Tim.

References:
- Abstract classes in Oberon / OOC
  - From: Stewart Greenhill <greenhil@murdoch.edu.au>
- Re: Abstract classes in Oberon / OOC
  - From: Michael van Acken <Michael.van.Acken@de.uu.net>

Prev by Date: Re: Abstract classes in Oberon / OOC
Next by Date: New version...
Prev by thread: Re: Abstract classes in Oberon / OOC
Next by thread: Re: Abstract classes in Oberon / OOC
Index(es):
- Date
- Thread