From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,ee887b7593f7961b
X-Google-Attributes: gid103376,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news3.google.com!feeder.news-service.com!newsfeed.freenet.de!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Re: Ada OS based on Minix3
Newsgroups: comp.lang.ada
User-Agent: 40tude_Dialog/2.0.15.1
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Reply-To: mailbox@dmitry-kazakov.de
Organization: cbb software GmbH
References: 
 <ed7d1ea9-bf0b-4e4a-b317-b57102853d65@p35g2000prm.googlegroups.com>
 <cef1a685-f474-4f5b-ba0c-1a1f0464310a@r37g2000prr.googlegroups.com>
 <1pmkcuemqczer.j2i34pvc2lne$.dlg@40tude.net>
 <81912719-8c66-439d-a40e-529b22acd8a6@u29g2000pro.googlegroups.com>
 <m9vvo4igyswg.1v3x0wk3xi1db.dlg@40tude.net>
 <wccd4h3iomo.fsf@shell01.TheWorld.com>
Date: Mon, 10 Nov 2008 16:56:35 +0100
Message-ID: <14t6hwu8udm8j$.1x339y69m2ew1.dlg@40tude.net>
NNTP-Posting-Date: 10 Nov 2008 16:56:35 CET
NNTP-Posting-Host: ac4363dc.newsspool1.arcor-online.net
X-Trace: 
 DXC=3g5D;gKe;?nm7>ihJR;B_cic==]BZ:afn4Fo<]lROoRa^YC2XCjHcbiTPFk8flE51aDNcfSJ;bb[eFCTGGVUmh?dLK[5LiR>kgbdUihOMN7m8h
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news1.google.com comp.lang.ada:2644
Date: 2008-11-10T16:56:35+01:00
List-Id: <comp.lang.ada>

On Mon, 10 Nov 2008 10:31:27 -0500, Robert A Duff wrote:

> "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:
> 
>> 6. Proper construction/destruction
> 
> What do you see as the limitations/problems with Ada in this area?

1. User-defined initialization/finalization shall be definable for any
type. I do mean any.

2. Composition rules of initialization/finalization for derived types must
ensure execution of the user-defined initialization/finalization code for
the base type.

3. User-defined initialization/finalization shall be definable for
class-wide types. AKA dispatch from constructor/destructor. Actually, a
part of the pos. 1.

4. Task-as-a-component problem to be solved.

5. Getting a pool-specific pointer to the object upon
initialization/finalization, when the object is allocated in such a pool.
(Unchecked_Conversion is really nasty there)

6. LHS/RHS issue.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de