I agree that this could be viewed as bad. However, this is way less of an issue than Google taking choice away, which is what the great-grandparent comment was about.
> you get the natural numbers, the integers, ... but even before the natural numbers come the prime numbers. Primes are the most fundamental set of numbers in mathematics, from which you can generate the natural numbers.
I don't really see how you can define prime numbers before the natural numbers.
The set of natural numbers contains the prime numbers.
The set of prime numbers doesn't contain the natural numbers, but every natural number > 1 can be generated/described as a product of prime numbers (fundamental theorem of arithmetic).
Maybe my terminology was incorrect, I'm not good at maths, but that's what I meant.
No, it isn't, really. It's internally buffered. Most calls to getchar do not read anything, they just return a pointer to the next character in an already read buffer.
> No, it isn't, really. It's internally buffered. Most calls to getchar do not read anything, they just return a pointer to the next character in an already read buffer.
Not only that, it's permissible for getchar() to be implemented as a macro, so you might even avoid an actual function call too.
It’s explicitly permissible for every C library function to be implemented as a macro (as well as an identically-named function in case you need the address), but they must preserve the illusion by evaluating every argument exactly once. You were probably thinking of getc(fp), which is special [and different from fgetc(fp)] in that it’s additionally allowed to evaluate fp multiple times: getchar() takes no arguments, so it doesn’t matter either way. Yes, the naming is confusing.
... In which case, getchar_unlocked() from POSIX 1993 and later is your friend, when used together with flockfile() / funlockfile(). Or, well, as much of a friend as an explicit locking function can ever be. (Over in Windows land, MSVC used to have a non-threaded static C runtime as well, which doesn’t strike me as a stupid idea for this kind of simple program, but for some reason musl on Linux doesn’t do non-threaded builds.)
> They also say openly that they cooperate with everyone to take down certain illegal material from channels and open groups.
Can you provide a link for that? I could only find that they'd hand over your personal account info if they get a court order claiming that you're a terror suspect (from https://telegram.org/privacy):
> 8.3. Law Enforcement Authorities
> If Telegram receives a court order that confirms you're a terror suspect, we may disclose your IP address and phone number to the relevant authorities. So far, this has never happened. When it does, we will include it in a semiannual transparency report published at: https://t.me/transparency.
> Can you provide a link for that? I could only find that they'd hand over your personal account info if they get a court order claiming that you're a terror suspect (from https://telegram.org/privacy):
Maybe I can:
First a note: "your personal account info" while somewhat correct makes it sound broader than what the paragraph below says: "your IP address and phone number".
That said, here is one that that at least partially confirms this:
> "Our mission is to provide a secure means of communication that works everywhere on the planet. In order to do that...we have to process legitimate requests to take down illegal public content (sticker sets, bots, and channels) within the app."
(emphasis mine)
There seems to be more in the search results here (if you have access to kagi, if not apply now:)
What does "targeting any glibc version" mean? Is it the solution to the problem where you have to compile on an ancient Debian version to produce a binary that works on all Linux distributions because it otherwise links to too-new symbol versions in glibc?
Can I use that outside of Zig, for compiling C++ code?
The correct solution for that is to just cross compile to whatever older CPU you want and target a sysroot that has a base image of whatever older glibc you wanted: you don't need to actually compile on the older device...
