Re: Newbie question about generic linked list tasks

[eachus@spectre.mitre.org (Robert I. Eachus)]

In article <farrell.780560711@coral.cs.jcu.edu.au> 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...