Hildo Biersma <[EMAIL PROTECTED]> writes: > Many people see even this as a bad choice, saying that 'explicit' should > be the default, and that C++ constructors should be marked 'implicit' > for this behavior to be allowed. Hmmm... having 'explicit' be implicit and vice versa? I think my head may be about to start spinning. Thank ghod I don't do C++. -- Piers
- RFC 171 (v1) my Dog $spot should call a constructor im... Perl6 RFC Librarian
- Re: RFC 171 (v1) my Dog $spot should call a const... Nathan Wiger
- Re: RFC 171 (v1) my Dog $spot should call a const... Michael Maraist
- Re: RFC 171 (v1) my Dog $spot should call a c... Matt Youell
- Re: RFC 171 (v1) my Dog $spot should call... Nathan Wiger
- Re: RFC 171 (v1) my Dog $spot should ... Michael Fowler
- Re: RFC 171 (v1) my Dog $spot sh... Nathan Wiger
- Re: RFC 171 (v1) my Dog $spot should call a c... Michael Fowler
- Re: RFC 171 (v1) my Dog $spot should call a c... Jonathan Scott Duff
- Re: RFC 171 (v1) my Dog $spot should call... Hildo Biersma
- Re: RFC 171 (v1) my Dog $spot should ... Piers Cawley
- Re: RFC 171 (v1) my Dog $spot should call a const... Hildo Biersma
- Re: RFC 171 (v1) my Dog $spot should call a c... Matt Youell
- Re: RFC 171 (v1) my Dog $spot should call... Michael Fowler
- Re: RFC 171 (v1) my Dog $spot should call... Hildo Biersma
- Re: RFC 171 (v1) my Dog $spot should ... Nathan Wiger
- Re: RFC 171 (v1) my Dog $spot should ... Matt Youell
- Re: RFC 171 (v1) my Dog $spot should call a c... Michael Fowler
- Re: RFC 171 (v1) my Dog $spot should call a c... Nathan Wiger
- Re: RFC 171 (v1) my Dog $spot should call a const... Piers Cawley
- Re: RFC 171 (v1) my Dog $spot should call a c... Nathan Wiger