All compiler programming projects must meet these requirements on a standard student account of a BB136 ("alamode") machine.

  1. Submitted as a .zip or .tar.(Z|gz|bz2) compressed archive.

    If you are generating an archive with symbolic links from another *nix box, just use tar --- the invocation of zip seems to be tricky (or there are inconsistent zip versions in Linux land).

  2. The unrolled archive will be scanned for a top-most key file: only one of these may exist:

    1. A Makefile compatible with GNU make (this is the standard make on a Linux box)

    2. A Build.sh Bourne (sh) or bash script

      Case in names are important! It is Makefile with a capital M, not makefile; likewise for Build.sh. This is a 400 level course in a CS program, I think it is reasonable to expect students to be able to either

      1. develop in a Unix environment
      2. transport a system independent code base1 from Windows or MacOS X to a Unix environment.

      If you need help doing this please let me know, I'm happy to assist.

    In either case, after running2

    top $ make
    or
    top $ bash Build.sh

    there should be an application3 named appropriately for the particular compiler project. 4

As a placeholder for this wiki page, we'll use PROGRAM since it reads nicely in prose. For compiler projects though, the name will be something else.

  1. PROGRAM will be invoked with the appropriate command line arguments for the assignment, results required by the assignment should be printed on stdout.

    1. Any stdout output line with a required result must have OUTPUT as the first word (token).

    2. All numerical values required by an assignment must have whitespace (which includes end of line) around them.
    3. Required textual output should be surrounded by single colons (:).

    4. The order for results is assignment specific and important, they must emanate from the application in the order dictated by the assignment.

  2. Depending on the assignment, PROGRAM may be required to write a specifically formatted result file, in which case the OUTPUT rules above won't apply to the contents of the file.

  3. Your submitted archive should not contain unnecessary files (.o, .pyc, *.h~ ) or executable machine or vm code (*.class files, a __pycache__ directory, ...).

  4. Files and directories that begin with an underscore are reserved for use by your instructor, TA, or grader.

    1. Your submitted archive file should not have any entries that begin with an underscore.
    2. Your PROGRAM should not use or create files or directories that begin with an underscore.
  5. Written answers or graphs should always be provided in a doc subdirectory, the doc directory should be alongside your Makefile or Build.sh.

    1. Prose should be provided in either a text file, an HTML file, or a PDF file.
    2. Graphs may be embedded in your written answers (if you provide HTML or PDF). If your answers are written in a simple text file, provide your graphs in a common raster image file format (PNG, JPEG, ...), SVG, or (preferably) PDF. Refer to the graphs by name in your answer write-up.
    3. Graphs provided for assignments without a required written component should be in appropriately named files (still, of course in doc) and should be self-explanatory on viewing.5

    4. Students may always feel free to submit a README file for any assignment, but it needs to be in doc and follow these conventions.

  6. Your PROGRAM should not prompt the user for any input, nor pause the display of console messages for the human eye.

Examples

Submission Templates

Here are example trees for submissions, one each for the most common languages used by students. If you are using another language, look at one of the templates for a similar language.

Templates with a Makefile: edit Project.mak instead --- much easier.

Here is a source tarball that is a "more pure" example of a non-trivial Makefile for build C++. This example doesn't use my Project.mak build configuration file.

If you like to use IDEs such as Eclipse or M$Vs:

  1. do your work in the IDE with a simple source layout
  2. copy your code into the appropriate extracted template on a CSM Linux box
  3. test to make sure it builds and runs correctly

  4. clean it out (there is a clean target in the provided Makefiles, otherwise remove residual files by hand)

  5. tar or zip it up and submit.

If your IDE purports to generate Makefiles, then give it a try (YMMV). Be sure to test on a Mines machine!

Beware that M$ based IDEs frequently generate NMAKE files, which are a far cry from conventional Unix make compatible build files, and are uniformly mocked by gmake.

Output Formatting

Suppose a compiler assignment dictates:

Your PROGRAM should accept two arguments: the first is a file containing a grammar, the second is a valid sentence of terminals from Σ. PROGRAM should emit the following values:

  1. The total number of productions performed by the grammar.
  2. The maximum size of the parser engine stack during the parse.
  3. The type and number of each non-terminal node in the parse tree.

Then both of the following outputs would be acceptable (they differ only in the amount of programmer debug messages spewed):

But this one is not acceptable for two different (unique) reasons, do you see why?

  1. Compiler projects should be pretty OS agnostic (1)

  2. The name of your directory containing Makefile or Build.sh does not have to be named top, the example is simply showing that make and bash will be run from within your top directory. (2)

  3. This means the Unix executable bit is set. (3)

  4. This does not preclude PROGRAM existing before make or Build.sh are run, and a build script might be a mere placeholder. Such a setup is applicable for certain languages. (4)

  5. Heaven forbid, don't forget a graph title. (5)

Assignments/Requirements (last edited 2020-02-06 18:53:25 by khellman)