-
1.1 Indent four spaces to create an escaped <pre> <code> block:
printf("%d\n", 42); /* what was the question again? */
-
1.2 Markdown and HTML are ignored within a code block
You would hate this if it weren't
/* | |
Goldbach's conjecture tested by a 47-state Turing machine | |
Author: Jared Showalter | |
If "a" and "i" were unbounded, this program would halt iff Goldbach's | |
conjecture is false. Furthermore, the program structurally | |
corresponds to a Turing machine with two symbols, one tape, and a | |
small number of states. The array "a" corresponds to the tape (each |
Why not use DNS over HTTPS (DoH)?
-
Pull dnscrypt-proxy docker image from dockerhub
I like writing well-formed git commits that explain the intention behind why a code change was made.
Check out Chris Beams excellent How to Write a Git Commit Message if you haven't read it.
Anyway, for a project I've been working on I've gathered up 900+ commits that hold up a pretty high quality (except for one 😁). Let's look at some trends about these commits!
How to remove GRUB from Windows laptop (MS Surface Pro 3) - the 4x BootRec commands did not work
=====================
- Run a
cmd.exe
process with administrator privileges
cmd.exe
- Run
diskpart
When you compile your program, you must tell the compiler to produce a program that is compatible with the debugger. The debugger needs special information to run properly. To do this, you must compile your program with the debugger flag, -g. This step is critical. Without it, the debugger won't have the program symbol information. That means it won't know what your functions and variables are called, and it won't understand when you ask it about them.