16 bit programming kinda sucked. I caught the tail end of it but my first project was using Win32s so I just had to cherry-pick what I wanted to work on to avoid having to learn it at all. I was fortunate that a Hype Train with a particularly long track was about to leave the station and it was 32 bit. But everyone I worked with or around would wax poetic about what a pain in the ass 16 bit was.
Meanwhile though, the PC memory model really did sort of want memory to be divided into at least a couple of classes and we had to jump through a lot of hoops to deal with that era. Even if I wasn't coding in 16 bit I was still consuming 16 bit games with boot disks.
I was recently noodling around with a retrocoding setup. I have to admit that I did grin a silly grin when I found a set of compile flags for a DOS compiler that caused sizeof(void far*) to return 6 - the first time I'd ever seen it return a non power of two in my life.
Where sublimation is the redirection of socially unacceptable impulses or desires into socially acceptable actions, desublimation refers to the acceptance of these impulses and desires, removing the energies otherwise available for higher goals.
I ran this at one time but it was a bit unstable. I remember corresponding with one of the authors who remarked that it was also attempting to emulate the stability of Windows 95. This was ... oh gawd ... back in 1997 or 1998 I think.
Yes, let's mention Roman Law in relation to British Common Law. The latter derived from the former, but there's a fair distance of about 1,000 years between our three points in time.
For all intents and purposes, every precedent and matter of jurisprudence can be resolved by referring only to Common Law. It would be rather exhausting and absurd to try and reach back past 1066 AD because things have changed, a lot.
Now in terms of forking Roman Law, there are other legal systems which are not directly related or derived from British Common Law. Especially the Napoleonic Code, which influenced Italy, which in turn influenced Catholic Canon Law. So here we have another lineage and a deeper "fork" from Roman Law where British Common Law doesn't really figure.
Also someone commented with a non sequitir about "antidisestablishmentarianism". I'd just like to point out that that word refers to revocation of things like the 1st Amendment and support for the Established Church laws, because it's "anti-dis" double negative.
If you want to talk about the United States' 1st Amendment, "disestablishmentarianism" is the term used to describe how the Founding Fathers set up the States without those meddling bishops.
I’d be interested to see a re-usable implementation of joe's[0] syntax highlighting.[1] The format is powerful enough to allow for the proper highlighting of Python f-strings.[2]
I've actually made several lexers and parsers based on the joe DFA style of parsing. The state and transition syntax was something that I always understood much more easily than the standard tools.
The downside is your rulesets tend to get more verbose and are a little bit harder to structure than they might ideally be in other languages more suited towards the purpose, but I actually think that's an advantage, as it's much easier to reason about every production rule when looking at the code.
It’s just that nesting them arbitrarily is now allowed, right? That shouldn’t matter much for a mere syntax highlighter then. And one could even argue that code that relies on this too much is not really for human consumption.
Also, you can now use the same quote character that encloses an f-string within the {} expressions. That could make them harder to tokenize, because it makes it harder to recognise the end of the string.
This is a good practical example for the less experienced that just because it’s written in rust doesn’t mean it’s magically more secure. Who’s gonna write up the CVE?
But what happens when the in-memory size of objects approaches 2⁶⁴? How to even map such a thing without multi-level page tables?