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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f7344,dbab47e756f4068e
X-Google-Attributes: gidf7344,public
X-Google-Thread: 103376,dbab47e756f4068e
X-Google-Attributes: gid103376,public
From: Charlie McCutcheon <cmccut>
Subject: Re: DEC Ada V3.3
Date: 1996/08/23
Message-ID: <4vl77s$obt@nntpd.lkg.dec.com>#1/1
X-Deja-AN: 176040638
references: <321C3BC6.1897@dial.eunet.ch> <321D6756.3AA2@ubs.com>
content-type: text/plain; charset=us-ascii
organization: Digital Equipment Corporation
x-url: news:321D6756.3AA2@ubs.com
mime-version: 1.0
newsgroups: comp.lang.ada,comp.os.vms
x-mailer: Mozilla 1.12I (X11; I; OSF1 V4.0 alpha)
Date: 1996-08-23T00:00:00+00:00
List-Id: <comp.lang.ada>


>AST_ENTRY issue

The only example I can think of would be on Alpha VMS V7.0, where
you must use pragma AST_ENTRY, due to DECthreads changes.  (You didn't
use to need the pragma).  This issue is in OpenVMS release notes.

Otherwise, I haven't seen this problem before.  If you can't reproduce
it with a small example, then we probably can't either without an example.

If you have a DEC Ada support contract, please work through there with
a reproducing program, since this sounds like a potential bug.

Charlie