Tech C Programming

I like C. You don't have to, but I do.

Here are some useful/interesting/insightful resources which I always refer back to:

• How to C in 2016
• Linux Kernel coding style and linuxsty.vim
• Programming Articles by Adam Tornhill
• Google C++ Style Guide - Names and Order of Includes

Other things I liked:

• Higher-Level C by ERJH
  • Objects in C
  • Encapsulation in C
  • Method Polymorphism in C
  • Namespaces in C
• Seventeen steps to safer C code by Thomas Honold
• The Ultimate Question of Programming, Refactoring, and Everything
  • How to make fewer errors at the stage of code writing. Part N1
  • How to make fewer errors at the stage of code writing. Part N2
• How I Program C by Eskil Steenberg

Building

• https://raw.githubusercontent.com/superjamie/snippets/master/Makefile
• https://raw.githubusercontent.com/superjamie/snippets/master/Makefile-simple

Arguments

• GNU getopt
• docopt - Command-line interface description language

Learning

• https://learn-c.org/
• CodeStepByStep - C Exercises

Networking

• Beej's Guide to Network Programming

Numbers/Memory

• https://float.exposed/
• https://integer.exposed/
• https://memory-spy.wizardzines.com/

SDL

• SDL Wiki
• TwinklebearDev SDL 2.0 Tutorial (C++ but explains concepts)
• Lazy Foo' Productions - Beginning Game Programming v2.0

Roguelike Stuff

• libtcod
• BearLibTerminal

Rust

• Rust By Example
• The Rust Programming Language

DOS

• https://delorie.com/djgpp/
• https://github.com/andrewwutw/build-djgpp
• https://pdcurses.org/
• https://github.com/msikma/allegro-4.2.2-xc

Vim

vim-lsp

https://github.com/prabirshrestha/vim-lsp

This is rad for everything except the kernel.

I use the ccls language server, I've found it better than clangd.

I generate compile_commands.json with bear like bear -- make

Key bindings:

    setlocal signcolumn=no
    if exists('+tagfunc') | setlocal tagfunc=lsp#tagfunc | endif
    nmap <buffer> gd <plug>(lsp-definition)
    nmap <buffer> gs <plug>(lsp-document-symbol-search)
    nmap <buffer> gS <plug>(lsp-workspace-symbol-search)
    nmap <buffer> gr <plug>(lsp-references)
    nmap <buffer> gi <plug>(lsp-implementation)  " doesn't seem to do anything for C
    nmap <buffer> gt <plug>(lsp-type-definition)
    nmap <buffer> <leader>R <plug>(lsp-rename)
    nmap <buffer> [g <plug>(lsp-previous-diagnostic)
    nmap <buffer> ]g <plug>(lsp-next-diagnostic)
    nmap <buffer> K <plug>(lsp-hover)
    nnoremap <buffer> <expr><c-k> lsp#scroll(+4)
    nnoremap <buffer> <expr><c-j> lsp#scroll(-4)
    nmap <buffer> <f2> <plug>(lsp-rename)

GNU Global's gtags-cscope

For the Linux kernel, I use the source code tagging system GNU Global to generate source code tags (it's much better than ctags), and this ships with a plugin that improves on the old vim-cscope:

https://cvs.savannah.gnu.org/viewvc/global/global/gtags-cscope.vim?revision=1.14&view=markup

There's a bit of history there, this assumes familiarity with cscope concepts:

• symbol global definition
• symbol usage
• symbol callers
• extended regex search

It creates Vim commands for these:

• :cs f g SYMBOL
• :cs f s SYMBOL
• :cs f c SYMBOL
• :cs f e PATTERN

It creates leader actions for these when you're on a keyword:

• Ctrl + leader + g
• Ctrl + leader + s
• Ctrl + leader + c
• Ctrl + leader + e

This is MUCH quicker than constantly hopping in and out of cscope, and lets you use Vim's native jump list commands to navigate older (Ctrl+o) and newer (Ctrl+i) as you read. See :help jump-motions