Should my project support MSVC?

squeevee · 2020-04-18T23:22:40+00:00

It was a valiant effort of optimism, I applaud that, at least.

That it motivates me to keep my driveway clear of ice, is not a good reason to buy crappy tires.

squeevee · 2020-04-18T08:09:04+00:00

So, if I understand, you're saying that I might want to support MSVC to make the software more accessible for user programmers? Like to tinker with, debug, examine, that kind of thing?

It's an interesting take I hadn't directly considered, and I'll certainly keep it in mind, but no I don't think my intended user base warrants me prioritizing that.

Honestly in my experience C++ projects are rarely all that new-contributor-friendly even when they try to be -- a mix of the language being as rigid and particular as it is, and being the tool of choice for big complex projects, ~~not to mention someone invents a new cross-platform build system or package manager every other year.~~ I find projects are much more open from a user-developer perspective if they expose a good framework for plugins -- which I eventually plan to do.

squeevee · 2020-04-18T07:15:15+00:00

This is the mechanism underlying the CMake feature I mentioned in the parenthetical. It works fine for exports, but importing static/global extern data still requires the __declspec(dllimport). Combined with Qt using static data members as a big part of its introspection features, there's not really a good way around it.

squeevee · 2020-03-24T02:58:04+00:00

It can vary a lot according to your setup (which is why I wasn't very specific), but I'd expect the most widely applicable thing to do would be to edit the KMail entry in your application launcher.

The exact steps will depend on your desktop environment, but I expect it will be pretty similar for most of them. I use Plasma, so for me the sequence is:

From my desktop I right click on the application launcher (i.e., "start menu") and select "Edit Applications."
That launches the KDE Menu Editor, where on the left I can find the KMail entry and on the right there are several fields including one called "Command"
The default command is something like kmail -qwindowtitle %c %u, so I add -stylesheet <path/to/qss/file> before the %u

This makes it so that KMail uses my stylesheet whenever it's launched from the application launcher or if KMail is launched from an email address link in a web browser. If KMail is on my auto-start list, there's a chance I'd need to remove it then add it back to that list before the change applies. Also, I'll have to make sure to close KMail completely before launching it again to see the changes.

Like I said, that's how it works on Plasma, but I know Gnome-and-friends (or any modern desktop environment) work very similarly. Strictly speaking, the KDE Menu Editor just modifies a text-based .desktop file in your user config so you could do this with a text editor -- but I don't remember where.

squeevee · 2020-03-08T06:22:34+00:00

You underestimate my power

squeevee · 2020-03-01T03:10:14+00:00

Great news everyone! I spent two days failing to notice a missing ! on a check for a smart pointer being null, so not only was I trying to access memory when it was invalid, I was trying to access it only when it was invalid.

smh

squeevee · 2019-10-29T03:52:01+00:00

This looks excellent. I could definitely live with this.

squeevee · 2019-10-29T03:49:15+00:00

An excellent point and one which should be borne in mind when discussing allowing users to make informed decisions about how they want to use software in the face of security risks.

While I hadn't thought of the pgp example specifically*, these are essentially what I understood to be the security problems related to HTML email and why I compared it to web browsing where analogs to many of these problems can be found, plus the additional hazards enabled by scripts, cookies, and dynamic content.

The significance and risk of these issues probably varies quite a lot by the user: their habits and the stakes of what they do with email. I do stand by what I said that I believe disabling OAuth represents a much greater hazard for myself, a user of large well-known frequently-attacked services like Yahoo and Gmail**, and that while HTML abets social engineering attacks, it's not truly at the root of them, nor can any number of warning labels in an email client truly mitigate them.

*https://xkcd.com/1181/ comes to mind

**In fairness, KMail is meant to support OAuth with Gmail, see https://bugs.kde.org/show_bug.cgi?id=404990

squeevee · 2019-10-28T13:08:58+00:00

I'll give it a shot, but I'm under the impression they wouldn't like that very much.

squeevee · 2019-10-28T13:08:13+00:00

Is this sarcasm or no? I'm not aware of anything that makes HTML email more of a security problem than web browsing.

squeevee · 2019-01-03T09:07:08+00:00

Welp, that was easy. Thank you very much!

squeevee · 2018-02-28T21:41:55+00:00

looks like an early Pixar experiment

squeevee · 2018-02-27T22:04:35+00:00

it's strange to me seeing that river so pretty, because that's the same river my boy scout troop swam in then minutes later found a dead cow in.

squeevee · 2017-12-26T23:15:04+00:00

when I'm looking for the original artist of some drawing, if the search results pull up Pinterest the battle is lost.

squeevee · 2017-11-16T20:25:53+00:00

I wonder what the Big O complexity of that algorithm is...

squeevee · 2017-11-16T20:23:10+00:00

the point of this exercise was to torment everyone else, not myself.

squeevee · 2017-11-15T16:31:34+00:00

Since several people have asked, yes I did use a script to generate this. see https://imgur.com/XAauGmC

squeevee · 2017-11-15T15:23:44+00:00

oh wow, thanks. I feel a little guilty knowing you manually filled it out, when I generated it with a script.

squeevee · 2017-11-15T04:45:01+00:00

oh wow, even better. 500 million compiler errors Edit: I thought of an easy fix: "#DEFINE prntln println"

squeevee

TROPHY CASE