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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,7a2d45f282a1da1c X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-09-03 18:41:45 PST Path: archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-post-01!supernews.com!corp.supernews.com!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: float with 24-bit resolution Date: Wed, 3 Sep 2003 20:43:42 -0500 Organization: Posted via Supernews, http://www.supernews.com Message-ID: References: <3F3CCB0F.543478AF@adrianhoe.nospam.com.my> <3f405ef4$1_1@news.tm.net.my> <3f54bf19_1@news.tm.net.my> X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 X-Complaints-To: abuse@supernews.com Xref: archiver1.google.com comp.lang.ada:42122 Date: 2003-09-03T20:43:42-05:00 List-Id: > Matthew Heaney writes: > > > Null_Object : T := null; > > > I find the latter convention confusing, because it suggests that if > > the initialization part were omitted, then the object wouldn't be > > initialized. But that would be incorrect. *I* find Null_Object : T; confusing. A maintenance programmer probably doesn't know the class of object that T represents, and the lack of an initialization looks like a bug. You could "fix" that with a comment, but an explicit initializer works just as well. (The lack of "constant" is also suspicious here; if the object is a variable, it probably shouldn't be named "Null anything", because it could change.) After all, I often have: Null_Object : constant T := ...; in my programs, where T could be any type. If the object is a variable, it probably ought to be initialized with something useful. But I suspect being consistent is more important than any particular rule. Randy.