Fundamentals of Computer Science I (CS151 2003F)
[Skip to Body]
Primary:
[Front Door]
[Current]
[Glance]
-
[Honesty]
[Instructions]
[Links]
[Guidelines for Lab Writeups]
Groupings:
[EBoards]
[Examples]
[Exams]
[Handouts]
[Homework]
[Labs]
[Outlines]
[Readings]
[Reference]
Misc:
[Scheme Report]
[Glimmer Scheme Reference]
[CSC151.01 (Gum)]
[CSC151 2003S]
[CSC151 2002F]
[SamR]
Back to Procedure Definitions. On to Conditionals Lab.
Held: Friday, 12 September 2003
Summary: Today we begin to learn how to tell Scheme to make decisions. The procedures used to make decisions are called conditionals. Today's class will be a large group design effort rather than an individual or small group design effort.
Assignments
Notes:
Overview:
ifif. For example,
if the grade is at least 94, then give the student an A, otherwise, if the grade is between 90 and 93, ...
(if condition
success-expression
failure-expression)
if does not behave according to the standard
pattern, in which all the arguments
to a procedure are computed before the procedure is applied).
(if (<= 90 grade) 'A 'F)
(if (<= 90 garde)
'A
(if (<= 80 grade 89)
'B
(if (<= 70 grade 79)
...)))
(if (<= grade 90)
'A
(if (<= 80 grade)
'B
(if (<= 70 grade)
...)))
cond, which more closely resembles a table.
cond expression looks like
(cond ((condition1) exp1) ((condition2) exp2) ((condition3) exp3) ... (else default-exp))
(cond ((<= 90 grade) 'A) ((<= 80 grade) 'B) ...)
if nor cond?
#t) or false
(#f).
< (strictly less than),
<= (less than or equal to),
= (equal to),
>= (greater than or equal to),
and
> (strictly greater than).
=,
eq?,
eqv?, and
equal?.
and,
or, and not.
Back to Procedure Definitions. On to Conditionals Lab.
[Skip to Body]
Primary:
[Front Door]
[Current]
[Glance]
-
[Honesty]
[Instructions]
[Links]
[Guidelines for Lab Writeups]
Groupings:
[EBoards]
[Examples]
[Exams]
[Handouts]
[Homework]
[Labs]
[Outlines]
[Readings]
[Reference]
Misc:
[Scheme Report]
[Glimmer Scheme Reference]
[CSC151.01 (Gum)]
[CSC151 2003S]
[CSC151 2002F]
[SamR]
Disclaimer:
I usually create these pages on the fly
, which means that I rarely
proofread them and they may contain bad grammar and incorrect details.
It also means that I tend to update them regularly (see the history for
more details). Feel free to contact me with any suggestions for changes.
This document was generated by
Siteweaver on Tue Dec 9 13:59:35 2003.
The source to the document was last modified on Mon Sep 1 13:30:51 2003.
This document may be found at http://www.cs.grinnell.edu/~rebelsky/Courses/CS151/2003F/Outlines/outline.10.html.
You may wish to
validate this document's HTML
;
;
Check with Bobby