Command-line vs. Dev tools
If you've come from programming classes where you've grown accustomed
to using dev tools like Eclipse, you will first need to get
comfortable with programming at the command line. What this means:
- On Mac-OS: You will need to learn how to edit, compile
and execute using the terminal.
You will need to use the ls, mkdir,
cd and cd .. commands
at the terminal. It helps to know other commands like
mv and rm, but you can manage to do the same
with Finder.
- On Linux: Well, you already know how to work at the
commandline. (It's more or less the same as on the Mac.)
- On Windows: You will need to learn how to edit, compile
and execute using the command-prompt.
You will need to use the dir, mkdir,
cd and cd .. commands
at the command prompt. It helps to know other commands like
ren and del, but you can manage to do the same
Windows-Explorer.
All told, you'll need to spend a couple of hours to get this working,
and will get more practice as you proceed in the course.
Editing programs:
- On Mac-OS: Mac-OS comes with the pico
and vim editors for the command-line. Generally,
pico is easier to learn. If you're up for it,
Emacs is a more sophisticated editor, preferred by
Unix hackers, but difficult to learn initially.
- On Windows: Not all versions of Windows come with a default
command-line editor. You can install the nano editor
(which is a version of pico)
yourself - it takes a little doing, but it's worth it because you
will have a solid editor. Otherwise, you will need to use
Notepad. You can also install Emacs and go
through the stiff learning curve.
Use the Terminal (Mac/Linux)