Yeah, it's in my edit I realized the same thing. I'm thinking it doesn't actually really make sense and the real reason is more "the specific way C does it causes a lot of problems so we're not poking syntax like that with a 10 foot pole" + "it makes writing the parser easier" + maybe a bit of "it makes grepping easier"
So I think it's still probably unclear to people why "mix of keywords and identifiers" is bad: it means any new keyword could break backwards compatibility because someone could have already named a type the same thing as that new keyword.
This syntax puts type identifiers in the very prominent position of "generic fresh statement after semicolon or newline"
..though I've spent like 10 minutes thinking about this and now it's again not making sense to me. Isn't the very common plain "already_existing_variable = 5" also causing the same problem? We'd have to go back to cobol style "SET foo = 5" for everything to actually make it not an issue
yep, it's almost all banana pi, and at least 4 different 'models' of it it seems. But the word is also used in some string processing tests and as an example comment of how suffix arrays work..
And most of those cases are of course using the word sarcastically
The next function to implement is called, amazingly, next(); its job is to
move the iterator forward to the next position in the sequence.
if (lc->sync == NOSYNC)
for (i = lc->header.nr_regions; i < lc->region_count; i++)
/* FIXME: amazingly inefficient */
log_set_bit(lc, lc->clean_bits, i);
else
for (i = lc->header.nr_regions; i < lc->region_count; i++)
/* FIXME: amazingly inefficient */
log_clear_bit(lc, lc->clean_bits, i);
/*
* Amazingly, if ehv_bc_tty_open() returns an error code, the tty layer will
* still call this function to close the tty device. So we can't assume that
* the tty port has been initialized.
*/
* this header was blatantly ripped from netfilter_ipv4.h
* it's amazing what adding a bunch of 6s can do =8^)
/*
* I studied different documents and many live PROMs both from 2.30
* family and 3.xx versions. I came to the amazing conclusion: there is
* absolutely no way to route interrupts in IIep systems relying on
* information which PROM presents. We must hardcode interrupt routing
* schematics. And this actually sucks. -- zaitcev 1999/05/12
* corresponding ABS_X and ABS_Y events. This turns the Twiddler into a game
* controller with amazing 18 buttons :-)
* In an amazing feat of design, the Enhanced Features Register (EFR)
* shares the address of the Interrupt Identification Register (IIR).
* Access to EFR is switched on by writing a magic value (0xbf) to the
* Line Control Register (LCR). Any interrupt firing during this time will
* see the EFR where it expects the IIR to be, leading to
* "Unexpected interrupt" messages.
* Thanks BUGabundo and Malmostoso for your amazing help!
the czech republic has over 40 thousand police officers and singapore routinely executes drug dealersSo while it may be technically true in that no actual violence was involved in the latest changes of government system, the threat of violence is always there
When you get to the informing policy stage, much "harder" sciences like pharmacology also get the same treatment of using completely disproven crap to inform drug policy. If you look hard enough, you can almost always find a study that agrees with your wildest biases and a PhD (often even in "good standing") who stands behind it and agrees with you.
That there are 500 papers that find the exact opposite of your conclusion is not much of an issue when you're acting in bad faith and have a friendly media outlet to voice your views
it does kinda fit in that if you forced people to learn linux, the basic stuff most people do should in the end not be much more difficult than windows (assuming you don't run into more bugs)
but that would never happen unless a "linux revolution" was already in full swing
My major version updates on 2 computers with linux mint in the past few years have been just one click, wait, reboot when prompted, everything works and you barely even notice that anything changed. Though maybe I've just been lucky
though the rest of the video's takes on the linux experience for new users seems pretty accurate to me (lol downloading an application and using it requires at least a manual chmod +x and that's the best case scenario. Maybe there's a distro that has a solution but I have doubts (and "have everything you could possibly need in the package manager" is obviously a nonstarter))
But the community parts seem odd to me:
Is "just disable secure boot" a bad take? Has someone been holding everyone out on a better solution?
and
The only way linux is going to change is when money and development power is given to major dekstop Linux projects. It's time to stop wasting time on customization or packaging
is just.. sure, herd all the cats into one place, make them all work together in harmony, and summon 500 million dollars out of thin air to wrap it all together. Instead of writing bash scripts everyone should be praying to gabe newell to save us lol
.44 magnum is barely on par with an intermediate rifle round like 5.56 against large game. And that's before considering the massively lower felt recoil or the fact that a rifle is much easier to aim
openAI tried to remove the mexico filter but they just can't. The AI is hopelessly addicted to that sepia tone