.	.	.	.	.

PEOPLE IN OUR CLASS (not yet available)

~~ Spring 2009 ~~

The Most Beautiful Tree

by

Jonathan Hinkle

SCHEDULE OF TOPICS (click here)


READING LIST

Many papers from Prof. Pierce's compiled list of "great works in programming languages".

	12:30 PM - 1:45 PM (Tue, Thu)	Hardman Hall (Bldg 1031)	Room: 101
	12:20 PM - 1:10 PM (Wed)	Boyd (Bldg 1023)	Room: 306

Buildings:
	Boyd (Bldg 1023 blue above )	306	Class Room (W) & Instructor/TA Mailboxes/Office
	Hardman Hall (Bldg TBD) not annotated)	101	Class Room (T/Th)
	Boyd Hall (Bldg 1023 blue above)	219C	Instructor Office

Maria Hybinette Boyd 219C maria at cs.uga.edu

 

Will Whiteside Boyd 201B

picture coming soon

 

Thursdays	2-3:30 pm	Hybinette (Boyd 219 C)	(and by e-mail appointment - maria AT cs DOT uga DOT edu)
M/W/F	3:30-4:30 PM	Whiteside (Boyd 201B)	willw900 AT GMAIL DOT COM

PREREQUISITE:

Proficiency in a programming language such as C++ or Java and Data structures (e.g. CSCI 2720).

This course is an introduction to the design and implementation of programming languages. We will cover both past and present languages, with an emphasis on modern languages. We will look at a wide spectrum of styles of programming that include imperative, functional, logic and object oriented languages and evaluate their strengths and limitations.

• Syntax and semantics
• Names, binding and scope
• Imperative, functional, logic based and object oriented paradigms
• Types
• Control flow
• Scripting languages

RECOMMENDED TEXT:

Programming Language Pragmatics, 2/e Michael L. Scott ISBN: 0-12-633951-1 Book/Paperback Publisher: Morgan Kaufmann Publishers, 2006

OPTIONAL TEXT:

Concepts of Programming Languages, 7/e Robert W. Sebesta, University of Colorado, Colorado Springs ISBN: 0-321-33025-0 Publisher: Addison Wesley Professional

EVALUATION:

Participation	5%
Projects	25%
Summaries	15%
Presentation/Chair	10%
Quizzes	10%
Exam 1	10%
Exam 2	10%
Final Exam	15%

Each student student will present on one-two topics throughout the Semester, each presenter is expected to read technical papers (or essays) to ensure breadth of the week's topic. Some suggestions to add "breath" to your themed topic are listed in the reading list, or, you may choose your own.

Students are expected to participate during presentations.

Students will read/skim at least one technical paper or essay every week. For each of the required papers each student will prepare a 1-page summary. This critique must be emailed to the instructor before midnight on the day the paper is due, typically a Wednesday. You also must turn in a hard copy of the paper the following day (Thursday). The hardcopy will be used for grading and the email will check when you turned in the HW (to see if it is elible to be graded). Note that both the hardcopy and the softcopy are required. The summary needs to reflect that you made an effort to read and understand the paper (and must cover the points listed on the reading web page). Graduate student summaries are expected to reflect a deeper understanding of the material than the under-graduate student summaries. The summary should address the questions listed on the reading list. You should also include a brief critique of the current week's presentation. What else should have been included?/excluded? Suggested improvements? You may skip up to 2 critiques without a penalty.

The purpose of the assignments is familiarization of concepts of programming languages. The assignments are individual projects. However, you are encouraged to ask questions of one another, and to respond to other student's questions. Direct exchange of code is prohibited, as is line-by-line assistance. This is checked for every assignments

No outside assistance is permitted (exceptions: instructor or TA).

Unless otherwise specified, exams are closed-book and no additional materials may be used.

Missing an exam: absence due to serious illness will be an acceptable reason for missing an exam. Doctor's diagnostic note is required. The final grade will be scaled accordingly.

You must subscribe to the class email list, see details HW1 listed on the schedule page.

Assigned homework (if any) must be typed, you must also email a copy to the class email account.

Projects must run and compile on atlas.

Other class polices will be listed on published class introduction slides.

• Email list: TBD

FINAL LETTER GRADES (not available)

LATEST GRADES (available)

Project 7,Project 6,Project 5, Project 4, Project 3

LATEST NEWS (listed most recent to least recent):

• 01/03/09 Working on getting e-mail list set up.