Anyway I think this interpretation means a C standard library implementation needs different implementations of scanf and strtoul to be conformant to both C23 and C17 and earlier.
My displeasure is imeasurable and my day is ruined.
:drgn_dizzy:
Anyway I think this interpretation means a C standard library implementation needs different implementations of scanf and strtoul to be conformant to both C23 and C17 and earlier.
My displeasure is imeasurable and my day is ruined.
:drgn_dizzy:
So I have set of interesting C corner cases…
Consult 7.24.1.7 of WG14 N3220, concering “The strtol, strtoll, strtoul, and strtoull functions” and then look at the following:
// C23 // In all of the following assume errno is initially 0 // Unambiguous r = strtoul("0", &endp, 0) r = strtoul("0", &endp, 2) r = strtoul("0", &endp, 16) // -> strcmp(endp, "") == 0, r = 0, errno = 0; r = strtoul("0b0", &endp, 0) r = strtoul("0x0", &endp, 0) r = strtoul("0b0", &endp, 2) r = strtoul("0x0", &endp, 16) // -> strcmp(endp, "") == 0, r = 0, errno = 0; // The following are ambiguous, however. // What is the correct output for each of these? strtoul("0b", &endp, 0) strtoul("0b", &endp, 2) // -> strcmp(endp, "b") == 0, r = 0, errno = 0;, or // -> errno = ERANGE strtoul("0x", &endp, 0) strtoul("0x", &endp, 16) // -> strcmp(endp, "x") == 0, r = 0, errno = 0;, or // -> errno = ERANGENote: in versions of C prior to C23, the following are unambiguous (the language permitting the 0b prefix was added in C23). Depending upon interpretation, in C23 strtoul may reject inputs that were considered acceptible in in previous versions of the standard
strtoul("0b", &endp, 0) strtoul("0b", &endp, 2) // -> strcmp(endp, "b") == 0, r = 0, errno = 0;If the local Bäckspace was a real thing I could go there and bake up a load of Franzbrötchen right about now…
Tired: Going to the hackspace to work on your programming project
Wired: Going to the hackspace to work on your electronics project
Un-Wired: Going to the Bäckspace to work on your baking project
@alina its red eurostar! its an imposter!!
(the artist formerly known as thalys)
The “Ohh its coming to Berlin - aww its already sold out” rollercoaster :(
This is just an unreasonably cool bit of imagery, and you’re telling me its from an opera?!
@yassie_j @rail_ @jeder its kinda funny, the traditional UK train safety system (AWS+TPWS) is a kinda cobbled together mess, the speed limit is higher (125mph 201km/h) and the lines are very intensively worked yet the UK railways are among the very safest in Europe.
The most probable answer for how this happened IMO is “They put the Rail Accident Investigation Branch and the Air Accident Investigation Branch in the same office”
@trwnh @julian @thisismissem @silverpill In any case I don’t think “origin based authentication” for fetches is a good idea for the simple reason that its not, to my knowledge, what implementations do today and it strongly risks leaking private posts. Certainly what the ActivityPub spec heavily implies if not outright says is that anything fetchable via a given identity should be visible to that identity, and I’m generally iffy on the idea of trying to make implementations execute potentially complicated ACLs on behalf of each other; that way is certainly a security disaster.
So that then leaves us with the question: is leaking the identity of the actor who has pasted a post’s URL into their instance’s search bar a real issue?
@thisismissem @blogdiva @mttaggart @mwl we’re currently at 50% utilisation. We’ve already exhausted a lot of the “good” ones (pray help you if your country’s name starts with an S); if they were permanently reserved we’d run out and run into issues.
Typically they become Transitionally Reserved for 50 years, though it can be shortened to 5 years with good reason
someone who is good at ram please help me budget this. my computer is dying.
immigrant | they/them | software engineer in card paymentsliker of ISO 8583, the 8051, ASN.1 and EBCDIC.I wrote the ActivityPub initial draft, so this social network is in some way my fault.Formerly @erincandescent@queer.af Instance admin, queer.af (2018-07 - 2024-02, RIP)
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.