|
I can't get over wordpad being called "much-loved".
I don't think I even know anyone who's ever used it -- except by accident, maybe.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I use it give a quick look at binary files, and to read text files that don't believe in CR.
|
|
|
|
|
GenJerDan wrote: I use it give a quick look at binary files
I got the Notepad++ Hex Editor extension for that, because I couldn't find the editor I used to use (primarily because I've forgotten what it's called, so I wasn't successful searching for it).GenJerDan wrote: text files that don't believe in CR
Now that is a pain (yes, DooM wad makers, I'm looking at you), so I associate the txt extension with either TextPad or Notepad++ on my laptops (and just swear about it, on the desktops).
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
The future of the next 46 billion devices So... they are moving to Linux?
|
|
|
|
|
What a shame that this article is on a site that I've blocked for infringing the law.
I really would have enjoyed reading the words of such a great oracle and vanguard of technological innovation.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Yeah, sorry about that. I am trying to wean myself off posting anything from The Verge (and Engadget, and Techcrunch), but sometimes they're the only ones with an article on a topic.
TTFN - Kent
|
|
|
|
|
Did me a favour, in this case, because if I could have read it, I would have read it, and it no doubt would have ruined my day.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Is he retiring early...
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
$42 million last year. I'd be booking off early.
TTFN - Kent
|
|
|
|
|
“When deep space exploration ramps up, it'll be the corporations that name everything, the IBM Stellar Sphere, the Microsoft Galaxy, Planet Starbucks.” -- The Narrator..Fight Club (1999)
Fight Club - Insomnia.wmv - YouTube
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
|
Kinda cool, but kill me now if I'm forced to use it. 
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
TheGreatAndPowerfulOz wrote: if I'm forced to use it
Wait.
Do you mean Win 3.11?
Or, do you mean dotnet Core?
Dotnet core really is cool. It is amazingly flexible and you still get to use C#!
|
|
|
|
|
Win 3.11
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
hanselman goes all the way with what not to do ..... ........ ..... ... ......
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
In this blog post, I’d like to show you how I could quickly improve my old project with Modern C++. Thanks to using the newest compilers and free code analysis checkers you can cover and modernise a lot of code. I thought "real" C++ developers eschewed IDEs?
Yes, I just really wanted to use eschewed today. Probably inappropriately, but hopefully you understand anyway. I know many developers are quite keen on proper English usage.
|
|
|
|
|
How does adding/removing noexcept in C++ work in practice? It gave immediate flashbacks to the horror that Java's exception specifications became in any larger code base if you did anything to change the exception behavior of a low level function.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
You're telling the compiler that either this function won't throw exceptions, or that the program should crash if it throws any exceptions. It lets the compiler optimize the code.
|
|
|
|
|
And when you've got something like:
void Function1() noexcept
{
Function2();
}
void Function2() noexcept
{
}
...and then at some point in the future you change Function2 to throw an exception, do you then end up having to ether update functions everywhere up the call chain propagating the change, or have a zillion new warnings (errors?) cluttering up your codebase and that of anything that consumes it. Javaland ended up doing a lot of grotesque contortions to avoid breaking API specifications by changing what exceptions were thrown. This smells like a lighter weight version of the same thing.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
In the Points of Interest section at the end of this article[^], I mention why I loathe noexcept. It should never have been allowed in any case, for the same reason that
inline has been effectively repurposedregister has been deleted- there is a proposal to remove
volatile
That is, telling the compiler what to do (inline, register) clutters the language with noise, and compilers that introduce errors during optimization (hence the need for volatile) should be taken out and shot.
A noexcept function can call functions that throw. But if one of them throws, abort will get invoked.
|
|
|
|
|
Greg Utas wrote: there is a proposal to remove volatile
People working in embedded land have got to be loving that one.  
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
It's a C++20 proposal, and I don't think it's a problem provided that the compiler does exactly as it's 🐘ing told. I've never used volatile and haven't read the proposal, but if some weenie involved with C++ standards submitted it, I must assume (perhaps mistakenly) that it's feasible.
|
|
|
|
|
volatile is deceptive. It has a very narrow legitimate use case and even then, there are better, safer, solutions.
|
|
|
|
|
Out of curiosity, what is the safer solution to keep the compiler from thinking it can optimize a memory read to a cached value in a register when the value at the address is being updated by something outside of the program the compiler knows about?
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
You have identified the legitimate, narrow use case. However, even that is problematic, especially with modern CPUs (For instance, if the value in question is not memory aligned, especially true with structs. Also, the CPU itself may cache the value(s).)
The problem arises is devs thinking volatile guarantees atomicity and/or is a reliable way to do synchronization.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
