I agree with FreeMan here. If you click on anything it will prompt to save. Change current cell or look at a different sheet. It remembers your position.
Heck, just look at it crosswise and it may prompt you to save...
I guess over prompting is better than not prompting often enough & risking losing things, but it really does make you sit back and say "woah! Did I actually change anything??"
I often have 5+ workbooks open at once and remembering if I did actually change something in one of them... I often end up clicking "No" on all or "Yes" on all without thinking.
2019 already includes some bullshit cloud sharing nonsense that seems to threaten the sanctity of your IDE. I am scared that 2022 will be more "cloud IDE".
oh you're being silly. Has Big Bill ever led us astray with his benevolent and loving guiding hand? He liberated us from those nasty people in Sun and those radical penugin heads.
The History of the Berkeley Software Distribution begins in the 1970s.
== 1BSD (PDP-11) ==
The earliest distributions of Unix from Bell Labs in the 1970s included the source code to the operating system, allowing researchers at universities to modify and extend Unix. The operating system arrived at Berkeley in 1974, at the request of computer science professor Bob Fabry who had been on the program committee for the Symposium on Operating Systems Principles where Unix was first presented. A PDP-11/45 was bought to run the system, but for budgetary reasons, this machine was shared with the ...
@HackSlash Just googled and read that. I think there are several flaws in their logic. Passing everything by reference doesn't mean that everything becomes a "big blob of global state". The article dismisses encapsulation as worthless, but it's the very means by which state is controlled.
Also, many of the arguments simply don't apply to C# to the same extent as they would to Java. C# has great support for immutables, I make any and every type I can immutable.
Overall the article comes across as FP zealotry IMO
@feeds Either:
A) a US map as drawn by a 2021 high school or college graduate, or
B) a US map drawn by someone who was scrolling around google maps and said, "Wait, there's a Brooklyn, IA???"
huh... Guess that makes sense. Not inherently obvious based on the picture. (pun only slightly intended...)
So a class hierarchy of: Machine -> Vehicle -> Truck -> Pickup would execute 4 constructors for every new Pickup built. (assuming they all have non-empty constructors)
The ordering of topics in this particular online training I'm going through strikes me as a bit odd, but it seems to be really sinking in better than the last time I tried to get started. I almost feel like I could open up the Duck's belly and have a clue what I was looking at.
@HackSlash didja link to the VB docs intentionally? I'm working through a C# tutorial...
They're probably basically the same thing, though, I'd imagine
@M.Doerner thank you! I'm copy/pasting that verbatim into my notes.
looking through the C# inheritance page on MSDN, it makes reference to System.IEquatable<T>. I know I haven't gotten there yet in this training, but I've seen lots of references posted here with <something>. What does that angle bracket notation mean on an interface?
So IEquatable<T> is an interface for equating variables of type <T>, where T is simply a place holder for "some type or another". Unless, of course, you've actually defined a class T, which would be somewhat foolish and exceedingly confusing.
cool. thanks for the mini lesson. I'm sure I'll get more into it in the next few days.