FSU Seal - 1851 Course Organizer
COP 4020 Programming Languages
Fall Semester 2011
Root View: Course Components
Syllabus
jump		 The course syllabus establishes course policies on grading, attendance, and exams. The syllabus should be read in detail at beginning semester.
Calendar
jump		 The course calendar provides a detailed temporal view of the course, including lecture coverage, assignments, and due dates. The calendar will be updated regularly.
Textbook
new window		 The textbook for the course is Michael Scott, Programming Language Pragmatics (3rd edition), Morgan Kaufman, 2009 (ISBN 978-0-12-374514-9). The textbook will be relied on as the core material for the course.
Assignments
new window		 Assignments will be released through the Calendar. You need the specific file name appended to this URL.
Lectures
new window		 Lectures are in the form of a power point slide show depicting highlights of the material covered in more depth in the textbook.
LIB The course code distribution library LIB = /home/courses/cop4020p/fall11
TIOBE
new window		 The TIOBE Web Site
Programming
new window		 Free Programming Resources
My FSU
new window		 The FSU/Blackboard Portal, where you will find this course. The course site is the main communication resource for the class. Here you can get help, talk to other students, retrieve your grades, and generally keep up with course news and announcements.
Office
jump		 Schedule, office hours, and contact information for Chris Lacher
Old Exams
20012002200320042005200620082010
E1 E2 E1 E2 E1 E2 E1 E2 E1 E2 E1 E2 E1 E2 E1 E2
These are provided without answers for student use. Students are welcome to discuss these old exams. There is a Blackboard Forum for this purpose. Please, do not expect instructors to participate.
Acknowledgement The overall design and many details of this course originated with Professor Robert van Engelen of FSU. We are pleased to have his permission for re-use of ideas and materials. Note, however, that Professor van Engelen is not responsible for specifics in this course and should not be contacted about them. Please confine your inquiries to the assigned instructional staff for the course.
Temporal View: Course Calendar
Week Dates         Reading from Text Other Resources Assignments Due Date
1 8/29 - 9/4 1.1, 1.2, 1.3, 1.5, 1.7 The Semicolon Wars   The Language List   Notes: Intro Assignment 0: Create Portfolio
Homework 1
 9/11
9/11
2 9/5 - 9/11 10.1, 10.2, 10.3, 10.5, 10.7 Scheme   Notes: Functional Programming Homework 2
 9/18
3 9/12 - 9/18 11.1, 11.2, 11.4 Prolog Homework 3 9/25
4 9/19 - 9/25 1.4. 1.6 Compilers Homework 4 10/2
5 9/26 - 10/2 2.1, 2.2, 2.3, 2.5 Syntax Project 1: Scheme 10/16
6 10/3 - 10/9 4.1, 4.2, 4.3, 4.4, 4.5, 4.6, 4.7 Semantics    
7 10/10 - 10/16        
8 10/17 - 10/23 Midterm Exam: See Syllabus for exact dates.
9 10/24- 10/30 Chapter 3 Names, Scopes, & Bindings Project 2: Calculator 12/11
10 10/31 - 11/6 6.1 - 6.6.1, 6.8 Control Flow Homework 5 11/13
11 11/7 - 11/13 8.1, 8.2.4, 8.3, 8.4, 8.7 Subroutines & Parameter Passing Homework 6 11/20
12 11/14 - 11/20 8.5 Exception Handling Homework 7 11/30 [Wed]
13 11/21 - 11/27 Chapter 9 Data Abstraction & Object Orientation Homework 8 12/4 [Sun]
14 11/28 - 12/4        
15 12/5 - 12/11  
16 12/12 - 12/18 Final Exam: See Syllabus for exact dates.
Ω 12/19 - 1/1 Semester Break - you've completed a capstone course!

Unix Script Submission Process:

Most programming assignments will be submitted via a specific Unix script from your CS Majors account logged in to shell.cs.fsu.edu. The submission script for a particular assignment will be located in the assignment distribution directory.

Submission via script should generate two email responses:

  1. When your submission is received, a receipt is sent via email. The date/time stamp of this email is the official submission time.
  2. After your submission has been unpacked and placed in your portfolio, a second message is sent containing a copy of all files that were unpacked. This is a record of exactly what was received and placed in your portfolio.

After submission, be sure to check your email for these two messages. Normally these would arrive within a few seconds of submission. If you do not get both email responses, a malfunction occurred. When you do receive these confirmation emails, save them. If a problem were to arise with your files, these emails are your proof of submission.

Note that revisions may be submitted any time prior to the deadline and will automatically replace the previous submission.

Blackboard Submission Process:

Some assignments require submission via the Blackboard assignments submission facility. These should be submitted via the corresponding link under the Assignments tab in Blackboard. (DO NOT submit to the "drop box".)

Submitted files should be in pdf format (in case of written assignments) or plain text format (for code or data files). The naming should appropriately identify files, but need not identify the author in the filename, because Blackboard automatically associates the submission with the student portfolio. The appropriate suffix indicating the file type should follow the name.

Example file names: hw2.pdf, MyClass.h, Data.txt.

Note that only one submission for an assignment is allowed by Blackboard. If you have made a mistake in a Blackboard submission, contact an instructor to have the submission "cleared" in order to resubmit.