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

Re: Proposal: Abstract types for OOC

To: Mailinglist 'OOC' <ooc-list@informatik.uni-kl.de>
Subject: Re: Proposal: Abstract types for OOC
From: Tim Teulings <tim@edge.ping.de>
Date: Sat, 2 Jan 1999 18:21:30 +0100
Delivered-To: jnzimmer@donau.informatik.uni-kl.de
In-Reply-To: <3.0.1.32.19990102223659.00946980@central.murdoch.edu.au>; from Stewart Greenhill on Sat, Jan 02, 1999 at 10:36:59PM +0000
Mail-Followup-To: Mailinglist 'OOC' <ooc-list@informatik.uni-kl.de>
References: <3.0.1.32.19981222060833.00915e80@central.murdoch.edu.au> <16599599@oberon.noris.de> <3.0.1.32.19990102223659.00946980@central.murdoch.edu.au>

Hallo!

> We could enforce this interpretation of abstract types by insisting that
> every type declared ABSTRACT has at least one method declared ABSTRACT. I
> would be prepared to add this to the specification. Can anyone think of any
> useful programming constructs that would be disallowed by this restriction?

The special abstract type object (ObjectDesc = RECORD END) would
perhaps somehow an abstract type (it does not implement anything and
serves only as a base type to inherit from) but has (perhaps) no
methods.

--
Gruß...
       Tim.

References:
- Proposal: Abstract types for OOC
  - From: Stewart Greenhill <greenhil@murdoch.edu.au>
- Re: Proposal: Abstract types for OOC
  - From: hartmut Goebel <hartmut@oberon.noris.de>
- Re: Proposal: Abstract types for OOC
  - From: Stewart Greenhill <greenhil@murdoch.edu.au>

Prev by Date: [ANN] Release of OO2C for the BeOS (x86 & PPC)
Next by Date: [ANN] UnixCalc release for BeOS R4 (PPC & x86)
Prev by thread: Re: Proposal: Abstract types for OOC
Next by thread: Re: Proposal: Abstract types for OOC
Index(es):
- Date
- Thread