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: 103376,e51581f95441cb4 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Discriminant as default initial value Date: 1997/04/02 Message-ID: #1/1 X-Deja-AN: 230148798 References: <199704020043_MC2-13A2-3DDB@compuserve.com> Organization: New York University Newsgroups: comp.lang.ada Date: 1997-04-02T00:00:00+00:00 List-Id: Kees said << I know by now how you feel about these things. It is just that this one intrigued me, because I had not encountered the use of a record discriminant as the default value for a component before. I spent a couple of minutes trying it out, found that it seemed to work, and decided that I could just as well post the reply.>> Using a discriminant in the expression for a default value is perfectly valid (it does not have to be on its own, it can be used within an expression, e.g. you can have a default expression A+B where both A and B are discriminants). This is legal because there is no rule that says it is illegal. And it should work properly!