Re: Compiler chooses conv ctor - why?
- From: "Ben Voigt [C++ MVP]" <rbv@xxxxxxxxxxxxx>
- Date: Tue, 15 Apr 2008 18:06:13 -0500
Charles Wang[MSFT] wrote:
Hi Cezary,
Thank you for your explaining on this according to ISO standard. I
think that I understand your meaning. Your main concern should be
that at least the compiler should throw an warning to tell developers
this potential issue, right? Could you please give Microsoft feedback
Really, the compiler should adopt the behavior specified by the standard and
provide a command-line parameter to allow programs relying on the old
behavior to compile. (like was done with forscope).
This "it's ok to depart from the standard as long as we document it" is why
programmers 'round the world are fed up with Microsoft. That happened with
IE DHTML support and look at the mess that made, now IE can't even follow
the standard if Microsoft wants it to.
.
- References:
- Compiler chooses conv ctor - why?
- From: Cezary H. Noweta
- Re: Compiler chooses conv ctor - why?
- From: Alex Blekhman
- Re: Compiler chooses conv ctor - why?
- From: Charles Wang[MSFT]
- Re: Compiler chooses conv ctor - why?
- From: Cezary H. Noweta
- Re: Compiler chooses conv ctor - why?
- From: Charles Wang[MSFT]
- Compiler chooses conv ctor - why?
- Prev by Date: Re: Array of char pointers.
- Next by Date: Re: Standard C Library and utf-8
- Previous by thread: Re: Compiler chooses conv ctor - why?
- Next by thread: Re: Compiler chooses conv ctor - why?
- Index(es):
Relevant Pages
|
Loading