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,3abdaa39e1c27f49 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news3.google.com!news.glorb.com!wns14feed!worldnet.att.net!attbi_s51.POSTED!53ab2750!not-for-mail From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: Discriminant computation problem References: <2vv4icF2pe63tU1@uni-berlin.de> X-Newsreader: Tom's custom newsreader Message-ID: NNTP-Posting-Host: 67.161.24.234 X-Complaints-To: abuse@comcast.net X-Trace: attbi_s51 1100636047 67.161.24.234 (Tue, 16 Nov 2004 20:14:07 GMT) NNTP-Posting-Date: Tue, 16 Nov 2004 20:14:07 GMT Organization: Comcast Online Date: Tue, 16 Nov 2004 20:14:07 GMT Xref: g2news1.google.com comp.lang.ada:6233 Date: 2004-11-16T20:14:07+00:00 List-Id: More quibbling: > type Bit_Vector (Bit_Max: Bit_Number) is > new Ada.Finalization.Controlled with > record > Payload: Vector_Access; > end record; Since there's an access type around, Bit_Vector should be either "limited" or there should be an Adjust to do a deep copy (or whatever). > procedure Initialize (Vector: in out Bit_Vector) is > begin > Vector.Payload := new Bit_Vector_Payload'( Is it possible for Initialize to be called more than once? (Say by an explicit call.) If so, there should be a Free(Vector.Payload) before assigning a "new" access value.