How things work around here:
Willow: stare
Me: “You had a pretzel, and Corky’s too. I think you can let me have a cookie or two.”
Corky: “Did someone call about food?”
Me: Eats third cookie
An orange in an apple orchard
How things work around here:
Willow: stare
Me: “You had a pretzel, and Corky’s too. I think you can let me have a cookie or two.”
Corky: “Did someone call about food?”
Me: Eats third cookie
Normally I don’t make meatloaf. But this time I decided to solve the main logistics problem: giving myself a good head start on cooking time. Plus two pounds makes a ton of meatloaf.
For reasons unknown to me: I seem incapable of remembering to warm up the meat in advance, so that I don’t end up with a frozen slab of meat for a mixing hand. But that’s a chronic problem that remains heat after year, lol.
Willow was pretty convinced that this meal should be shared, but had to settle for her own meat and gravy bits after human’s dinner.
Last night, I was really tied. Misty was kind of looking at me with concern in her eyes as if to say, “Don’t fall out of the chair human, you’ll die if you hit the floor that tired.”
Tonight on the other hand: she’s looking as if to say: “Why you no bring me another treat.”
Oh, alright lit’ Mis’ I’ll go and get a treat, lol.
New safety rules in C++ Core Check
While the for loop part may be a bit spotty, in the sense you should be paying attention and know which you want when writing the statement. I have to admit I would have liked the auto thing.
I’ve mainly relied on C++14 since about 2016 for my C++ use whenever possible, and sometimes newer because of standard library. While catching up wasn’t as painful as I thought, aside from how long it’s taken for C++17 to trickle through various Linux distributions, there were a few things I found myself watching closer.
One of these was the way auto typing copes with references. I learned pretty quickly to watch my syntax when using auto. If a real warning was available: it would have been much faster to notice the distinction. In my code, you’ll usually see auto used when the type would be redundant salt. But we usually want our sugars to not to have unintended pains, lol.
The code samples on the switch/case part also makes me remember just how verbose C’s simple switch/case statements are by today’s standards. Damn it, now my kind is flashing to SML….lol
Surface Duo postures: Every bend and fold you need to know
For some years, I’ve thought it would probably be awesome sauce if you took two tablets and put them in a book like case side by side, and made some kind of software pipe between them for opening apps and sharing via intents.
Microsoft’s Surface Duo definitely represents something much more complete and natural. And sadly just as expensive, or more. But it’s an actual product you can sell your left nut or right tit for. So there is that 🤣.
I would love to see more devices like this. Both in the Duo’s size that can bridge between a phone and a tablet, and something closer to a tablet than a phone.
In various bits of code: I’ve been using these headers to solve the “__cplusplus says yeah, but actually compiling says go to hell” problems. Because sometimes the macro tells you one thing and actually trying to preprocess and link makes naughty hand gestures on the systems I encounter.
Finally, I’ve gotten around to sticking these in their own repo.
Which is much nicer than going: “Which project did I last update that in?”