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

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!

Davy jones couldn't step on land, and the dirt in the jar symbolizes land

getting the picture to perfectly replicate the image on the screen without it being noticeable that it's just a picture of a screen would be so difficult it would probably be easier to modify the camera instead

blockchain is a totally useless extra bit glued on there. All the real evidence will be the cryptographic signatures added by the hardware manufacturer (which can be faked, but requires extracting the keys from the "security chip" in the camera which may be very difficult)

all the blockchain does at that point is provide a timestamp of "signed hash of the picture+metadata was uploaded on x date" which can easily be done without blockchain too

the czech republic has over 40 thousand police officers and singapore routinely executes drug dealers
So 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

Apparently it's specifically "Players can avoid sequences of precisely timed inputs ("quick time events") or button mashing"