🚀 go-pugleaf

[code and explanation deleted]

The confusion seems to be over HOW a compiler
must behave when the program is ill-formed.

If (and only if) it is a diagnosable error, the compiler
must issue at least one diagnostic message (1.7/1&2).

The question that started this thread was focused
on the classes involved.  Generally, when those are
processed, there is not enough information to
diagnose the program as ill-formed.  Rather, the
stage is merely set for possible styles of ill-formed-ness
that can result.  When the use is processed, the
compiler now has a diagnosable case of ill-formed-ness
and it must emit an error message.  That error message
is, inevitably, associated with the use.  This is THE
appropriate piece of code to finger, though the error
message will establish the properties of the context
that make the use ill-formed.

Good Day
Dick
Dick.Menninger@DaytonOH.ATTGIS.COM
---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]