RotsiserMho

8 ms·

31.
by RotsiserMho 10y ago
It's disturbing that this is considered normal. I would never work for a company that required this of me.
32.
by RotsiserMho 10y ago
Mackup ( https://github.com/lra/mackup ) is a great tool for this. Beware, however, that it creates symlinks in place of your existing files. So if you decide you don't like it, run the uninstall command before re
33.
by RotsiserMho 10y ago
True, but a lot of that functionality can be gained using boost::signals2 and a simple cross-thread queue. (though some may question the wisdom of trading one dependency for another, I prefer my dependencies decoupled from each other). Stil
34.
by RotsiserMho 10y ago
My problem with it is the fact that it inserts itself in my otherwise standard-conformant C++ code; right in the middle of class declarations. If I decide I want to use another GUI framework I'd have to refactor that code. Most other b
35.
by RotsiserMho 10y ago
It's an incredibly fast moving target. Just look at the GTK mess, let alone keeping a wrapper toolkit up to date with other vendors' OS updates. Plus for operating systems like Windows it's not really clear which GUI technolo
36.
by RotsiserMho 10y ago
hiro ( https://gitlab.com/higan/higan/tree/master/hiro ) by byuu ( http://byuu.org ) is similar to libui in that it wraps native controls. It isn't quite stable but it's very interestin
37.
by RotsiserMho 10y ago
I avoided Qt for a long time due to what I'd heard about moc being required. However recent versions support connecting lambdas to slots which is sufficient for my relatively simple application to avoid using moc to set up signals&#x2F
38.
by RotsiserMho 10y ago
The low road at that. Nice catch.
39.
by RotsiserMho 10y ago
Heh
40.
by RotsiserMho 10y ago
I drive an FRS (Toyota 86) for this reason. It's an absolute joy to drive.
41.
by RotsiserMho 10y ago
Protection != prevention
42.
by RotsiserMho 10y ago
I was disappointed to see that concurrency support won't be in Swift 3.0.
43.
by RotsiserMho 10y ago
Me too. Is something similar available in Rust? I'm familiar with smart pointers in C++ but I love that Swift manages a lot of that mess for me.
44.
by RotsiserMho 10y ago
As a C++14 programmer, I disagree. for..in syntax is so much clearer and being able to simply specify the range without having to manually increment makes more sense to me. I would love to see something like Swift's stride in C++.
45.
by RotsiserMho 11y ago
I think the discussion such an article generates has value. I've learned about some nice C++ tools in this thread that I may not have otherwise.
46.
by RotsiserMho 11y ago
No, all are equally prone to errors if a bit in RAM is unexpectedly flipped. My understanding is that ZFS requires more RAM and possibly more CPU than other filesystems and those costs aren't worth it if you're going to use RAM th
47.
by RotsiserMho 11y ago
I've used parts of boost extensively on embedded platforms and cross-platform projects without ever encountering painful runtime bugs. What issues did you have?
48.
by RotsiserMho 11y ago
This can be avoided by using CMake as QtCreator supports it as a project type. CMake isn't exactly a bastion of simplicity however.
49.
by RotsiserMho 11y ago
Couldn't that have been found by turning on the signed-to-unsigned conversion warning?
50.
by RotsiserMho 11y ago
Maybe. No one really wants to make a new C++ without being careful not to make something as convoluted as C++.
51.
by RotsiserMho 11y ago
Someone mentioned using an initializer list, which is a pretty good option if you don't want to be explicit. However, writing a small helper function or class to automatically (and using constexpr, at compile time) convert between diff
52.
by RotsiserMho 11y ago
Depending on your perspective, this can be a strength of C++. It is flexible enough to be used differently as appropriate for each project.
53.
by RotsiserMho 11y ago
You just described std::shared_ptr and std::weak_ptr. I recommend doing some more reading on the subject.
54.
by RotsiserMho 11y ago
In my experience in the embedded world it is at least recognized that RAII should be used. It is fast becoming the exception not to use RAII and now that smart pointers are in the standard, the same goes for them.
55.
by RotsiserMho 11y ago
There's a proposal to include it in C++17. See also: https://www.justsoftwaresolutions.co.uk/cplusplus/standardiz...
56.
by RotsiserMho 11y ago
I would just like to say that I love boost. I believe it leads credibility to a project such as this to know that the wheel wasn't reinvented. I seriously don't understand why there's such an aversion to it. Most of it is hea
57.
by RotsiserMho 11y ago
I so wish it were.
58.
by RotsiserMho 11y ago
I had the same thought and found they have a section of the website devoted to this. Very nice. https://www.touchdevelop.com/docs/creatinginteractivetutoria...
59.
by RotsiserMho 12y ago
I believe the intent is to sync state between Macs, e.g. a MacBook and an iMac.
60.
by RotsiserMho 12y ago
That's not modern C++. This is much less noisy: #include <memory> #include <vector> // ... // circle and shape are user-defined types auto p = make_shared<circle>( 42 ); a

More ›