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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,ff3e0c57fc4cfad
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.220.230 with SMTP id pz6mr14952070pbc.3.1341624900793;
        Fri, 06 Jul 2012 18:35:00 -0700 (PDT)
Path: 
 l9ni11068pbj.0!nntp.google.com!news1.google.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
From: Adam Beneschan <adam@irvine.com>
Newsgroups: comp.lang.ada
Subject: Re: strange error in tiny ada 2012 program
Date: Fri, 6 Jul 2012 17:36:58 -0700 (PDT)
Organization: http://groups.google.com
Message-ID: <7faec088-ac59-44c2-93f2-0e7dce2b5d45@googlegroups.com>
References: <ba3d13c3-527e-4f09-8d09-ee7d450e5b62@googlegroups.com>
NNTP-Posting-Host: 66.126.103.122
Mime-Version: 1.0
X-Trace: posting.google.com 1341624900 9565 127.0.0.1 (7 Jul 2012 01:35:00
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sat, 7 Jul 2012 01:35:00 +0000 (UTC)
In-Reply-To: <ba3d13c3-527e-4f09-8d09-ee7d450e5b62@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=66.126.103.122;
 posting-account=duW0ogkAAABjRdnxgLGXDfna0Gc6XqmQ
User-Agent: G2/1.0
Content-Type: text/plain; charset=ISO-8859-1
Date: 2012-07-06T17:36:58-07:00
List-Id: <comp.lang.ada>

On Friday, July 6, 2012 2:55:53 PM UTC-7, Charly wrote:
 
> So my questions are:
> Did I make any mistake in this tiny program or is it a bug in the new GNAT version?
> How can a extend a proteced type (line 16).

I have no idea about the STORAGE_ERROR issue, but the answer to the second one is simple: you can't.  The following paragraph from AI95-345 appears to be the main reason:

An important advantage of eliminating inheritance of any code or data
for tasks and protected types is that the "monitor"-like benefits of
these constructs are preserved. All of the synchronizing operations are
implemented in a single module, simplifying analysis and avoiding any
inheritance "anomalies" that have been associated in the literature with
combining inheritance with synchronization.

                               -- Adam