DOC PREVIEW
LSU CSC 4101 - Syllabus

This preview shows page 1 out of 4 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 4 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 4 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

CSC 4101Programming LanguagesFall 2014SyllabusGerald BaumgartnerCourse SummaryPrinciples of programming language design; specification of syntax and semantics; underlying implementation ofblock structured languages; dynamic memory allocation for strings, lists, and arrays; imperative versus applicativeprogramming; logic programming; modern programming languages.Prerequisites• CSC 3102: Advanced Data Structures and Algorithm Analysis.• Credit will not be given for both this course and CSC 7001.Office HoursWho Where Phone E-Mail WhenGerald Baumgartner PFT 3119C 578–2191 [email protected] TTh 1:00–2:30pmDipak Singh [email protected] office hours by appointment.Reading• Michael Scott, Programming Language Pragmatics, 3rd ed., Morgan Kaufmann Publishers, 2009.• Robert W. Sebesta, Concepts of Programming Languages, 10th ed., Addison-Wesley, 2009 (optional).• Peter Norvig, Teach Yourself Programming in Ten Years, http://norvig.com/21-days.html, 2001.• Guy L. Steele Jr., Growing a Language, OOPSLA ’98, ACM, 1998.• Henry G. Baker, I Have a Feeling We’re Not in Emerald City Anymore, ACM SIGPLAN Notices, Vol. 32, No. 4,April 1997.• Richard P. Gabriel and Ron Goldman, Mob Software: The Erotic Life of Code, OOPSLA ’00, ACM, 2000.• CSC 4101 Mailing List.• Web page http://www.csc.lsu.edu/˜gb/csc4101/.1Important Dates• Fall Holiday: Thu, Oct 2• Midterm Exam: Tue, Oct 14, 10:30am–11:50am• SC ’14 conference: Nov 18–20 (?)• Turkey Day Break: Thu, Nov 27• Final Exam: Tue, Dec 9, 5:30pm–7:30pmBoth exams are comprehensive.HomeworksThere will be five homework assignments, which will be due at the beginning of class on the due date. A penalty of15% will be assessed for each day a homework is late up to a maximum of 30%.Programming AssignmentsThere will be three programming assignments, which will be due at midnight (11:59pm) of the due date. The firsttwo programming assignments will be in Java or in C++. The third one will be in Scheme. There will also be smallprogramming assignments, such as 1–10 liners in Scheme, ML, or Prolog as part of homeworks.A penalty of 10% will be assessed for each day a project is late up to a maximum of 30% after which it will not beaccepted.GradingThe following grading scale will be used. The homeworks all weigh equally. The first two projects are worth 13%each, while the third project is worth 10%.Homework 15%Projects 36%Midterm 24%Final 25%The course will be graded partly on a curve. For this reason, I will deduct points rather liberally and I willencourage the graders to do the same. Don’t be too upset if you don’t get what you consider to be a high score. Whengrading on a curve the absolute score is not that important. To give you a feeling about where you are standing inclass, statistics about the scores will be provided periodically.TopicsThe following list of topics is the ordering of subjects covered in this course. The time spent on each subject will vary.I don’t know yet when the homework and project due dates will be. So the following list of topics is only a roughoutline.2Topic DueIntroduction, Functional ProgrammingScheme, OO Programming HW 1Syntax and Parsing, OO Programming HW 2OO Programming, Data Types Project 1OO Programming, Types, Scoping HW 3Subprograms and Parameter Passing MidtermParameter Passing, Subprogram Impl. HW 4Subprogram Impl., Exception Handling Project 2Functional Programming, ML HW 5Logic Programming, Prolog Project 3Due Dates and GradingThe time allotted for each homework assignment will be made quite generous, as such, the penalty for turning in lateis high: 15% per day up to a maximum of 30%. If you turn in a homework on a weekend, write on the submission dateand time and slide it under my door. I often stop by my office on weekends. Predating a late submission is considereda cheating offense. On weekends, submission by Saturday 5pm will incur a penalty of 15%; submission by the nextclass period will incur a penalty of 30%.Since the time needed for finishing a programming assignment is harder to estimate and to allow fixing severebugs that show up close to the deadline, programming assignments can be submitted up to three days after the officialdeadline. For each day past the deadline, a penalty of 10 percent will be incurred. Programming assignments will besubmitted electronically. Projects will be due at midnight. The submission facility will reject your submissions threedays after the due date.Without prior arrangements in case of extenuating circumstances, submission of homeworks and projects past thelate deadline is not allowed and such work will not be graded and you will receive no credit. It is your responsibilityto make sure that you have completed your work with enough time to submit your materials.Grading disputes can be submitted in writing with accompanying documentation, or in person during regular officehours. It is course policy that whoever graded the work will be responsible for handling disputes. In general, I willgrade the midterm exam and the final exam. The graders will grade the homeworks and the programming assignments.Grades become final one week after a homework, project, or exam is handed back. This should leave ample time forresolving grading disputes.Homework StandardsAll written work submitted must carry the student’s name and must be reasonably neat and well organized. Any workthat cannot be read easily will score zero points. A reasonable standard of English expression and grammar is alsorequired. The same requirements apply to exams.Programming StandardsThe algorithm used must be essentially correct. Obviously, the program should (compile and) run. Because of thecomplexity of some of the programs, very little or no credit can be given for a program that doesn’t run. If a programdumps core or throws a runtime exception, only partial credit will be given.Since programming assignments might build on top of a previous project, it is very important to get each submis-sion to run without core dumps and to structure the program so it can be easily extended.I expect your work to exhibit high standards of programming style and layout, reflecting your expertise as acomputer professional. Poor style and documentation may results in points being deducted.3HonestyI will treat you as professionals, and you should plan on conducting yourself as such. This course presents manyimportant concepts you will need throughout your career as a computing


View Full Document

LSU CSC 4101 - Syllabus

Download Syllabus
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Syllabus and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Syllabus 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?