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,1d6e3c069f70fa5a,start
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news3.google.com!news.glorb.com!feeder.xsnews.nl!news.germany.com!news.belwue.de!LF.net!news.enyo.de!not-for-mail
From: Florian Weimer <fw@deneb.enyo.de>
Newsgroups: comp.lang.ada
Subject: "Do not use" feature list for GNAT
Date: Tue, 23 Aug 2005 18:41:53 +0200
Message-ID: <877jecppv2.fsf@mid.deneb.enyo.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: albireo.enyo.de 1124815322 10242 212.9.189.177 (23 Aug 2005 16:42:02
 GMT)
X-Complaints-To: 
Cancel-Lock: sha1:XlEK7js+Mc+JC+HxmXagBI2AzlU=
Xref: g2news1.google.com comp.lang.ada:4261
Date: 2005-08-23T18:41:53+02:00
List-Id: <comp.lang.ada>

Would you like to share a list of language areas which you should
avoid when using GNAT because AdaCore customers do not stress-test
them and they are riddled with strange bugs?

My current list looks roughly like this:

  - access discriminants (several ICE-on-legal bugs)

  - subunits (ICE, maybe on invalid input, I'm not sure)

  - the 'Valid attribute (wrong-code bug with GCC 4)

  - conditional entry calls (run-time bug in GNAT 3.15p)

Anything I've missed so far?