Assuming you're a native English speaker, why is "whiskers" unfamiliar?
If not referring to the beard as a whole, how else would you reference the facial hair - whiskers is less of a mouthful than any other term.
574 karma · joined March 23, 2019
If not referring to the beard as a whole, how else would you reference the facial hair - whiskers is less of a mouthful than any other term.
The only 'non modern' bits are 'Michaelmas' (which I know is a Christianity related date), and 'undistinguishable' where I'd use 'indistinguishable'. So the note about the student being quizzed to translate to 'modern English' seems moot as it is modern English.
However, I'm English, so a number of the terms are immediately obvious.
I obvious know who the Lord Chancellor is (as the role still exists); as do the Inns of Court, being where Barristers receive their initial training. So I would suggest it is more a case of needing specific cultural knowledge, than needing enhanced language skills.
Bleak House: https://www.gutenberg.org/files/1023/1023-h/1023-h.htm
As to the rest of the initial 7 paragraphs.
In P2, I had to look up "aits" (islands); otherwise they are all of no issue other than the length of the sentences, occasionally requiring me to reread a few phrases.
Basically Dickens is modern English, with a few archaic words being used.
i.e. possibly Intel having some protection (copyright?) over its assembly mnemonics and register names.
The build kit for CDOS-68k 1.2 (aka FlexOS 68k) is available ob Gaby's site.
I worked for an OEM in the 90s, and we used FlexOS 286 (and 386) ver 2.2/2.3 on some custom systems, including an ePOS system.
Apart from not being able to taste coffee, I also could not taste freshly ground black pepper, fresh spicy peppers, nor Tabasco sauce.
I could only feel the effects of the capsaicin at the back of my throat after having swallowed.
So it is a southern English habit, not a British one. The other parts of England are more direct, and will use more obvious phrasing. Similarly the other parts of Britain will be more direct.
i.e., either of these forms:
foo * volatile p;
foo * _Atomic p;
The task of walking (or measuring) the whole of England's coastline is made a bit more difficult by the existence of various islands classed as part of England.
e.g. Isle of Wight, St. Mary's Island, Coquet Island, Lindisfarne, the other Farne islands, etc.
The UK pint is 568ml, apparently a US pint is 473 ml.
https://www.airs.com/blog/archives/428
The use of 'const' in C is very much a mixed blessing; I certainly have experience of the 'const poisoning' issue. Possibly it would have been better as a storage class.
For bool, yes it was a useful addition. Especially for the cases where old code would have something like:
#define FLAG_A 1u
#define FLAG_B 2u
int has_flag_B (something *some) { return some->field & FLAG_B; }
An 'aggr' is equivalent to C 'struct' combined with 'typedef', and an 'adt' is an 'aggr' having methods.
[1] https://en.wikipedia.org/wiki/Alef_(programming_language)
That was using the Claude Sonnet 4.5 model, I wonder if using the Opus 4.5 model would have managed to avoid that.
That the perpetrators may turn out to be foreign agents is neither here nor there, only if they were diplomatic staff would it not be a domestic policing issue. However the UK police have largely withdrawn from certain areas, and this would simply be another symptom.
High Court action suggests there was a civil case pursuing the perpetrators (or their principals), rather than a criminal case. With a properly functioning police system, that should not be necessary.
Kahn is the PCC for London, he sets their priorities.
Nothing will improve as long as Khan is Mayor, and may not even if he is replaced.
Anyway, MI6 (SIS) is the overseas spies, MI5 is the domestic spy agency.
As to 3g, it is largely switched off here, and I understand most of the rest of the world is also disabling it.
However it does not remove images from messages, it just disables certain automatic helpers - e.g. link previews etc.
One can still send photos, etc without any issue.
I allowed (e.g.) a syntax like:
M0, M1, M2, M3, M4: con (1<<iota);
I'm trying to drag one program at $employer up to C99 (plus C11 _Generic), so I can then subsequently drag it to the bits of C23 which GCC 13 supports.
This all takes times, and having to convince colleagues during code reviews.
What C23 has done is authorise some of the extensions which GCC has had for some time as legitimate things (typeof, etc).
However the ability to adopt is also limited by what third party linters in use at $employer may also support.
For example, I'm maintaining some 20 year old C code, which the employer adopted around 10 years ago. It will likely stay in use at least until the current product is replaced, whenever that may be.
(https://news.ycombinator.com/item?id=46243298)
Which rather suggests to me that such a scheme, but generated by the compiler, should have a similar performance to said "Normal Functions" and hence similar to his preferred lambda form.
Since his benchmark environment is so unwieldy, I may have a go at extracting those two code sets to a standalone environment, and measure them so see...
e.g. ch, th, sh, wr, oo; etc
See https://en.wikipedia.org/wiki/Digraph_(orthography)#English
That page lists 15 such over and above the doubled letters.
All through middle and high school, so for 7 years from around 10 to 16. It did become one eventually in primary school, so probably the last 2 or 3 years there.
Yes it did exist. It just wasn't mentioned in the original K&R book.
See this page of a memo from November 78, passing and returning structs was supported. When I learn C on a Unix system, there was a copy of this memo in the printed papers section.
https://www.nokia.com/bell-labs/about/dennis-m-ritchie/cchan...
There is a bark of an Englifh tree, which I have found by experience to be a powerful aftringent, and very efficacious in curing aguifh [agues] and intermitting diforders.
My curiofity prompted me to look into the difpenfatories and books of botany, and examine what they faid concerning it; but there it exifted only by name. I could not find, that it hath, or ever had, any place in pharmacy, or any fuch qualities, as I fufpected afcribed to it by the botanifts.
i.e. Englifh => English; aftringent => astringent; aguifh => aguish; diforders => disorders; curiofity => curiosity; difpenfatories => dispensatories; faid => said; exifted => existed; fuch => such; fufpected afcribed => suspected ascribed; botanifts => botanists
The other case has been miscommunication over phone or email to someone actually requesting to change billing provider. Or error on the part of the potential customer.
I've had a bill from some random billing provider. In my case it is common for folks newly arriving in the block of flats to get the digits of the address transposed. Due to them using the common English convention, whereas the part of Scotland I'm in uses a different convention.
I believe the High-C compiler with this support is still available, for modern embedded CPUs.
There they allowed nested functions, but also what they termed "full function values", being a form of fat pointer. Certainly I came across it in High-C v1.7 in 1990, and the full manual for an earlier version (1.2?) from around '85 can be found on Bitsavers.
It had a syntax like:
extern void Quick_sort(
int Lo, int Hi, int Compare(int a, int b)!,
void Swap(int a,int b)!
);
static Sort_private_table() {
Entry Entries[100];
int Compare(int a,int b) {
return Entries[a] < Entries[b];
}
void Swap(int a,int b) {
Entry Temp = Entries[a];
Entries[a] = Entries[b];
Entries[b] = Temp;
}
...
Quick_sort(1,100,Compare,Swap);
}
https://archive.org/download/Yoshizuki_UnRenamed_Files__D-V/...