Article View: comp.std.c++
Article #1761Re: Why no conversion of string to const char * in STD lib?
From: Rick Hollinbeck
Date: Mon, 21 Aug 1995 17:49
Date: Mon, 21 Aug 1995 17:49
16 lines
1284 bytes
1284 bytes
Distribution: Oren Ben-Kiki (oren@melissa.schema.co.il) wrote: : But now that we have the 'explicit' keyword, shouldn't this decision be : reconsidered? This seems like just the situation for which it was intended. I don't think this will work, since 'const char *' is not a class, and therefore cannot have its constructor declared as explicit. As far as I understand, the explicit keyword can only be applied to type conversion constructors (not operator functions like 'operator const char *'). --- [ 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. ]
Technical Details
Message-ID:
<MATT.95Aug21104958@physics2.Berkeley.EDU>Path:
arc1-ca.pugleaf.net!128.32.155.1!mattReferences:
<BASHFORD.95Aug1200815@toad.scripps.edu> <MATT.95Aug13161131@physics2.Berkeley.EDU> <MATT.95Aug16093212@physics2.Berkeley.EDU>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!128.32.155.1!matt From: rickh@csn.net (Rick Hollinbeck) Newsgroups: comp.std.c++ Subject: Re: Why no conversion of string to const char * in STD lib? Date: 21 Aug 1995 17:49:57 GMT Organization: SuperNet Inc. (303)-296-8202 Denver Colorado Approved: matt@physics2.Berkeley.EDU (Matt Austern) Message-ID: <MATT.95Aug21104958@physics2.Berkeley.EDU> References: <BASHFORD.95Aug1200815@toad.scripps.edu> <MATT.95Aug13161131@physics2.Berkeley.EDU> <MATT.95Aug16093212@physics2.Berkeley.EDU> NNTP-Posting-Host: physics2.berkeley.edu