Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Ian Collins Newsgroups: comp.lang.c++ Subject: Re: Help needed Date: Sat, 4 Apr 2020 19:43:04 +1300 Lines: 39 Message-ID: References: <66b94985-7db1-41e1-98f7-e509c5a0a142@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net kO+ZNsXckO0kiZFHRzYlrAGCkFzDY6j1SewVS/t62uL2KGjIAr Cancel-Lock: sha1:P8gFscDKiv5yruIWrwof/y0xnsQ= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 In-Reply-To: Content-Language: en-US Xref: csiph.com comp.lang.c++:72786 On 04/04/2020 19:20, Ned Latham wrote: > Paavo Helde wrote: >> On 4.04.2020 0:58, Ned Latham wrote: >>> Jorgen Grahn wrote: >>>> Ned Latham wrote: >>>> ... >>>>> C++ has become a moving target and a profligate producer of maintenance >>>>> nightmares. My own projects are okay so far, but I've had to make so >>>>> many fatuous changes that I'm now actively looking for languages to >>>>> port them to. >>>> >>>> Which changes would that be? Between, say a decent version two >>>> decades ago (C++98) and a well-supported one today (C++11)? >>> >>> Exception throwing: once an option, now the default. >>> "namespace": once an option, now a requirement. >> >> Exception throwing and namespaces were both in the first 1998 C++ >> standard. > > As options. No different from now. >> The problem with MSVC++ used to be that it purposefully chose >> to not follow the C++ standard in some places, but this has been mostly >> fixed in recent versions. >> >> What I find seriously objectionable is that the new C++ standards are >> actually *removing* things from the standard like std::auto_ptr and >> throw(), causing maintenance issues for old legacy codebases. > > I don't use std: or throw(). They're both crocks, IMO. So you are bitching about stuff that's been a standard part of the language for almost 23 years? That ship has sailed. -- Ian.