Held: Wednesday, 27 January 2016

Back to Outline 02 - An Introduction to Linux. On to Outline 04 - Computing with Symbols and Numbers.

Summary

Today we begin your exploration of the Scheme programming language and the environment in which you will be devleoping algorithms in Scheme.

Related Pages

• Reading: The DrRacket Program Development Environment
• Reading: Beginning Scheme
• Reading: How Scheme Evaluates Expressions (Take 1)
• Lab: Starting Scheme
• EBoard 3 (Source 3)

Overview

• Why use programming languages?
• Scheme history.
• Scheme basics.

Administrivia

• Please grab a card and go to the computer named on the card.
• Office hours: MTWF 10-11, Tu 1-2.
  • Sign up at http://rebelsky.youcanbook.me.
  • Also feel free to stop by when my door is open.
  • Or to email me for an appointment.
• Weekly review sessions:
  • Wednesday (TONIGHT) at 8pm in the CS Commons with Zacharcy
  • Thursday at 10am in this room with SamR
  • Thursday at 8pm in the CS Commons with Kumar

Upcoming Work:

• Readings for Friday:
  • Reading: Symbolic Values
  • Reading: Numeric Values
• Assignment 2 due next Tuesday at 10:30 p.m.

Extra Credit

Academic

• Scholars' Convocation, Thursday, 11 am, JRC 101: Surveillance Techniques of the Romanian Secret Police.
• Community Conversations on Race, 7:30 p.m., Tuesday, February 2, Lazier 3rd Floor Lounge

Peer

• Track and Field at Cornell this Saturday.
• Swimming at Macalester this Saturday.

Future

• Track and Field Grinnell Invite February 6.
• Swimming February 6 vs. UN and IAState.

Miscellaneous

• Caucus on Monday night. (Or observe a Caucus on Monday night.)

Lab

• You will learn Scheme better by trying than by listening, so I'm just going to have you work on the lab.
• I hope to spend a few minutes at the end of class giving you a chance to reflect on your first real experiences with Scheme.

The Need for Formality

• Computer scientists often express their algorithms in programming languages, languages designed by other computer scientists to express algorithms.
  • Most programming languages can also be "understood" by computers.
  • More precisely, we can use a program to automatically translate programs written in these languages into instructions the computer can follows.
• In this class, you will express your algorithms in the programming language Scheme.
• In Scheme, as in most languages, you will explore the syntax (the structure of the things we write) and the semantics (what meaning we assign to the things we write).
• Some people wonder why we need artificial languages like Scheme, Pascal, C, Java, Python, and the ilk, given that we should be able to write algorithms in English.
  • In part, it's probably because the computer elite want to maintain their sense of superiority over the masses.
  • In greater part, it's because English and other "natural" languages can be ambiguous. At the very least, they have many similar structures that are interpreted very differently. Consider the classic pair of phrases.
    • Time flies like an arrow.
    • Fruit flies like a banana.
• Remember: Computers are sentient and malicious.
  • From the programmer's perspective, it often seems that they'll do their best to misinterpret whatever it is you write.

A Short History of Scheme

• Scheme is a variant of Lisp (the List processing language).
• Lisp is one of the oldest high-level programming languages in active use
  • It's from the late 1950's.
  • That is, it's from about the time of the invention of Cobol and only a few years after the invention of Fortran.
  • It predates C, C++, C#, Basic, and almost every other language used.
• John McCarthy (of MIT and then Stanford) designed Lisp to provide a language for programming in artificial intelligence.
  • At the time, many people believed that intelligence was grounded in symbolic processing.
• Lisp added many things to languages of the day:
  • Symbolic values
  • Dynamic lists as built-in data structures
  • Automatic memory management for those built-in data structures
  • Functions as values (we'll return to this in a few weeks)
• In later reflection, McCarthy indicated that some of these things were just luck. For example, the lambda that you'll learn about soon was just a "hmmm ... that sounds interesting, I'll put it in" fluke.
• Scheme was designed in the 1970's as a variant of Lisp more appropriate for teaching computer science (and doing many other things; it's more elegant).
  • Scheme has a slightly clearer semantics than Lisp (and a formal semantics, which is important).
  • Scheme adds some nifty features for advanced programmers.
  • But, at least for 151, you're doing Lisp-like programming.
• A variant of Scheme called Script-Fu was added to the Gimp in its early development, so it is tightly integrated with the Gimp.
• We've built a friendlier version of Script-Fu.

Scheme Basics

• Scheme is generally used in an interactive environment: You type syntactically valid expressions and Scheme returns their values.
  • Later this semester, we may explore how to use Scheme in different environments.
• Scheme's syntax is fairly simple: Since almost everything in Scheme involves the application of a function (a.k.a. operation, a.k.a. procedure) to some arguments (a.k.a. parameters), you write:
  • an open parenthesis;
  • the name of the function;
  • a space;
  • the arguments to the function (separated by spaces); and
  • a close parenthesis.
• For example, (+ 2 3 4) (sqrt 4) (expt 2 3)
• If you remember this basic syntactic structure, you'll rarely get syntactic errors from Scheme.
• And if you believe that claim, I have a bridge to sell you.

Some Procedures You Should Know

• +: Sum its parameters.
• *: Compute the product of its parameters.
• -: Subtract the second parameter from the first.
• (sqrt *val*): Compute the square root of val.
• (expt *v* *p*): Compute v^p.
• (abs *v*): Compute the absolute value of v.
• (max *v1* *v2* ... *vn*): Determine the largest of the given values.
• (min *v1* *v2* ... *vn*): Determine the smallest of the given values.