r/cprogramming

As the title says, My first program is a text editor. Well other that hello world.

------------BACK GROUND----------------

Im 19 now but a year ago I got really into old computers and laptops. And I like really love them they are all really cool. but i realized I don't really use them and they just sit there. So I decided to get myself used to MSDOS and everthing to know about using them for daily things.

oneday I was thinking about how id like to learn how to program. I tried before by making gamed with c# and unity when I was 10 but I didnt really get into it.

I decided I really wanted to learn but I was afraid that i would give up again so I tried to think about the best way to learn. Who could I learn from that was also really great at programming you know? I realized that it were the programmers from the 80's and 90's. They could do amazing things by just learning from books and had the discipline to write efficient code while being limited with memory.

I realized I could follow in their foot steps with the same computers that they would have used. which mine is running MS-DOS 5.0 and an 80386 CPU.

So I went on a hunt to find the physical copies of compilers of languages I want to learn from. I found Borland Turbo C/C++, MASM, Microsoft Fortran and cobol. As well as a couple books for C.

These last two months of March and april Ive read seven books on C. My favorite was "Pointers on C" by Kenneth A. Reek. after learning the basics from the first book I read I wrote hello world as Is mandatory. But before I started learning C I had a goal which was to write a text editor so I kept reading until I felt like I could start.

------------The Grit Text Editor-----------------

I have named It Grit.

currently It is at a bare Minimum. The arrow keys are used to traverse the file and is saved/closed with ESC.

one Issue that desperatly needs attention is how the text is displayed. Because It is meant for to be ran from the command line it was not made using and specialized graphics functions and the text is just written character by character.

One

This Issue is the fault of my current gap in C knowledge. The functions I used from conio.h that control where the cursor is, and clearing the screen are work but cause on screen blips. this is because these functions are wraps for system interupts that do things like moving the cursor and such. this works HOWEVER back then programmers would display things on screen by directly accessing the graphics in memory with pointers.

--------------HOW I PLAN TO FIX/IMPROVE-------------

This is what I plan on learning next. first Im going to reread a lot of my books and then Im going to learn Graphics and at the same time Assembler with MASM.

-------------------GIT HUB--------------------------------

https://github.com/thatoneproton/Grit.git

if you guys could, read over and give feedback

I'm gonna take a hot take, I think that AI is absolutely terrible at coding in low level (C/C++/ASM) the code it generates is absolute SLOP, and functions terribly. (AI SLOP)

I am having a problem with loading .c files in ye olde Borland Turbo C for DOS 2.01. .C files will display properly if I load them in any other editor on earth, under any other operating system, but Turbo C seems to ignore line feeds(?) when loading that same file into it's IDE editor. It will throw out an error about the line being too long, etc.

Sincerely,

Getting a Bit Annoyed in Bermuda

[supprimé]

I've recently purchased a physical copy of Tanenbaum's original "Operating Systems: Design and Implementation" (first edition), downloaded the companion MINIX 1.1 source code and spent a few weeks setting up a cross-platform toolchain so that I can build the pre-ANSI C codebase, targeting the 8086/8088, from my modern machine. The toolchain is based on Bruce's C Compiler (bcc) and the dev86 project, which is vendored into the project to keep things stable.

So far I've learned a ton and had to deal with a few interesting problems trying to get such an old C codebase compiling:

• Porting the original PC/IX assembly code to dev86's as86.
• Adding some numeric compiler routines from bcc libc to the MINIX libc library.
• Tweaking the MINIX C runtime (crtso) to work with bcc and the MINIX exec syscall.
• Fixed a couple of bcc compiler bugs to allow passing structs by value: a bug in the optimiser was trashing the stack and a bug in the codegen logic was clobbering a register. I've since learned that passing structs by value wasn't supported in the original K&R book or Ritchie's original reference manual, but the code for the MINIX shell requires it and it was a common compiler extension.

Further details in the project changelog.

Anyway, thought I'd share this here because it's been a lot of fun bringing this historical codebase and OS back to life and I want others to know that there's still a lot of fun/learning to be had exploring the original MINIX OS.

Accessible via the `complex.h` header

What other useless things have you encountered in C?

i want to learn C in a interesting way other than reading doc. As I'm more of a visual learner then reading text.

I have watched yt videos but most good onces are old.
Any suggestions on how?
websites / Games or anything?

been learning C for a bit and wanted to make something visual. but SDL2 felt too involved for doing sth simple....so i made my own library..its called Cinder. sits on top of SDL2, collapses all the setup into basically nothing:

CinderInit(CINDER_SUBSYSTEM_ALL);
CinderCreateWindow(CinderDefaultWindowDesc());

while (CinderIsRunning()) {
    CinderBeginFrame();
    CinderClearBackground(CINDER_BLACK);
    CinderEndFrame();
}

covers drawing, input, audio, fonts, textures, timers, rng.. the usual stuff. there are examples in the repo (pong, snake, pendulum) if you want to see how it actually feels to use.

feedback welcome

AutoRocq: an open-source LLM agent built for verifying C code in Rocq/Coq. Linked with CoqPyt to autonomously search for existing lemmas and get real-time feedback.

im a lazy programmer, I absolutely hate cmake files, they take away from the C experience. Just wondering who else uses AI to write cmake files. (I love cmake, its real easy to use. Just not the cmakelists.txt files)

Someone give me feedback on how eligible this blog is

Hey,
I wrote a code base in C and want to check its MISRA C complaince. Searched and found cppcheck which supports MISRA 2012 could not get hand on any latest tools. Is there any tool that support the latest MISRA edition compliance check and is free ?

Hi, I had to do a project where I used an FPGA and i wrote half in C and half in Verilog, now I need to present my project in a few weeks but I don't know exactly what type of diagram I should use for my C part. I thought about using a block diagram similar to the one used for Verilog designs, but that feels a bit too simple but using UML diagrams also feels somewhat unnatural? maybe because I do not know how can i replicate it from OOP to C. Is there a specific type of diagram that is commonly used for C projects to represent functionalities and communication between modules? My project has around 9 files in C, each responsible for a specific task, and some of them communicate with each other.