At a quick skim this looks like they reinvented something very similar to phkmalloc, but they didn’t cite phkmalloc nor include it in their benchmarks.
You'll still probably need the `strcmp` because the pointers won't be the same unless you check for them and make them the same.
You may be thinking about how `eq?` (reference equality) works in scheme. That's usually done by hashing the identifier string. Which is the more general solution to this equality problem.
You're right `virtmach` only works on things that are output from `compile` and maintaining the invariant that virtmach lisp uses those pointers isn't difficult to do in with how the evaluator is presented.
It gives virtmach lisp and scheme different ontology, but I can't think of any practical reason why that would matter other than it makes things a little bit more complicated. But, then again if I'm thinking practically scheme should be using hashed identifiers, and then there's no reason for them to have different ontology and conceptually we're right back where we started with virtmach lisp and scheme using identifiers as objects.
Auditing is only for paying customers of commercial products who've agreed to it in their contract. There's obviously nothing to pay for because the JDK is free. Oracle doesn't even collect contact information when downloading the JDK.
What could be happening there is that an Oracle customer uses their customer account to get access to a non-free JDK, such as an update that isn't offered on the public website because it's past the free update period.
That sentence is specifically about composers of methods in change ringing, where the musical possibilities are tightly constrained by the rules and the physics of ringing large bells. Change ringing is based on permutations constructed by swapping adjacent pairs. (Except for the jump changes that the article is about.) For a “triples” peal on 7 bells the ringers are supposed to ring all 5040 possible permutations. It’s called “triples” because you can make up to 3 swaps at a time; one of the challenges (for example) is to construct a triples peal that only uses triple changes.
The problem in the US is that time zone boundaries very frequently do not match state boundaries.
It’s common for major cities to be located on rivers that are state boundaries, the area around the city uses the same timezone, and one of the states has a timezone boundary in the middle. Indiana has many tz database entries because of this kind of thing.
There are other fun cases like the Navajo Nation in Arizona.
I live in South Dakota, which is one of them—the Mountain/Central timezone boundary within the state follows the Missouri river. (Locals refer to "East River" and "West River" to refer to the two halves of the state. The capital, Pierre, is technically East River, but is right on the banks, almost dead-center.)
https://phk.freebsd.dk/sagas/phkmalloc/
https://cgit.freebsd.org/src/tree/lib/libc/stdlib/malloc.c?h...