while(status != SUCCESS) {
status = syscall(...);
// do something with status
}782 karma · joined November 27, 2018
while(status != SUCCESS) {
status = syscall(...);
// do something with status
}However it turned out that you could rename them .bat or .cmd and they would execute just fine.
I think Doom 2 multiplayer was extra fun because of the added need to be aware not just of in-game enemies but also the need to be aware of the teacher and be ready to instantly quit at any moment.
It used to be that even accepted bugs and paid bounties would be publically disclosed. It helped me learn a ton just from reading the (partially redacted) bug reports. Over time they became more and more redacted until they were left entirely pointless.
To mark a bug as N/A, declare it 'not fix' but then say also it can't be disclosed is precisely why responsible disclosure is a thing. Companies can't have their cake and eat it.
Here's the BBC's "cyber attacks" page: https://www.bbc.co.uk/news/topics/cp3mvpdp1r2t/cyber-attacks
Predictably the very first picture is a guy in a hoodie. In all the stories they clearly struggle for images. They picture instead the targets or in some cases resort to people holding laptops or phones or this garbage: https://www.bbc.co.uk/news/uk-england-essex-48351510
In the US? Maybe, jury is still out: https://text.npr.org/s.php?sId=696709717
The same argument could be made for rainforest deforestation, saying it's a good thing because it's feeding the poor!
Nonsense, tax the externality and then give back and support the worst affected through taxation or aid if needed. Inequality is at a record high, perhaps it wouldn't be so high if we made everything more expensive and then taxed the rich to pay for it.
In this case it drowns out discussion of the article because the article is terrible. It doesn't start with the code as it would look like with loops, but instead says "Let's pretend you don't have loops" and then refactors the logic which has nothing to do with loops, then puts the loop back in.
The same refactoring would be just as clear with loops, and in fact the version without the refactor might be even more clear.
A static function which is only called from a single place isn't always more clear than having the logic inside the loop, especially if all that is left from the original function is the loop.
I'm a professional software developer and I open excel every day.
Let's say someone emails me a list of figures and I want to quickly add them up?
Sure, I could write an incantation in awk but I can't then see if it's wrong because maybe on one row they 'accidentally' put an extra blank column in before the number by marking it with a letter, or there being an extra tab or whatever might cause that.
It's far quicker and less error prone to pop open excel, paste it in and then sum the column, and most importantly there is clear visual feedback if that doesn't work. In awk or a programming environment you'd just either get an incorrect figure and never know it was incorrect, or you'd get an error (e.g. trying to add a letter and number) and then have to debug what should have been an instant thing.
Excel shines for doing one-shot data processing.
If you "manage" your settings to block everything it'll just be back next time.
As a consequence, I haven't read a techcrunch article since June 2018.
But they didn't, that's a detail you can't just conveniently drop to argue in the abstract.
I suspect people are upvoting this based on the headline alone because it's not a well written essay and doesn't back up its assertions.
If the hardware itself has vulnerabilities it could be used to mask the cheat loading and make it harder for the host PCs to detect if any of that side-loading is happening.
(2)Subject to subsection (3) below, this section applies to any article which has a blade or is sharply pointed except a folding pocketknife.
(3)This section applies to a folding pocketknife if the cutting edge of its blade exceeds 3 inches.
The three inches is clarification around folded pocketknives, it's not blanket authorisation to carry knives less than that length.
Phrasing it as, "The COO was a woman who changed her mind often enough" draws a lot more attention to her gender rather than the issue of lack of direction.
I'm not normally one to point out this kind of thing, but it stuck out to me too.