C++ compiler accepts explicit constructor call
connect.microsoft.com
C++ compiler accepts explicit constructor call
1–10 of 30 posts
Re: C++ compiler accepts explicit constructor call
#2In a changing world, you can depend on Microsoft:
"Where you want to go today? Meh, as if we care; we have already decided on that."
Re: C++ compiler accepts explicit constructor call
#3Re: C++ compiler accepts explicit constructor call
#4And also here: http://connect.microsoft.com/VisualStudio/feedback/details/7... And again: http://connect.microsoft.com/VisualStudio/feedback/details/7...
Re: C++ compiler accepts explicit constructor call
#5Unless this breaks valid C++ code, I don't see how they need care too much about fixing it, especially since that would break existing code.
Re: C++ compiler accepts explicit constructor call
#6seems standard. visual studio releases are years behind each other so they're not going to fix anything that's not critical.
Re: C++ compiler accepts explicit constructor call
#7Unless this breaks valid C++ code, I don't see how they need care too much about fixing it, especially since that would break existing code.
A quote from Stroustrup:
"Use of a supplier's language extensions and non-standard-conforming features limits the portability of your code and can prevent you from choosing a new implementation supplier."
Re: C++ compiler accepts explicit constructor call
#8Unless this breaks valid C++ code, I don't see how they need care too much about fixing it, especially since that would break existing code.
A quote from Stroustrup: "Use of a supplier's language extensions and non-standard-conforming features limits the portability of your code and can prevent you from choosing a new implementation supplier." http://www.stroustrup.com/compilers.html
Quite a valid observation from Stroustrup. But in this case the programmer has chosen to use a non-standard, vendor specific feature. So it is not clear how it applies here? (Especially given the cost of breaking existing code)
Re: C++ compiler accepts explicit constructor call
#9Their approach seems reasonable. If they fix this, they will break code that currently works by depending on this. They've not said that they will never fix it, just that they won't for the time being and will reconsider for a future release.
Re: C++ compiler accepts explicit constructor call
#10Earlier quoted context omitted.
A quote from Stroustrup: "Use of a supplier's language extensions and non-standard-conforming features limits the portability of your code and can prevent you from choosing a new implementation supplier." http://www.stroustrup.com/compilers.html
Quite a valid observation from Stroustrup. But in this case the programmer has chosen to use a non-standard, vendor specific feature. So it is not clear how it applies here? (Especially given the cost of breaking existing code)
The programmer inadvertently used a vendor-specific feature. This is the key difference. Nobody writes perfect, standards-compliant code all the time, so the compiler needs to tell you when you are doing this.