[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: strings and QStrings
From:       Mark Deneen <deneen () bucknell ! edu>
Date:       2000-12-10 15:03:47
[Download RAW message or body]

On Sunday 10 December 2000 06:48 pm, David van Hoose wrote:
> Patrick Julien wrote:
> > I think I have wasted enough time on this.  But I will try one last time.
> >
> >         In all cases, YES because on init this ( B b1 = a; ) is not
> > operator=.  Try any modern compiler that supports the "explicit" keyword
> > and modify the original example to say.
> >
> >         explicit B ( const A & a ) { ... }
> >
> > All the compilers are gonna barf at
> >         B b1 = a;
> >
> > but not at
> >         b1 = a;
> > and not
> >         B b1 ( a );
> >
> > Because they can't call the constructor implicitely.
>
> Implicit calling violates programming theory as it has collisions
> within the logic laid out. The compiler should compile exactly what the
> programmer has written as there is a damn good reason for them writing
> the code as such.

One of you look at the c++ spec and stop this thread.
 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]