INFS 590: Program Submission Requirements

INFS 590 programs will be submitted electronically, and will be compiled and run automatically. Therefore, it is very important that your program use the following naming convention, and that your programs accept inputs in the exact format that is specified in the assignment. Submit your program as follows:

• Name your file for program 1 "P1username.java" (note that this means the name of the Java class must be P1username.) To make sure we don't have duplicate names, please use your GMU osf1 email user name as part of all files. For example, the TA would use the name "P1skime.java".
• Send your Java source to skime@osf1.gmu.edu, with the subject "590 P1 username". You can send your program using one of the following three methods. These are listed in the order of preference:
  1. Use our submission web page (described below).
  2. Using an attachment that her email program can handle. She uses pine on osf1 to read her email.
  3. Sending an email with the text in the body of the email.
• Your program may only create one BufferedReader object. The explanation is rather involved.
• Do not use packages. (Packages would force the TA to have to create subdirectories for your program.)

You can submit your program through our web page. Please go to the URL http://www.science.gmu.edu/~skime/SUBMIT/, and copy and paste your program into the window. This page will generate a mail message to the TA.

Here is a list of mail programs that use attachments that we know work:

• pine
• elm
• DOS or Unix file from Mozilla 4.61
• hotmail (with file written on Notepad)

The main problem we have had so far is when long lines have been copied and pasted into a mail window. Sometimes this will cause lines to be broken into two lines. If the line is a string or a comment, the program will no longer compile. This has been a particular problem with Microsoft Outlook 8.5.

When you send email, please:

• Do not include HTML tags (change the settings on Netscape).
• Do not use extremely long lines (they wrap and look ugly).
• Do not send .class files.
• Try to send just one file. You can put multiple classes into one file.
• If you send more than one file, every file name must have "PNUserName" as part of the file name. That is, if you have a node class in a separate file, call it "P2skimeNode.java".
• If you submit more than one file through the web page, submit them separately.
• Do not use TABs to indent. If you use tabs, they may look different when we print them, and you may lose points for formatting.

Jeff Offutt, Aug, 1999