Re: Warning: Religious naming convention discussion :-) [was: assign help!!]

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

In article <dewar.863496133@merv> dewar@merv.cs.nyu.edu (Robert Dewar) writes:

   (I said:)

   >>  My reaction in those cases is to diagnose a misplaced use clause,
   >> and use the package name:

   >>  Parent : constant xxx := My_List_Instance.Parent (K);>>

   RBKD said:

   > Well you sure take a shaky place to make the no-use-clause
   > stand. I find it hard to imagine that anyone would think that it
   > made the GNAT soures clearer to do a global replace of Parent
   > with Atree.Parent. Given that the whole of GNAT is about tree
   > processing, and the Parent function is truly fundamental, this
   > seems silly to me.

   I wasn't advocating elimination of use clauses, and I never have.
I tend to be a moderate on the subject.  (Look at my .sig file! ;-)
But in this case, there is a perfectly simple "fix" of the problem by
adding the needed qualification.  The reason for the reference to
misplaced use clauses was because I'll look there to see what the
right prefix is.

   Incidently, and here I am willing to be counted as an extremist,
often the right solution to use cause induced conflicts is to put the
use clauses where needed, rather than in the context clause.  If you
have 20 operations on an ADT, two of which use Text_IO, put a with
Text_IO in the context clause for the body, but put the use clauses in
the IO operations.

--

					Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...