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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ba049bdce87e95c1 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1994-09-26 06:54:56 PST Path: bga.com!news.sprintlink.net!howland.reston.ans.net!cs.utexas.edu!convex!news.duke.edu!eff!blanket.mitre.org!linus.mitre.org!linus!mbunix!eachus From: eachus@spectre.mitre.org (Robert I. Eachus) Newsgroups: comp.lang.ada Subject: Re: Newbie question about generic linked list tasks Date: 26 Sep 94 09:44:20 Organization: The Mitre Corp., Bedford, MA. Message-ID: References: <35q08a$1e5u@watnews1.watson.ibm.com> NNTP-Posting-Host: spectre.mitre.org In-reply-to: farrell@coral.cs.jcu.edu.au's message of 26 Sep 94 06:25:11 GMT Date: 1994-09-26T09:44:20+00:00 List-Id: In article farrell@coral.cs.jcu.edu.au (John Farrell) writes: > Thanks. This is beginning to sound like Constitutional Law. -- Yup! > I have to ask - if these things have workarounds, why is the restriction > there? Maybe this is more of a newbie question than the original :-). -- Because it isn't a restriction, it is a naming conflict. -- You need to be able to name the current task object in the body of -- the task, and you sometimes need to be able to refer to the task -- type as well. The design team decided to use the task type name -- for the first for consistency with task objects. This means a -- different name must be used for the type. Therefore if you need to -- name the type (and since qualified names won't work) you have to -- declare a subtype outside the task body. -- Robert I. Eachus with Standard_Disclaimer; use Standard_Disclaimer; function Message (Text: in Clever_Ideas) return Better_Ideas is...