- Available C++ Libraries FAQ - 1 Update
- Question on "range-for-statement" - 1 Update
- Static exceptions - 1 Update
- random_device question - 1 Update
| Nikki Locke <nikki@trumphurst.com>: Oct 14 10:23PM Available C++ Libraries FAQ URL: http://www.trumphurst.com/cpplibs/ This is a searchable list of libraries and utilities (both free and commercial) available to C++ programmers. If you know of a library which is not in the list, why not fill in the form at http://www.trumphurst.com/cpplibs/cppsub.php Maintainer: Nikki Locke - if you wish to contact me, please use the form on the website. |
| Bonita Montero <Bonita.Montero@gmail.com>: Oct 14 07:53PM +0200 > for(const auto &i : x) > cout << i << " "; I think auto shold be used only when really needed, f.e. when x would be a templated object whose iterators reference a "dyamic" type. But in the upper case the code simply becomes less readable. |
| "Öö Tiib" <ootiib@hot.ee>: Oct 14 02:55AM -0700 > CPP Con. It was helpful and I recommend it. He mentions how > Swift has had static exceptions for years. He also mentions > Outcome. Swift's exceptions are useless things in practice. Throwing these is made less convenient than returning optionals or enums. Optional in Swift is std::weak_ptr for classes and std::optional for structs. Enum in Swift is like std::variant. Apple's framework still throws its Objective C/C++ exceptions and Swift is incapable of catching those. So a team that wants to develop in Swift may need to understand all three languages. Similar issue is with Kotlin and Java ... who wants to develop in Kotlin may need to understand Java. > Anyone want to trade Coroutines and Concepts for static exceptions? If the static exceptions will be made side-by-side with current exceptions then result will be rather unpleasant. We had that already with "structured" exceptions. The "__try" and "try" were in mix on Windows in nineties. That was horrible and had only bad outcome. RaiseException() is banned by everybody, lot of people consider exceptions very evil to this day and everything what was possible to __except with __try is likely doomed to be "undefined behavior" forever now. |
| "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>: Oct 13 11:27PM -0700 On 10/13/2019 1:51 PM, Chris M. Thomasson wrote: >>> ;^) >> Funny, however I wonder how reliable it can be - there is no guarantee >> of an actual race condition. Well, if the simulation was using a single thread, then there is no race condition wrt the foobare'd impl of fetch-and-add. > Yes there is. I am implementing an atomic fetch-and-add operation in a > very standard yet racy way, well, lets call it the full blown wrong way > wrt the fetch-and-add... [...] |
| 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