CS 3723
Programming Languages  
Fall 2014
  Submitting Homework  

Paperless Course: I will use electronic submission of homework, to make do with less paper in this course. Each homework will be submitted by email, graded, and returned by email. The email address to use will be the first one below, where δοτ is a "dot" and ατ is an "at-sign":

    <nealδοτwagnerδοτextraατgmailδοτcom>
            (for all homework and nothing else)

    <nealδοτwagnerατgmailδοτcom>
            (for everything else: questions, etc.)

When you send email to either of the above addresses, you implicitly give permission for me to send email to you at the address you use. The UTSA administration has no access to email at either of these addresses.

Submission Requirements:
  • Subject Header in Email: Your header line for Homework 0 should be: "H0, <your last name>, <your first name>", where you put in your actual last name and first name. Thus a student named Bruce Wayne should use
      H0, Wayne, Bruce
    for the subject line.

    You should also copy the same subject header as the first line of your submission. Sample Submission.

  • Form of Submissions: I prefer submissions that are a single text file (.txt).   Absolutely no WORD or Zip files (no .doc, no .zip files), nothing created with Microsoft Wordpad, no Rich Text Format files (.rtf), and no binary files. HTML and PDF are fine. If you work in Windows, you could use Notepad, but must be careful to save as "text only" (.txt).

    If you would normally want to submit several files, you can concatenate them into one file (preferred), or you can attach them as separate files (acceptable).

    I recognize that it will sometimes be annoying to write answers to homework requirements as a text file, particularly for mathematical formula. You should not worry about making these answers good-looking or neat.

    Submissions for a homework should not contain extraneous or excessive material, but should be limited to the homework requirements.

  • Deadlines: Each homework has a full credit due date and time, usually ????day at midnight during the week after the homework. After that there is a 75% credit due date and time, usually ????day at midnight during the week after the homework. Following the second deadline, the homework is not good for any credit.

    I intend to be strict about these deadlines. If some special problem comes up, that is what the 75% fallback credit is for, and if a special problem keeps you from meeting the second deadline, you just shouldn't have cut it that close, and it is only one out of 12 or 13 homeworks. In the end, you should send something to meet the deadlines even if it is not complete.

    For the deadline I will use the timestamp on the email, which should be when the email is processed. There could be a delay between when you submit the email and the timestamp, but I don't expect this to be a problem.

    It is permissible to submit the homework in time for the first deadline, and then to submit a better version in time for the second deadline. Your grade in this case will be the better of the two grades for the two submissions. In case of multiple submissions for the same deadline, only the latest will be graded, although all will be retained.

  • Programs with Runs: I will often have you submit computer programs as part of homework assignments. Unless explicitly stated otherwise, program source must always be submitted, and it must always be followed by the results of a run.

(Revision date: 2014-07-25. Please use ISO 8601, the International Standard.)