As mentioned, I’m learning C, and I’ve achieved hello-world, plus recursive calculations of factorials and some data structures. Whee. :) For those playing along at home, I’ll describe my dev setup.
But first, an unexpected discovery: Counter to my intuition, there’s a beneficial synergy between learning a new editor and learning a new language at the same time. I had thought it would be too many new things to take on at once. I’ve wanted to learn Vim for its beautiful efficiency, but its formidable learning curve repels all comers. I couldn’t gain traction. When writing in a language with which I am comfortable (C#, English), my thoughts would run too fast, too far ahead of my rudimentary editor skills, ideas slipping out of my grasp as I stumbled around the text with j, k, h, and l (and never the one I meant). But in C, where I am carefully picking my way over unfamiliar terrain, my lines of code have slowed down to match my fingers. Because I am trying to hang onto only one edit at a time, I can spare a second to check that A will switch me to insert mode at the end of the current line. I recommend it: learning a new language is a good time to learn a new text editor.
I use VirtualBox to run virtual machines. VMs are excellent for experiment-based learning; think of it: a nice clean server that you can start up, poke and abuse, throw away and start again. If you start with the right VM image—for example, one configured for Ruby on Rails—you can jump right into the experimentation without all the installation hoop-jumping.
To install a compiler (later), I needed my VM to connect to the internet. In VirtualBox Settings > Network, I set “Attached to” to “Bridged Adapter,” meaning the VM could use my laptop’s connection, and the adapter’s “Name” to my wireless card. (The other choice in the dropdown list is a PCI-E Fast Ethernet Controller, and that… didn’t work.) With that set, I powered up the VM, which starts the webmin console. I let it automatically configure DHCP, and I was internet-ready.
Vim is already installed on the Core VM image, so I just needed to type “vim helloworld.c” to start stumbling around my new code file. I’m relying on the TuXfiles Vim cheat sheet.
- apt-get update (to update apt’s list of modules)
- apt-cache search gcc (to find modules for the gcc compiler – gcc-4.1 looked right.)
- apt-cache show gcc-4.1 (to get info about it)
- apt-get install gcc-4.1 (to install it)
- gcc-4.1 myfile.c -o myexename (to compile and generate myexename executable)
- ./myexename (to run my program)
I followed a video that creates and compiles a C program using the GCC compiler. “Hello, World!” A simple phrase, profoundly satisfying.