| Lynn McGuire <lmc@winsim.com>: Sep 28 12:14PM -0500 "Rejuvenating the Microsoft C/C++ Compiler" http://blogs.msdn.com/b/vcblog/archive/2015/09/25/rejuvenating-the-microsoft-c-c-compiler.aspx The Walking Dead? Lynn |
| Paavo Helde <myfirstname@osa.pri.ee>: Sep 28 12:59PM -0500 > http://blogs.msdn.com/b/vcblog/archive/2015/09/25/rejuvenating-the-m > icrosoft-c-c-compiler.aspx > The Walking Dead? Looks like they are on the right track. Lagging few years behind as always, but at least they are explicitly aiming for a fully standards-compliant compiler. And there is ìn principle nothing wrong with working with a 30- year old codebase and enhancing it gradually. Cheers Paavo |
| red floyd <no.spam.here@its.invalid>: Sep 27 10:05PM -0700 On 9/26/2015 11:50 AM, Rosario19 wrote: >> Why are you still using <iostream.h> instead of <iostream> >> 17 years after standardization? > i like the past time Irrelevant. Since <iostream.h> is not standard, it can do whatever the hell it wants, and nobody can tell you what it is supposed to do. |
| Rosario19 <Ros@invalid.invalid>: Sep 26 08:48PM +0200 On Sat, 26 Sep 2015 10:49:59 -0700, Barry Schwarz wrote: >Since you second code sample has almost no relation to your first, are >we still discussing your incorrect assertion that the order of calling >the precision and width functions causes different output? no it is not in discussion, i remembered it wrong etc what could be in discussion coul be: if i need to show the number + 2 digit afther the point... in C i have printf("%.2f", (double)123.123); -> "123.12" what in C++? |
| Juha Nieminen <nospam@thanks.invalid>: Sep 28 08:51AM > The C++ Standard Library also incorporates 18 headers of the ISO C90 C standard library ending with ".h", but their use is deprecated. > [...] > I must have been living under a rock: I did not know this was being deprecated. Any reference on this ? and why ? I think that it's referring to standard include files inherited from C using the .h suffix, which is deprecated. The non-deprecated versions omit the .h (and add a 'c' at the beginning of the header file name, such as <cstdio>.) --- news://freenews.netfront.net/ - complaints: news@netfront.net --- |
| "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com>: Sep 28 02:04AM +0200 On 9/27/2015 12:40 PM, Udo Steinbach wrote: > After reading http://www.boost.org/community/exception_safety.html and > experimenting with throwing at every point that can throw ... > How do you test your code for exception safety? You can use memory leak detectors to detect memory leaks. That's one aspect. You can generate hashes of object state to detect changed object state. That's another aspect. These comments are just common sense. I'm not aware of special techniques for generating exceptions within operations used by the code. It could be very costly to create mockups of lower level operations. > Is there any module for doing that in the world? Don't know, sorry. Cheers & hth., - Alf |
| Ian Collins <ian-news@hotmail.com>: Sep 28 01:12PM +1300 Udo Steinbach wrote: > and experimenting with throwing at every point that can throw ... How > do you test your code for exception safety? Is there any module for > doing that in the world? As part of my unit tests, I mock everything the code under test calls. It is straightforward to get the mock functions to throw exceptions. -- Ian Collins |
| You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to comp.lang.c+++unsubscribe@googlegroups.com. |
No comments:
Post a Comment