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.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,a1265d36600e47dd
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.181.12.101 with SMTP id ep5mr595236wid.1.1351608361543;
        Tue, 30 Oct 2012 07:46:01 -0700 (PDT)
Path: 
 ha8ni87232wib.1!nntp.google.com!feeder3.cambriumusenet.nl!217.73.144.44.MISMATCH!ecngs!feeder.ecngs.de!xlned.com!feeder7.xlned.com!news2.euro.net!82.197.223.108.MISMATCH!feeder2.cambriumusenet.nl!feed.tweaknews.nl!193.141.40.65.MISMATCH!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Tue, 30 Oct 2012 15:37:30 +0100
From: Georg Bauhaus <rm.dash-bauhaus@futureapps.de>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Static bounds of loop - compilation error
References: <6cc8e815-96c3-4a79-8bcd-e3aea906b889@googlegroups.com>
In-Reply-To: <6cc8e815-96c3-4a79-8bcd-e3aea906b889@googlegroups.com>
X-Enigmail-Version: 1.4.5
Message-ID: <508fe626$0$6634$9b4e6d93@newsspool2.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 30 Oct 2012 15:37:26 CET
NNTP-Posting-Host: dc1a7159.newsspool2.arcor-online.net
X-Trace: 
 DXC=aYTZ2anKj;X\9P[:DUn00QA9EHlD;3YcR4Fo<]lROoRQ8kF<OcfhCO[SWM54i`XW]\nc\616M64>ZLh>_cHTX3j]Ra_<b1:H=]X
X-Complaints-To: usenet-abuse@arcor.de
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Date: 2012-10-30T15:37:26+01:00
List-Id: <comp.lang.ada>

On 30.10.12 14:26, pascal.malaise@gmail.com wrote:
> Hi Ada experts,
> 
> can anyone explain the following compilation errors:
> procedure T is
>   type E is (A, B, C);
>   subtype S is E range A .. B;
>   X, Y : S;
> begin
>   X := A;
>   Y := B;
>   for I in S range X .. Y loop
>     case I is
>       when A => null;
>       when B => null;
>     end case;
>   end loop;
> end T;
>>> missing case value: "C"

> So is it a bug?

I won't speculate, but assuming it is not a bug, then qualifying the I
should not make the compiler think the source is fine after qualifying?

 for I in S range X .. Y loop
    case S'(I) is
      when A => null;
      when B => null;
    end case;
  end loop;