In particular, all C++ programs must compile and work using SUN workstations and the GNU C++ compiler ( g++ ). You may use other platforms to help you develop and debug the program, but the eventual submission will have to be done with the "submit" program using the UNIX infrastructure. NO EXCEPTIONS TO THIS RULE AND NO EXCUSES!!

In order to do so you first need to download X-Win32 from here. You will be asked to login using your USC account. You can find detailed instructions on how to set it up to connect to aludra here. You can also find some very useful instructions on how to use UNIX commands and Emacs in the Course Material link on the left.

So let's assume that you have written your first program whose name is assignment1.cpp

Please note that the shell is CaSe SeNsItIvE. The g++ compiler uses -o switch to specify the name of the output file and the second argument is the c++ file you would like to compile. Now your c++ file should be compiled and the object file named ass1.out should be created (use "ls" to make sure it now exists in your current directory). Simply type ass1.out and press enter now to execute your program.

This means you have done everything right and can now submit the program. Don't forget that we do NOT need the object file (ass1.out) because we will use the same g++ command described above and will compile it ourselves. So all you have to do is to send us your cpp file. Use the following command to do so:

In the above line, the -user tag specifies which use should receive the file. So if you miss spell it we will NOT receive it. The -tag is used to direct the file(s) you submit into the right folder on our server. It is "very" important that you double check the tags for each assignment before submitting it. We have had "many" cases in which the grader has not been able to find the file(s) students submitted only because they submitted it to a wrong folder. There is a corresponding folder on our account whose name should just be similar to what you use in your tag option above. So for the second assignment you would change the -tag option to -tag p2 and so on.

Please note that the tag name is CRITICALLY important, if you mis-spell it or say instead of -tag p1 you use -tag myassignment or -tag ass1 it will not be copied to the TA's submit folder and the grader/TA will not be able to find it and grade it. Please pay extra attention to the syntax of the submit command.

This means on the class account, under the "p1" folder, submit program has automatically created a folder the same as your username and has copied your assignment1.cpp there. Do not delete or change the assignment after submission. The system saves the submission time and when you resend a file the timestamp will be updated as well. The grader will test your program by compiling and executing your program. You are completely responsible for making sure that you submit the program correctly.

If you would like to "record" your session to keep a "receipt" of the assignments you submit, you can use the "script" command as follows:

The -a switch enables you to append your new session to the previously created file called "filename". If you don't use that switch, it simply logs your session to the file mentioned in [filename]. For more information use the "man" command in your terminal session: man script

aludra.usc.edu(28): script -a jafkhosh_log.txt
Script started, file is jafkhosh_log.txt
aludra.usc.edu(1): ls -l
total 1
-rw------- 1 jafkhosh 0 Sep 6 18:59 jafkhosh_log.txt
-rw------- 1 jafkhosh 16 Sep 6 18:49 test.cpp
aludra.usc.edu(2): submit -user csci455 -tag p1 assignment1.cpp
Submitting file "assignment1.cpp" to "csci455" ... SUCCEEDED.
aludra.usc.edu(3): date
Tue Sep 6 19:00:35 PDT 2005
aludra.usc.edu(4): exit
exit
Script done, file is jafkhosh_log.txt

The lines in red are the ones you should type at the command prompt. You have now created a log file which has recorded your session. Keep this log file for your own records.

Caution: Never delete or modify the submitted file(s) until the assignment is graded to your satisfaction

The University of Southern California does not screen or control the content on this website and thus does not guarantee the accuracy, integrity, or quality of such content. All content on this website is provided by and is the sole responsibility of the person from which such content originated, and such content does not necessarily reflect the opinions of the University administration or the Board of Trustees