Rust will yell at you if you use specific magic numbers like these edit: yes, 0xCAFEBABE is a warning but 0xFEEDFACE is not: 3405691582 https://github.com/rust-lang/rust/blob/d0ea1d767925d53b2230e...
What a meme language.
0xCAFEBABE & 0xFEEDFACE (2003)
121–126 of 126 posts
Re: 0xCAFEBABE & 0xFEEDFACE (2003)
#122Earlier quoted context omitted.
That says all I need to know about the community.
Really? Current mainstream political shibboleths are more important than for example their stance on module versioning or on whether C code should have a right to exist?
>right to exist
we must secure the existence of C code and a future for node children
Re: 0xCAFEBABE & 0xFEEDFACE (2003)
#123Earlier quoted context omitted.
Kind of low-key hilarious that someone thought this was a serious enough issue to actually submit that code. I wonder if there is a written spec that helps to judge which integers should be considered "problematic" and which ones aren't.
Not just that, but they also wrote the numbers in decimal - they didn't even want them in the code as an example of what not to do. Maybe someone was having too much fun and got carried away, but what an odd sense of humor.
It’s not humor.
It’s religion for the irreligious.
Re: 0xCAFEBABE & 0xFEEDFACE (2003)
#124Earlier quoted context omitted.
Because every word and every combination of hexadecimal characters is "potentially offensive", and because those prone to taking offense are perfectly capable of finding it anywhere that they want to anyway?
> Because every word and every combination of hexadecimal characters is "potentially offensive" No they are not. There are plenty of harmless combinations, like 0x1235679a or other with English words like 0xcafebad0. Offensive was a bit of a strong word here, I was mostly paraphrasing the dictionary. However in male-dominated field, using an objectifying word targeting 50% of the world population is definitely in poo…
Krssst wrote:
> No they are not. There are plenty of harmless combinations, like 0x1235679a or
> other with English words like 0xcafebad0.
and 0xcafed00d?
Re: 0xCAFEBABE & 0xFEEDFACE (2003)
#125Earlier quoted context omitted.
Not just that, but they also wrote the numbers in decimal - they didn't even want them in the code as an example of what not to do. Maybe someone was having too much fun and got carried away, but what an odd sense of humor.
> wrote the numbers in decimal Maybe they just didn't want the checker to flag itself. I remember there was a similar check inside Google, where any file containing the words "DO NOT SUBMIT" will cause the presubmit check to fail. Naturally the presubmit checker needs to look for that string, but it couldn't trivially include the string as-is because that would prevent the presubmit checker from being submitted. (Mot…
But it's clippy, you can just annotate it with an #[allow(problematic_constants)]
Re: 0xCAFEBABE & 0xFEEDFACE (2003)
#126Earlier quoted context omitted.
But why?
https://www.oxfordlearnersdictionaries.com/definition/englis... > but sometimes considered offensive if used by a man to a woman he does not know There are billions of other magic numbers to choose from anyway.
> but sometimes considered offensive if used by a man to a woman he does not know
At some point within the past 10 years they started inserting these annoying little sjw asides into the dictionaries