X-Git-Url: http://lambda.jimpryor.net/git/gitweb.cgi?p=lambda.git;a=blobdiff_plain;f=how_to_get_the_programming_languages_running_on_your_computer.mdwn;h=78efd3df5268120a8f3d7dbb5d2b2b32ab6a7646;hp=f9fa2d43282ead1598b463b34e8068868872a3ac;hb=35ea387dd37b8fba24a3f085c27be4cf9a71e3a4;hpb=5595cab508b2f06edc3fc21bcf3cd75b3193423b
diff --git a/how_to_get_the_programming_languages_running_on_your_computer.mdwn b/how_to_get_the_programming_languages_running_on_your_computer.mdwn
index f9fa2d43..78efd3df 100644
--- a/how_to_get_the_programming_languages_running_on_your_computer.mdwn
+++ b/how_to_get_the_programming_languages_running_on_your_computer.mdwn
@@ -1,6 +1,9 @@
## Identifying your system ##
We'll assume you're using either Mac OS X, or Windows, or Linux.
+If you're running **iOS**, you'll have a much harder time (perhaps impossible,
+perhaps not) getting this software to run on your machine, and we can't give
+you any guidance.
If you're using **Mac OS X**, take note of what version of the Mac OS you're
running. (Under the Apple Menu, select "About this Mac".)
@@ -12,74 +15,79 @@ running. (Under the Apple Menu, select "About this Mac".)
* Mavericks (10.9)
* Yosemite (10.10)
-If you're running **iOS**, you probably can't use this software on that machine. (A bit more below.)
+Furthermore, Mac users will be in one of two subgroups:
-Furthermore, you'll be in one of two subgroups:
+* You'll have Apple's Xcode and the independent MacPorts system
+ installed. (Probably you don't. If you don't know what I'm talking about, you don't have these.)
-* You'll have Apple's Xcode and the independent MacPorts system
- installed. (Probably you don't. If you don't know what I'm talking about, you don't have these.)
+ If you don't have these, but want to try this route, you can read about
+ the MacPorts system at .
+ This automates the building of Unix-type software on your Mac; it
+ makes it a lot easier to check for dependencies, use more-recent
+ versions of things, and so on. (Though as it happens, MacPorts only has an older version of
+ our chosen implementation of Scheme.)
- If you don't have these, but want to try this route, you can read about
- the MacPorts system at .
- This automates the building of Unix-type software on your Mac; it
- makes it a lot easier to check for dependencies, use more-recent
- versions of things, and so on. (Though as it happens, MacPorts only has an older version of
- our chosen implementation of Scheme.)
+ There are also other package management systems available for the Mac, notably Homebrew and Fink. I only know a little bit about them.
- Xcode is available at
- . Some
- versions of this have been available for free, though you do have to
- register with Apple as an "Apple Developer", which involves accepting a
- legal agreement with Apple. I have an older version of this installed.
- If you download a recent version, email me and let me know how the
- process works so I can tell others. There are instructions about how to
- get Xcode in the MacPorts installation guide.
-
+ There are instructions about how to get Xcode on the [Installing MacPorts](https://www.macports.org/install.php) page.
+ Some versions of [Xcode](http://developer.apple.com/xcode.html) are available for free on the Mac App Store.
+ Other versions are available through Apple's Developer website (some of these are free, but do require you to
+ register with Apple as an "Apple Developer", which involves clicking to accept a legal agreement with Apple).
+ I have an older version of this installed. If you download a recent version, email me and let me know how the
+ process works so I can tell others.
+
+* Or you won't have those installed. (**Most Mac users will be in this group.**)
+ Then you'll need pre-packaged (and usually pretty GUI) installers for
+ everything. These are great when they're available and kept up-to-date;
+ however sometimes those conditions aren't met.
-* Or you won't have those installed. (**Most Mac users will be in this group.**)
- Then you'll need pre-packaged (and usually pretty GUI) installers for
- everything. These are great when they're available and kept up-to-date;
- however sometimes those conditions aren't met.
If you're using **Windows**, you'll be in one of two subgroups:
-* You'll have the Cygwin system
- installed.
- This puts a Unix-like layer on top of your Windows system,
- and makes it easier for you to use the same software everybody
- else will be using, without its needing as much special-for-Windows
- treatment. However, many of you won't have this installed.
+* You'll have the Cygwin system installed.
+ This puts a Unix-like layer on top of your Windows system,
+ and makes it easier for you to use the same software everybody
+ else will be using, without its needing as much special-for-Windows
+ treatment. However, many of you won't have this installed.
+
+* You won't have Cygwin installed. (**Most Windows users will be in this group.**)
+ You might in theory have a different group of compilers installed
+ (MinGW, or Microsoft Visual C++) but we'll assume that the overwhelming
+ majority of users in this group don't have access to a compiler and
+ need pre-packaged installers for everything.
-* You won't have Cygwin installed. You might in theory have
- a different group of compilers installed (Microsoft Visual C++) but
- we'll assume that the overwhelming majority of users in this group
- don't have access to a compiler and need pre-packaged installers
- for everything.
If you're using **Linux**, you could be using any one of numerous packaging
systems.
-* We'll give examples using the packaging system shared by Debian and Ubuntu,
- and we'll assume that those of you using different packaging systems will know
- how to make the relevant substitutions. You may also want to take note of the
- output of the "uname -srm" command. On my machine this tells me "Linux
- 3.12.8-extrastuff x86\_64". That tells me I'm running the x86\_64 (as opposed to the
- i686 or i386 or whatever) version of Linux, and that I'm running kernel
- version 3.12.8.
+* We'll give examples using the packaging system shared by Debian and Ubuntu,
+ and we'll assume that those of you using different packaging systems will know
+ how to make the relevant substitutions.
+
-**For all of these groups**, a general item to take note of is what "processor architecture" your machine is running. Three of the possibilities are:
+**For everyone**, a general item to take note of is what "processor architecture" your machine is running. Three of the possibilities are:
-* One of Intel's i386, i486, i586, i686 architectures. These are collectively known as "x86" or "IA-32" or sometimes just "32-bit".
-* Intel or AMD's x86\_64 architecture. This is sometimes also called "x64" or "amd64" or "IA-64" or sometimes just "64-bit".
-* ARM or some other architecture. These are generally lower-powered machines, like iPads. Some of the software we're proposing *might* in principle be capable of running on such machines, but installers don't seem to be available. We'll assume you have access to an x86 or x86\_64 machine.
+* One of Intel's i386, i486, i586, i686 architectures. These are collectively known as "x86" or "IA-32" or sometimes just "32-bit".
+* Intel or AMD's x86\_64 architecture. This is also called "x64" or "amd64" or "IA-64" or sometimes just "64-bit". (Note that these *aren't* "x86" machines, even though "x86\_64" starts with those letters.)
+* ARM or some other architecture. These are generally lower-powered machines, like iPads. Some of the software we're proposing *might* in principle be capable of running on such machines, but installers don't seem to be available. We'll assume you have access to an x86 or x86\_64 machine.
-In the Linux example above, I could tell my machine is running x86 because the result of the `uname` command said "i386" at the end. Another machine I have says "x86\_64" at the end. On a Mac, you can also say `uname -m` in a Terminal session, and it will say something like "i386". I think that Mac OS's from Lion / 10.7 forward have all been x86\_64-only. On Windows, I don't know how to collect this information. But generally, machines running Windows XP will probably be i386/32-bit (unless it's a version of Windows with "64-bit" or "x64" in its title); machines running Windows Vista or Windows 7 or Windows 8 could be running either x86/32-bit or x64/64-bit.
+On Linux or Mac OS X, you can open a terminal and type `uname -m`. If the
+result is "x86\_64", then you've got x64/64-bit. If it's "i386" or something
+like that, then you've got x86/32-bit. I think that Mac OS Xs from 10.7 / Lion
+forward have all been x86\_64-only.
+
+On Windows,
+[here is a page that can help you figure this out](http://windows.microsoft.com/en-us/windows/32-bit-and-64-bit-windows).
+I think that most machines running Windows XP will be x86/32-bit (unless it's
+a version of Windows with "64-bit" or "x64" in its title); machines running
+Windows Vista or Windows 7 or Windows 8 could be running either x86/32-bit or
+x64/64-bit.
## PLEASE REPORT PROBLEMS (AND SOLUTIONS!) ##
@@ -94,76 +102,123 @@ easier and more straightforward for others.
## Getting Scheme ##
-**Scheme** is one of two major dialects of *Lisp*, which is a large family of
-programming languages. The other dialect is called "Common Lisp." Scheme is the
-more clean and minimalistic dialect, and is what's mostly used in academic
-circles.
+**Scheme** is one of two or three major dialects of *Lisp*, which is a large family
+of programming languages. The other dialects are called "Common Lisp" and "Clojure".
+Scheme is the more clean and minimalist dialect, and is what's mostly used in
+academic circles.
+
+* In your web browser:
+
+ There is a (slow, bare-bones) version of Scheme available for online use at .
Scheme itself has umpteen different "implementations", which share most of
their fundamentals, but have slightly different extensions and interact with
-the operating system differently. One major implementation used to be called
-PLT Scheme, but then a few years ago changed their name to Racket.
-This is what we recommend you use. (If you're already using or comfortable with
-another Scheme implementation, though, there's no compelling reason to switch.)
+the operating system differently. One major implementation is called [Racket](http://racket-lang.org),
+and that is what we recommend you use. (A few years back they were called PLT Scheme, but then
+they changed their name to Racket.)
+If you're already using or comfortable with
+another Scheme implementation, though, there's no compelling reason to switch.
+
+
-Racket stands to Scheme in something like the relation Firefox stands to HTML. It's one program among others for working with the language; and many of those programs (or web browsers) permit different extensions, have small variations, and so on.
+Another good Scheme implementation is [Chicken](http://www.call-cc.org). For our purposes, this is in some respects
+superior to Racket, and in other respects inferior. If you have any issues with installing or using Racket, you could
+try this out instead. You might even want to install both.
+
+
+
+Racket and Chicken stand to Scheme in something like the relation Firefox stands to HTML. They are two programs (or platforms) among others for working with the Scheme language; and many of those programs (or web browsers) permit different extensions, have small variations, and so on.
Racket has several components. The two most visible components for us are a command-line interpreter named "racket" and a teaching-friendly editor/front-end named "DrRacket". You will probably be working primarily or wholly in the latter.
+
+
+The current version of Racket is 6.1.1 (released November 2014).
+
+* **To install in Windows**
+
+ Go to . Download and install the "Windows x64" version. (Or the "Windows x86" verson if you have an older, 32-bit system.)
-
+* **To install on Mac without MacPorts**
-* In your web browser:
+ Go to . Download and install the option for your system, most likely "Macintosh
+ OS X (Intel 64-bit)".
- There is a (slow, bare-bones) version of Scheme available for online use at .
+ After you copy the files from the Installation disk to your /Applications folder, I think it's helpful to do these additional steps. In a Terminal, type:
+ sudo ln -s /Applications/Racket*/DrRacket.app /Applications/
+ sudo ln -s /Applications/Racket*/bin/racket /usr/bin/
-* **To install in Windows**
+ Then you can launch Racket either by double-clicking the DrRacket icon in
+ your Applications folder (this gives you the GUI interface); or by typing
+ `racket` in a Terminal (this gives you the command-line version).
- Go to . Download and install the "Windows x64" version. (Or the "Windows x86" verson if you have an older, 32-bit system.)
+* **To instead install Chicken Scheme on Mac without MacPorts**
-* **To install on Mac without MacPorts**
+ Here are the exact steps I just verified worked. Note that I installed the Haskell Platform, described further down this page, first; that installed some developer tools that were needed to build and install Chicken.
- Go to . Download and install the option for your system, most likely "Macintosh
- OS X (Intel 64-bit)".
+ 1. Go to , and click the "Source code" link near the top. Current version is 4.9.0.1, released November 2014. This should fetch a file to your download folder, and will probably automatically unpack that file into a folder, "chicken-4.9.0.1". Click on that folder and press command-C / Copy, then open a Terminal.
+ 2. In the terminal type `cd` followed by a space, then press command-V / Paste. Then press enter. This will move your session into the folder you just downloaded.
+ 3. Type `less README` and read that file.
+ 4. Type `sudo mkdir -p /usr/local`
+ 5. Type `make PLATFORM=macosx XCODE_DEVELOPER= XCODE_TOOL_PATH=/usr/bin`
-* **To install on Mac with MacPorts**
+ The options starting with `XCODE_` are to tell the Chicken build scripts that I've got the developer tools installed in my main system, rather than as part of Xcode. (That's where the Haskell Platform installer put them.)
- You can install a command-line version of
- PLT Scheme (dating from early 2009) by opening a Terminal
- and typing:
+ 6. Wait a while while Chicken builds.
+ 7. If it finishes with no errors, then type `sudo make PLATFORM=macosx XCODE_TOOL_PATH=/usr/bin install`. This will prompt you for your account password, and then install Chicken underneath your `/usr/local` directory.
+ 8. At this point you can type `which chicken`. If it gives you an answer of "/usr/local/bin/chicken", then skip to the next step. Else you should type `echo 'export PATH=/usr/local/bin:$PATH' >> ~/.bashrc`, then exit and restart your Terminal session.
+ 9. In your terminal, type `chicken-install -sudo r7rs datatype matchable monad`. This will download, build, and install a few extensions (Chicken calls them "eggs") relevant to ideas we'll be working with in this course.
- sudo port install mzscheme
+* **To install on Mac with MacPorts**
- If you want the GUI components, I think you'll need to use the
- "Mac/without MacPorts" installation options above.
+ Unfortunately, MacPorts doesn't have Racket itself available. It only has an older version from when they still called
+ themselves PLT Scheme. And even then, it only has the command-line program "mzscheme" (what's nowadays called "racket"); it
+ doesn't have the GUI program that corresponds to what's now called "DrRacket". You can install mzscheme by opening a Terminal
+ window and typing:
- I recommend also typing:
+ sudo port install mzscheme
- sudo port install rlwrap
+
- then if you ever use the command-line program `mzscheme` (or `racket`), you should start it by typing `rlwrap mzscheme`. This gives
- you a nice history of the commands you've already typed, which you can scroll up and down in with your
- keyboard arrows.
+ If you want the GUI components, I think you'll need to use the
+ "Mac/without MacPorts" installation options above. Or you could try the Chicken Scheme implementation instead of Racket. This is more current.
+ To do that, type:
-* **To install on Linux**
+ sudo port install chicken readline
- Use your packaging system, for example, open a Terminal and
- type:
+
- sudo apt-get install racket
+ Whether you use mzscheme or Chicken, I recommend also typing:
- It's very likely that your packaging system has some version of
- Racket available, so look for it. However, if you can't find it you
- can also install a pre-packaged binary from the Racket website at .
- Choose the option for your version of Linux (Ubuntu and Debian are available).
+ sudo port install rlwrap
- As above, I recommend you also type:
+ then if you ever use the command-line program `mzscheme` (or `racket`, for that matter), you should start it by typing `rlwrap mzscheme` (or whatever). This gives
+ you a nice history of the commands you've already typed, which you can scroll up and down in with your
+ keyboard arrows.
- sudo apt-get rlwrap
+* **To install on Linux**
- then if you ever use the command-line program `mzscheme` (or `racket`), you should start it by typing `rlwrap mzscheme`. This gives
- you a nice history of the commands you've already typed, which you can scroll up and down in with your
- keyboard arrows.
+ Use your packaging system, for example, open a Terminal and
+ type:
+
+ sudo apt-get install racket
+
+ It's very likely that your packaging system has some version of
+ Racket available, so look for it. However, if you can't find it you
+ can also install a pre-packaged binary from the Racket website at .
+ Choose the option for your version of Linux (Ubuntu and Debian are available).
+
+ As above, I recommend you also type:
+
+ sudo apt-get rlwrap
+
+ then if you ever use the command-line program `mzscheme` (or `racket`), you should start it by typing `rlwrap mzscheme` (or whatever). This gives
+ you a nice history of the commands you've already typed, which you can scroll up and down in with your
+ keyboard arrows.
## Getting OCaml ##
@@ -172,97 +227,155 @@ Racket has several components. The two most visible components for us are a comm
programming languages. The other dialect is called "SML" and has several
implementations. But Caml has only one active implementation, OCaml or
Objective Caml, developed by the INRIA academic group in France.
-
-
-*Will add more information about this soon.*
-
-