So You Want to Become a Programmer
From Compsci.ca Wiki
(Difference between revisions)
(→A Little Bit of Theory) |
|||
(2 intermediate revisions not shown) | |||
Line 8: | Line 8: | ||
*** PATH | *** PATH | ||
** Differences | ** Differences | ||
- | ** Less need to modify PATH on *nix (/usr/bin and /usr/local/bin) | + | *** Less need to modify PATH on *nix (/usr/bin and /usr/local/bin) |
- | ** Running executables in current directory | + | *** Running executables in current directory |
+ | ** Bridging the gap | ||
+ | *** Cygwin | ||
* Filesystem hierarchy | * Filesystem hierarchy | ||
+ | |||
+ | == A Little Bit of Theory == | ||
+ | |||
+ | * Source code as simply text | ||
+ | * Compilers/interpreters taking that and turning it into a format a machine can understand | ||
+ | * Statements vs. Expressions | ||
+ | ** Removes bad "magic" from programming | ||
+ | ** <pre>(+ (- 5 1) (/ 6 2))</pre> does not require special syntactic support, as opposed to <pre>(+ 4 3)</pre> | ||
+ | * Entry points (what order things are executed in) | ||
+ | ** Sometimes the program is just executed in order, and sometimes the entry point is specially delineated |
Latest revision as of 16:26, 11 May 2006
First Steps: Know Your Environment
- ASCII
- File extensions
- Command-line
- Commonalities between *nix and Windows shells
- Spaces to separate arguments
- PATH
- Differences
- Less need to modify PATH on *nix (/usr/bin and /usr/local/bin)
- Running executables in current directory
- Bridging the gap
- Cygwin
- Commonalities between *nix and Windows shells
- Filesystem hierarchy
A Little Bit of Theory
- Source code as simply text
- Compilers/interpreters taking that and turning it into a format a machine can understand
- Statements vs. Expressions
- Removes bad "magic" from programming
-
(+ (- 5 1) (/ 6 2))
does not require special syntactic support, as opposed to(+ 4 3)
- Entry points (what order things are executed in)
- Sometimes the program is just executed in order, and sometimes the entry point is specially delineated