CSE3322 Programming languages and implementation - Semester 2 , 2006 unit guide

Semester 2, 2006

Chief Examiner

Lloyd Allison

Lecturers

Clayton : Lloyd Allison

Outline

The four main programming language paradigms: imperative, functional, logic and object oriented. Example languages and their applications. The implementation of programming languages by means of interpreters and translators will be discussed. This will include parsing techniques, compiler construction and implementation techniques for language features which are paradigm specific.

Objectives

Ability to use a specified programming language from a paradign other than the dominant paradigm of the course. Knowledge of the features of the main paradigms of programming languages. Knowledge of, and ability to implement, features (syntactic and semantic) of languages in the main programming paradigms.

Prerequisites

Before attempting this unit you must have satisfactorily completed
  • CSE2303 or CSC2030,
  • CSE2304 or CSC2040, and
  • CSE2305 or CSC2050
, or equivalent. You should have knowledge of
  • Advanced programming including recursion
  • Elementary data structures including lists and binary trees
  • Familiarity with an object-oriented programming language
  • Deterministic and non-determinstic finite state automata and regular expressions
  • Context-free grammars

Unit relationships

CSE3322 is a unit in the BCS, BSE, BSci(CS) and some double degrees.

It is a prerequisite/corequisite for Before attempting this unit you must have satisfactorily completed

  • CSE2303 or CSC2030,
  • CSE2304 or CSC2040, and
  • CSE2305 or CSC2050
, or equivalent. You should have knowledge of
  • Advanced C programming including recursion
  • Elementary data structures including lists and binary trees
  • Familiarity with an object-oriented programming language
  • Deterministic and non-determinstic finite state automata and regular expressions
  • Context-free grammars
.

 

You may not study this unit and

CFR3160, CSC3220, SFT2207, SFT3207

in your degree.

 

Texts and software

Required text(s)

Recommended references

* J.D. Ullman. {\narrower Elements of ML Programming (2nd Ed.). Prentice Hall, 1998. * D. Watt. Programming Language Design Concepts, John Wiley, 2004. * A.V. Aho, R. Sethi and J.D. Ullman. Compilers: Principles, Techniques and Tools. Addison-Wesley, 1986. }

Additional reading

