Difference between revisions of "CS422 - Programming Language Design (Spring 2018)"

From FSL
Jump to: navigation, search
Line 39: Line 39:
 
::* [http://k-framework.org/index.php/K_Tutorial#.5B33.2710.22.5D_.C2.A0_Part_3:_Defining_LAMBDA.2B.2B K Tutorial, Part 3: Defining LAMBDA++] (see the provided video and textual documentation)
 
::* [http://k-framework.org/index.php/K_Tutorial#.5B33.2710.22.5D_.C2.A0_Part_3:_Defining_LAMBDA.2B.2B K Tutorial, Part 3: Defining LAMBDA++] (see the provided video and textual documentation)
 
::* [http://k-framework.org/index.php/K_Tutorial#.5B46.2746.22.5D_.C2.A0_Part_4:_Defining_IMP.2B.2B K Tutorial, Part 4: Defining IMP++] (see the provided video and textual documentation)
 
::* [http://k-framework.org/index.php/K_Tutorial#.5B46.2746.22.5D_.C2.A0_Part_4:_Defining_IMP.2B.2B K Tutorial, Part 4: Defining IMP++] (see the provided video and textual documentation)
 +
::* {{pdf|CS422-K-Overview.pdf|K Overview}} paper to learn more about K.  Sections 1 and 2 (the other sections are optional now; they are covered below)
 +
 +
'''''<font color=red>Note:</font>''''' Always download the nightly build of the K tool from http://kframework.org before any HW or project.  The latest stable may be too old.  Note that K v5.0 has just been released, under the repo named `k5`.  Make sure you do not use the `k` repo, which forwards to `k-legacy`!
  
 
{| border="1" cellpadding="5" cellspacing="0" width="100%"
 
{| border="1" cellpadding="5" cellspacing="0" width="100%"

Revision as of 19:05, 14 February 2018

Students enrolled in this class are expected to check this web page regularly. Complete lecture notes will be posted here.

Course Description

CS422 is an advanced course on principles of programming language design. Major semantic approaches to programming languages will be discussed, such as structural operational semantics (various kinds), denotational semantics, and rewriting-based semantics. Programming language paradigms will be investigated and rigorously defined, including: imperative, functional, object-oriented, and logic programming languages; parameter binding and evaluation strategies; type checking and type inference; concurrency. Since the definitional framework used in this class will be executable, interpreters for the designed languages will be obtained for free. Software analysis tools reasoning about programs in these languages will also arise naturally. Major theoretical models will be discussed.

Meetings: W/F 14:00 - 15:15, 1304 Siebel Center
Credit: 3 or 4 credits
Professor: Grigore Rosu (Office: SC 2110)
Office hours: Held by Grigore Rosu in SC 2110; by appointment.

Lecture Notes, Useful Material

The links below provide you with useful material for this class, including complete lecture notes. These materials will be added by need.

  • Structural Operational Semantics 25px-Pdf_icon.png slides Info_circle.png
  • Book lecture notes on the IMP language, big-step SOS, and small-step SOS (you can skip the rewriting logic and Maude parts; comments welcome!): 25px-Pdf_icon.png IMP-BigStep-SmallStep Info_circle.png
HW1 (due Friday, February 2) Downarrow.png

Exercise 1 (10 points): Modify IMP (its Big-Step and its Small-Step SOS) to halt when a division-by-zero takes place, returning a configuration holding the state in which the division by zero took place.

Exercise 2 (10 points): Add a variable increment construct, ++x (increment x and return the incremented value), to IMP: first add it to the formal BNF syntax, then to the Big-Step SOS, then to the type-system, and then to the Small-Step SOS.

Exercise 3 (10 points): Add I/O constructs, read() and print(AExp) to IMP: first add these to the formal BNF syntax (read() is an AExp construct and print(AExp) is a Stmt construct), then to the Big-Step SOS, then to the type-system, and then to the Small-Step SOS.

Exercise 4 (10 points): Combine the three above: add division-by-zero halting, an increment construct, and the two I/O constructs to IMP. Feel free to comment on what's going on, particularly on how inconvenient it is to do certain things in SOS (one of the points of this HW is to understand the limitations of SOS, so you will appreciate K).

Note: Always download the nightly build of the K tool from http://kframework.org before any HW or project. The latest stable may be too old. Note that K v5.0 has just been released, under the repo named `k5`. Make sure you do not use the `k` repo, which forwards to `k-legacy`!

HW2 (due Wednesday, February 21) Downarrow.png

Exercise 1 (10 points): The current K LAMBDA semantics of mu (in Lesson 8) is based on substitution, and then letrec is defined as a derived operation using mu. Give mu a different semantics, as a derived construct by translation into other LAMBDA constructs, like we defined letrec in Lesson 7. To test it, use the same definition of letrec in terms of mu (from Lesson 8) and write 3 recursive programs, like the provided factorial-letrec.lambda.

Note: See the mu-derived exercise in the nightly built for details and test programs.

Exercise 2 (10 points): Modify the K definition of IMP to not automatically initialize variables to 0. Instead, declared variables should stay uninitialized until assigned a value, and the execution should get stuck when an uninitialized variable is looked up.

Note: See the uninitialized-variables exercise in the nightly built for details and test programs.

Exercise 3 (10 points): Mofify IMP so that the K "followed by" arrow, ~>, does not explicitly occur in the definition (it currently occurs in the semantics of sequential composition). Hint: make sequential composition strict(1) or seqstrict, and have statements reduce to "{}" instead of ".", ... and don't forget to make "{}" a KResult (you may need a new syntactic category for that, which only includes "{}" and is included in KResult).

Note: See the purely-syntactic exercise in the nightly built for details and test programs.

Exercise 4 (10 points): Define a variant of callcc, say callCC, which never returns to the current continuation unless a value is specifically passed to that continuation. Can you define them in terms of each other? Do these in both the substitution and the environment-based definitions.

Note: See the callCC (substitution), from-call-CC-to-callcc (substitution), from-callcc-to-call-CC(substitution), callCC (environment), from-call-CC-to-callcc (environment), and from-callcc-to-call-CC (environment) exercises in the nightly built for details and test programs.

  • SIMPLE: Designing Imperative Programming Languages
Personal tools
Namespaces

Variants
Actions
Navigation