/c89/ - C Programming

Rules

Obviously, the global rules apply. This shouldn't need stating because you agreed to them when you filled out the captcha.

/c89/ is SFW. Any NSFW content will be deleted with prejudice. However, if you get fired for using C at work, it wasn't safe for work, was it?

This is not a place to discuss programming with meme languages, this includes Rust and any version of C++ more recent than 98. Fortran is welcome; so is Lisp.

Do your own homework.

Malicious interpretation of the C language standard is a bannable offense. This applies to any and all GCC and clang contributors. Yes, if you've conributed to GCC from 2.95 onward, or clang/llvm, ever, you're not welcome here.

Here, SUS is the Single Unix Specification, only and always. Using SUS with a different meaning is a bannable offense. Just play it safe and write out the Single Unix Specification in full every time.

And finally, trust the programmer, if you need hand holding because you don't know, and don't want to know, what you're doing, get off the board.

Because it Needs to be Said

Your gender is C. Your pronouns are you/your. If you code with your genitals, you keep that shit off this board.

We don't care about your skin colour; neither should you when coding. It's not important.

In this reality, 2+2=4. Objections are a bannable offense. See also https://0.30000000000000004.com/ for floating point calculations.

Good day anons,

Recently discovered this board and was immediately intrigued.

I've been programming using C99 for the last year, writing a assembler for my custom cpu arch. Has been one of the most informative experiences, learned a great deal about C in that time (but of course still have long to go).

My question in particular is about GCC 2.95.

What happened?

What paradigm shift occurred that caused the fear of the undefined?

The gnu changelog doesn't mention anything particularly pozzed:

https://www.gnu.org/software/gcc/gcc-2.95/features.html

Also noticed LFS documentation (albeit dated) that mentioned "that the kernel developers have certified GCC-2.95.3 as the preferred compiler for compiling the [linux] kernel".

https://www.linuxfromscratch.org/blfs/view/5.1/general/gcc2.html

Thanks for reading anons.

That didn't go well.

What can C be used for?

This question gets asked a surprising number of times by newcomers. After all, everyone and their dog are doing memes instead of coding.

C powers the world. Apache and nginx are written in C, so is PHP. Almost all operating system kernels are written in C. This includes Linux. PostgreSQL is written in C.

To write games in C, use SDL. If you want to write GUI applications, use IUP instead. For web/HTTP clients and the like, use Curl. For server applications, use FastCGI.

Almost every task already has a C library for it. This includes parsing meme protocols like XML and JSON. For whatever you want to do, find the appropriate library and use it. Only write your own when you can't use something else.

Why /c89/?

/c/ was taken, it's e0001. Obviously, /cp/ for C Programming is a banned board name. It does not mean that we only use or discuss C as of ANSI 1989. All versions of C are welcome, from the mid-70s editions with the =+ operators reversed, to current_year(). When it matters, state what standard you're coding to.

Why 8kun?

For the past twenty years, ever since GCC 2.95 came out, or thereabouts, programmers have been systematically brainwashed that undefined behaviour is a swear word and must be stamped out at all costs.

This has resulted in extreme backlash against people who speak against that insane intpretetation of the C standard. See for example discussions between a GCC contributor and Anton Ertl.

The reality is more complex, and it's the opinion of this board owner that GCC and clang maintainers and contributors are simply insane, and have had the past twenty years to convince the rest of the world that their insanity is real.Post too long. Click here to view the full text.