* M. Felleisen and D. Friedman. {\narrower The Little MLer.. MIT Press, 1997. * L.C. Paulson. ML for the Working Programmer (2nd Ed.). Cambridge University Press, 1996. * T.W.Pratt and M.V. Zelkowitz. Programming Languages: Design and Implementation (4th Ed). Prentice Hall, 2001. * J.C. Mitchell. Concepts in Programming Languages. Cambridge University Press, 2003. * R. Sethi. Programming Languages: Concepts and Constructs. Addison-Wesley, 1989. * R. Wilhelm and D. Maurer. Compiler Design. Addison-Wesley, 1995.

Textbook availability

Text books are available from the Monash University Book Shops. Availability from other suppliers cannot be assured. The Bookshop orders texts in specifically for this unit. You are advised to purchase your text book early.

Software requirements

Current versions of:
gcc (C, http://gcc.gnu.org/), Java (http://java.sun.com/), SML, (http://www.smlnj.org/), ghc (Haskell, http://haskell.org/haskellwiki/Implementations), Pascal (http://www.gnu-pascal.de/gpc/h-index.html).

Software may be:

  • downloaded from see 7.3

Hardware requirements

Students studying off-campus are required to have the minimum system configuration specified by the Faculty as a condition of accepting admission, and regular Internet access. On-campus students, and those studying at supported study locations may use the facilities available in the computing labs. Information about computer use for students is available from the ITS Student Resource Guide in the Monash University Handbook. You will need to allocate up to n hours per week for use of a computer, including time for newsgroups/discussion groups.

Recommended reading

Recommended references

* J.D. Ullman. {\narrower Elements of ML Programming (2nd Ed.). Prentice Hall, 1998. * D. Watt. Programming Language Design Concepts, John Wiley, 2004. * A.V. Aho, R. Sethi and J.D. Ullman. Compilers: Principles, Techniques and Tools. Addison-Wesley, 1986. }

Additional reading

* M. Felleisen and D. Friedman. {\narrower The Little MLer.. MIT Press, 1997. * L.C. Paulson. ML for the Working Programmer (2nd Ed.). Cambridge University Press, 1996. * T.W.Pratt and M.V. Zelkowitz. Programming Languages: Design and Implementation (4th Ed). Prentice Hall, 2001. * J.C. Mitchell. Concepts in Programming Languages. Cambridge University Press, 2003. * R. Sethi. Programming Languages: Concepts and Constructs. Addison-Wesley, 1989. * R. Wilhelm and D. Maurer. Compiler Design. Addison-Wesley, 1995.

Library access

You may need to access the Monash library either personally to be able to satisfactorily complete the subject.  Be sure to obtain a copy of the Library Guide, and if necessary, the instructions for remote access from the library website.

Study resources

Study resources for CSE3322 are:

Pdf notes and example code at http://www.csse.monash.edu.au/courseware/cse3322/ under the current year.

Unit website

http://www.csse.monash.edu.au/courseware/cse3322/

Structure and organisation

Week Topics Study Guide
1 introduction, ML1 http://www.csse.monash.edu.au/courseware/cse3322/2006/
2 ML2, ML3
3 ML4, ML5
4 ML6, ML7
5 ML8, summary.
6 Concepts 1, 2, http://www.csse.monash.edu.au/courseware/cse3322/2006/
7 concepts 3, 4.
8 Implementation 1, 2 http://www.csse.monash.edu.au/courseware/cse3322/2006/
9 Implementation 3, 4
10 Implementation 5, 6
Non teaching week
11 Implementation 7, 8
12 Implementation 9, 10
13 summary.

Timetable

The timetable for on-campus classes for this unit can be viewed in Allocate+

Assessment

Assessment weighting

see 14.4; also see http://www.csse.monash.edu.au/courseware/cse3322/

Assessment Policy

To pass this unit you must:

see 14.4; also see http://www.csse.monash.edu.au/courseware/cse3322/

Your score for the unit will be calculated by:

see 14.4; also see http://www.csse.monash.edu.au/courseware/cse3322/

Assessment Requirements

Assessment Due Date Weighting
a1 (ML) 4 Aug 5%
a2 (ML) 25 Aug 10 %
a3 (implementation) 6 Oct 10 %
a4 (implementation) 16 Oct 5 %
The exam is 3 hours long and is closed book. Exam period (S2/06) starts on 23/10/06 70 %

Assignment specifications will be made available on http://www.csse.monash.edu.au/courseware/cse3322/2006/.

Assignment Submission

the submit program and/or hardcopy as specified at http://www.csse.monash.edu.au/courseware/cse3322/ under the current year

Extensions and late submissions

Late submission of assignments

assignments must be received on or before the due date and time. Late submissions will be penalised at a 5% penalty per day or part thereof. They will not be accepted more than one week after the due date: see http://www.csse.monash.edu.au/courseware/cse3322/ under the current year for specific details.

This policy is strict because comments or guidance will be given on assignments as they are returned, and sample solutions may also be published and distributed, after assignment marking or with the returned assignment. 

Extensions

It is your responsibility to structure your study program around assignment deadlines, family, work and other commitments. Factors such as normal work pressures, vacations, etc. are seldom regarded as appropriate reasons for granting extensions. 

Requests for extensions must be made as soon as possible . You will be asked to forward original medical certificates in cases of illness, and may be asked to provide other forms of documentation where necessary. A copy of the email or other written communication of an extension must be attached to the assignment submission.

Grading of assessment

Assignments, and the unit, will be marked and allocated a grade according to the following scale:

Grade Percentage/description
HD High Distinction - very high levels of achievement, demonstrated knowledge and understanding, skills in application and high standards of work encompassing all aspects of the tasks.
In the 80+% range of marks for the assignment.
D Distinction - high levels of achievement, but not of the same standards. May have a weakness in one particular aspect, or overall standards may not be quite as high.
In the 70-79% range.
C Credit - sound pass displaying good knowledge or application skills, but some weaknesses in the quality, range or demonstration of understanding.
In the 60-69% range.
P Pass acceptable standard, showing an adequate basic knowledge, understanding or skills, but with definite limitations on the extent of such understanding or application. Some parts may be incomplete.
In the 50-59% range.
N Not satisfactory failure to meet the basic requirements of the assessment.
Below 50%.

Assignment return

We will aim to have assignment results made available to you within two weeks after assignment receipt.

Feedback

Feedback to you

You will receive feedback on your work and progress in this unit. This feedback may be provided through your participation in tutorials and class discussions, as well as through your assignment submissions. It may come in the form of individual advice, marks and comments, or it may be provided as comment or reflection targeted at the group. It may be provided through personal interactions, such as interviews and on-line forums, or through other mechanisms such as on-line self-tests and publication of grade distributions.

Feedback from you

You will be asked to provide feedback to the Faculty through a Unit Evaluation survey at the end of the semester. You may also be asked to complete surveys to help teaching staff improve the unit and unit delivery. Your input to such surveys is very important to the faculty and the teaching staff in maintaining relevant and high quality learning experiences for our students.

And if you are having problems

It is essential that you take action immediately if you realise that you have a problem with your study. The semester is short, so we can help you best if you let us know as soon as problems arise. Regardless of whether the problem is related directly to your progress in the unit, if it is likely to interfere with your progress you should discuss it with your lecturer or a Community Service counsellor as soon as possible.

Plagiarism and cheating

Plagiarism and cheating are regarded as very serious offences. In cases where cheating  has been confirmed, students have been severely penalised, from losing all marks for an assignment, to facing disciplinary action at the Faculty level. While we would wish that all our students adhere to sound ethical conduct and honesty, I will ask you to acquaint yourself with Student Rights and Responsibilities and the Faculty regulations that apply to students detected cheating as these will be applied in all detected cases.

In this University, cheating means seeking to obtain an unfair advantage in any examination or any other written or practical work to be submitted or completed by a student for assessment. It includes the use, or attempted use, of any means to gain an unfair advantage for any assessable work in the unit, where the means is contrary to the instructions for such work. 

When you submit an individual assessment item, such as a program, a report, an essay, assignment or other piece of work, under your name you are understood to be stating that this is your own work. If a submission is identical with, or similar to, someone else's work, an assumption of cheating may arise. If you are planning on working with another student, it is acceptable to undertake research together, and discuss problems, but it is not acceptable to jointly develop or share solutions unless this is specified by your lecturer. 

Intentionally providing students with your solutions to assignments is classified as "assisting to cheat" and students who do this may be subject to disciplinary action. You should take reasonable care that your solution is not accidentally or deliberately obtained by other students. For example, do not leave copies of your work in progress on the hard drives of shared computers, and do not show your work to other students. If you believe this may have happened, please be sure to contact your lecturer as soon as possible.

Cheating also includes taking into an examination any material contrary to the regulations, including any bilingual dictionary, whether or not with the intention of using it to obtain an advantage.

Plagiarism involves the false representation of another person's ideas, or findings, as your own by either copying material or paraphrasing without citing sources. It is both professional and ethical to reference clearly the ideas and information that you have used from another writer. If the source is not identified, then you have plagiarised work of the other author. Plagiarism is a form of dishonesty that is insulting to the reader and grossly unfair to your student colleagues.

Communication

Communication methods

Preferred: At the tutorials, or at the lectures.

Notices

Notices related to the unit during the semester will be placed on the Unit Website. Check this regularly. Failure to check the web site is not regarded as grounds for special consideration.

Consultation Times

As indicated at http://www.csse.monash.edu.au/~lloyd/Misc/time-sem2.html

If direct communication with your unit adviser/lecturer or tutor outside of consultation periods is needed you may contact the lecturer and/or tutors at:

Dr Lloyd Allison
Reader
Phone +61 3 990 55205
Fax +61 3 990 55157

Mr Cameron McCormack

All email communication to you from your lecturer will occur through your Monash student email address. Please ensure that you read it regularly, or forward your email to your main address. Also check that your contact information registered with the University is up to date in My.Monash.

Additional information

http://www.csse.monash.edu.au/courseware/cse3322/ under the current year.

Last updated: Jul 25, 2006