I’ve been a professional programmer for nearly a decade and I just realized that C# is C++++ with the pluses stacked
I know right‽ feels like when I learnt about the FedEx arrow for the first time
o shit
I’m glad I wasn’t the only uncultured swine unaware of the ++++ = #
Yes, and that is on purpose! It was always meant to be a joke on C++ :)
- TIL.
Me too - maybe because I was distracted by the irony that C# devs are typically the opposite of sharp… Or because it’s MicroShit and I didn’t give a flippin fuck ;)
Cringy
Don’t cut yourself on that edge kiddo
Change is hard.
Issue is, Rust is not a drop-in replacement for C. The memory safety features are just one part, and since Rust is also a “weakly” functional language, thus its prefered to write such code with it.
Anything that is drop-in replacement for C (or C++ for that matter) is going to be awful because of the same compatibility burden, imo
D is a mostly drop-in replacement (type renaming and such needed though), and it doesn’t have that issue. D even has a mode called BetterC, where the D standard library and the garbage collector is left out.
What about Zig?
Oh boy, Zig is just uglier C++ with memory safety, and it still has those awful header files…
IIRC it’s garbage collected, so really it’s just a version of Java.
I was planning to check it out, but don’t have any experience yet. I thought it is more of a replacement than drop-in replacement, I may have been wrong
Yeah, it’s not a small change. If there was a simpler way to make C memory-safe, it would have been done decades ago. It’s just a different language too, which is fair given how much younger it is.
If there was a simpler way to make C memory-safe, it would have been done decades ago.
We’ve had compile time sanitizers (-fsanitize=blah in gcc/clang) and runtime sanitizers (valgrind) for ages. I don’t know how they stack up against rust’s compile time sanitizers, but it’s something.
About how an Excel spreadsheet with no formulas stacks up against a corporate accounting suite. Valgrind is how you find the bleeding once you inevitably introduce a memory bug. I don’t understand all the fsanitize options, but I’m guessing they aren’t a blanket solution, exactly because memory bugs have still been inevitable.
This thread is making me wonder how many people actually understand what Rust does. It rigorously prevents any form of memory error at all in normal code, and unsafe blocks, where needed, tend to be tiny. It makes C segmentation faults look just as goofy as JavaScript type errors.
D kind of did that (C pointers are still an option, alongside with the preferred dynamic arrays, which has the memory safety features), and once I’ve seen a C compiler fork that retroactively added D-style memory safety features, although they also very much insisted on the “const by default” mantra.
I think this is one of those things where there’s no “kind of”. Pointers were added for a reason, you’re probably not going to implement a database very well without them. If you use them, at some scale you’re inevitably going to have memory bugs. Technically, if you were to only use hardcoded printfs, C is memory safe too.
It’s not that bad, besides who cares with machines being as fast as they are nowadays?
I care, when I need to compile a lot of stuff multiple times on not-as-fast machines. I’ll create a private repo powered by my workstation just for this. For C stuff I don’t need to, because I can just use my workstations power via distcc.
I once saw an issue someone made for some database and said that they were learning Rust and if the database was rewritten in Rust then they could help contribute!
TessaraCt
TesseraC+
I’m waiting for the marvel cinematic universe movie about filling out TPS reports and preparing for Y2k… it’s guaranteed to do better than Black Adam.
Wasn’t that the Loki show, where all of time is run by a boring dystopian corporate bureaucracy?
Now that I think of it, I guess you’re right, that show probably did do better than Black Adam.
That’s a HyperCube.
Where C♭
- C
- C plus plus
- C plus plus plus plus
- C plus plus plus plus plus plus plus plus
- C plus plus plus plus plus plus plus plus plus plus plus plus plus plus plus plus
C₊𝅄⨧⁺ᐩ is used for building firmware for hyperdimensional singularity processors.
How did you insert those unicodes???
Go here and Ctrl-C / Ctrl-V
I especially like ⨹
H̢̱̀e͖ͧ͘r͈̔́e̖̅̀ͅ ḩ͒͏̩̲ẹ̽ͯ̀ c̔͑͠҉̬o̢̢̠̜̓̚m̷̻̳ͧͪ͘ę̢̥̋̀s̢͈̲ͧ̀͜ͅ,̧̔͞ͅ f͖͗̿̕͝ȅ̴̶̩̂͟a̸̡̯͈̼͋͡s̗̋̀̀̀̀͟t̒̾͏̯ y̸̛̟̽̇o̢̟̜͂͆ͯ͘͜u̧̧̜͔͇ͭͫ́̚͞r̀̃͑̓͒͏̮ e̍̒̇ͯ҉̴̲̭y̷̰̖ͨ̑͜e̓ͭͭ͂̕҉̸̛̦̱̤̫͢s̡̛̫͋̕ o̢͉̘͚̤̅ͫͤ̓ͭ̕͡n͊͘҉̲̟̖͔͝͞ t̷̟͊̽h̨̦͎̅̄ͪ́̚͘͠i̶̢̛̬̞̦͊̅̏̀́s̶̸̢̹̹͕̩̜̣̎ͫͤ͐̈̀.̛̰̼̗̺̼͗ͣ̏́̚͟͠.̵̪ͥ̈̚̚͞ͅ.̷̶͎̞̳̘̈͋ͬ̈͂͒͠ z̸̛̫̓͜͟͡ḁ̧ͨ͊͗ͫͫ̅́͢͠͠l̵̴͒͏͚̥̻g̩͎̲̼̠̿̅ͩ͌̇͟o̢̝͍͔͍̼̼ͤͦ̎́͘͝ i̷ͧ̅̂͟͡͠͞҉̸̙̱͍͈̝̠̺̀ͅs̗̮͇̪̯̋͋́̕ t̵̶̛̰̘̰̫̬͖̜͗̒͗̉̿͌̀̀͢ẖ̴̴̡̭̪̉̌̈́͗͘e̵ͬ̃ͬ͌͆̍͏̧̡̧̦̘͇͕͙̳̹͜ ạ̳̺͎̤̺̖̠̔̈ͮ̉̌̓̀́͟͢͞͞n̊͏̰̖̘̖̭̰̖̕͢ş̴̽͘҉̮̞̼̱w̨̢̠̻͐̐͑̊͢͞e̢̡̛͖̙̟̣͋͆͘̕ͅŗ̧̯ͪ͘͘͜͡.̭̘͇͓̹̻̖̖͉͊ͪ́
On PC, you can hold Alt and press a number combination, like 1 or 257, to get an ASCII smiley. Not Unicode, but hey, it’s something
On windows *
On mäc âⁿd linųx wə ūsẽ → «çøḿpõsē» këy™
This isn’t the evolution of C at all. It’s all just one language and you’re simply stuck in a lower dimension with a dimensionally compatible cross-section.
Nix
I’m starting to have my suspicions
always wanted to C in the 4th dimension
I’m not ready for 4D, just let me try out C Lattice on a few smaller projects first.
“works on my machine.”
“Just a heads up that we’ll be shipping your machine to the client, since it’s the only machine on Earth known to support the software. You’re getting the spare machine out of the basement. Super fast Cyrix processor. Looks like it boots to Windows 11 release 3, but they’ve written it 3.11 for some reason.”
Lol I had windows 11 before it was cool
I wonder if I could upgrade it to Windows 95 and run X-Wing vs. TIE Fighter on it.
Closes ticket, marks Git issue as closed
C
C plus
C plus plus
C sharp
C sharp sharp
C through time and space
Edit: formatting
+esseraC+
🤔
The last one needs the prongs sticking out to make it a hyperhashtag.
Fun fact, C didn’t have a lot of things like Classes and was often distributed or stored alongside various libraries so it was C Plus (as in addition to) Libraries before it was C++, and somebody decided the next iteration was C with 4 pluses, which forms a #
Source: Bjarne Stroustrup, I forget which edition of his C++ book.
