🚀 go-pugleaf

In article <4638jp$ef4@fsgm01.fnal.gov> b91926@fsgm01.fnal.gov (David Sachs) writes:

> X x(a) uses higher priority conversion by overloading rules
> 
> X x=a uses X(a.operator X&)

Sort of.  If a is of class A, if the copy constructor X::X(const X&)
exists, and if the converting constructor X::X(const A&) exists and
isn't qualified as explicit, then "X x(a)" simply invokes the
converting constructor while "X x=a" invokes the converting
constructor and then the copy constructor.

Section 12.6 of the working paper explains this in detail.  The rest
of chapter 12 is somewhat relevant too.
-- 
  Matt Austern                             He showed his lower teeth.  "We 
  matt@physics.berkeley.edu                all have flaws," he said, "and 
  http://dogbert.lbl.gov/~matt             mine is being wicked."

---
[ 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. ]