Where’s the Bappyscript interface for Linux? Um sorry what? This is Bappyscript, not C. Int openat2(int dirfd, const char *pathname,Ĭonst struct open_how *how, size_t size) įeature Test Macro Requirements for glibc (see * Documented separately, in openat2(2): */ Int openat(int dirfd, const char *pathname, int flags, mode_t mode) Int openat(int dirfd, const char *pathname, int flags) Int creat(const char *pathname, mode_t mode) Int open(const char *pathname, int flags, mode_t mode) Int open(const char *pathname, int flags) Open, openat, creat - open and possibly create a file I hear that everything on Linux is “just a file”, so let’s open a file on Linux! You know like, take user input, or write output, or literally anything observable? If you want programs written in your language to be good little citizens that work well with the major operating systems, you need to interact with the operating system’s interface.
An amazing language that’s going to completely revolutionize the way that cats, sheep, and sharks program!īut now you need to actually make it do something useful. You’ve finished designing your new language, Bappyscript, with first class support for Bappy Paws/Hooves/Fins. But only insofar as it makes this protocol we all have to use an even bigger nightmare! So actually this kinda is about the whole “C is an inscrutable implementation-defined mess” thing. We must all speak C, and therefore C is not just a programming language anymore – it’s a protocol that every general-purpose programming language needs to speak.
ASTUTE GRAPHICS PLUGINS INTERFERING WITH ILLUSTRATOR LAUNCH SKIN
Rust and Swift cannot simply speak their native and comfortable tongues – they must instead wrap themselves in a grotesque simulacra of C’s skin and make their flesh undulate in the same ways it does.Ĭ is the lingua franca of programming. My problem is that C was elevated to a role of prestige and power, its reign so absolute and eternal that it has completely distorted the way we speak to each other. That stuff sucks, but on its own that wouldn’t be my problem.
This isn’t about the fact that C is actually horribly ill-defined due to a billion implementations or its completely failed integer hierarchy. Unfortunately, it’s not, and it hasn’t been for a long time. It wouldn’t if C was actually a programming language. Now you might reasonably ask: “what the fuck does your problem have to do with C?” I’m trying to materially improve the conditions of using literally any language other than C. He’s trying to materially improve the conditions of using C itself as a programming language.
Where we’re not aligned is why we’re mad about them. Phantomderp and I have both recently been very aligned on a particular subject: being extremely angry about C ABIs and trying to fix them.
0 kommentar(er)
