It's UWAweek 50

help2002

This forum is provided to promote discussion amongst students enrolled in CITS2002 Systems Programming.
Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.
Displaying the 2 articles in this topic
Showing 2 of 834 articles.
Currently 2 other people reading this forum.


 UWA week 42 (2nd semester, week 12) ↓
SVG not supported

Login to reply

👍?
helpful
2:44pm Tue 15th Oct, ANONYMOUS

"You have to write a C program in a single file called simulation.c, and compiled as an executable called simulation. It will read two file names from the command line, in.txt and out.txt. The first file is the one mentioned above, for reading process ids. The second file is an output file where you should print the following information at the end of the simulation. Your submission will be executed as: simulation in.txt out.txt" About this requirement, does our code have to run with the cmd "simulation in.txt out.txt" instead of "./simulation.c in.txt out.txt" like usual?


SVG not supported

Login to reply

👍?
helpful
4:23pm Tue 15th Oct, Joshua N.

ANONYMOUS wrote:
> "You have to write a C program in a single file called simulation.c, and > compiled as an executable called simulation. It will read two file names from > the command line, in.txt and out.txt. The first file is the one mentioned > above, for reading process ids. The second file is an output file where you > should print the following information at the end of the simulation. Your > submission will be executed as: > simulation in.txt out.txt" > > About this requirement, does our code have to run with the cmd "simulation in.txt out.txt" instead of "./simulation.c in.txt out.txt" like usual?
I believe that's a typo should be "./simulation.c in.txt out.txt".

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  8:08AM Aug 25 2024
Privacy policy