Hello!

I was just wondering whether the input file will always be called in.txt, and the outfile will always be called out.txt since the project description says that we should take in.txt and out.txt as command-line arguments.

If a filename other than in.txt or out.txt is passed in should these be used instead? And if so, should I check that the extension is always .txt ?

Thank you!

"Harrison Lisle" [email protected] wrote:

Hello!

I was just wondering whether the input file will always be called in.txt, and the outfile will always be called out.txt since the project description says that we should take in.txt and out.txt as command-line arguments.

If a filename other than in.txt or out.txt is passed in should these be used instead? And if so, should I check that the extension is always .txt ?

Thank you!

You can write is as an assumption that it will always be named that. This is a simple project so I doubt they'd check it. But a good practice is to not hard code it but instead let it work with any names. Hope this helps!

"Harrison Lisle" [email protected] wrote:

Hello!

I was just wondering whether the input file will always be called in.txt, and the outfile will always be called out.txt since the project description says that we should take in.txt and out.txt as command-line arguments.

Yes. The spec explicitly states the names of the files will be in.txt and out.txt

If a filename other than in.txt or out.txt is passed in should these be used instead? And if so, should I check that the extension is always .txt ?

As Anon said it is good practice to be able to read a file of any name as opposed to a hard coded value. However, for this project you can assume that the file name passed in as a command line argument is always correct. So, no checking is necessary.

Thank you!

I actually have already implemented it so as that the command-line arguments will be the files taken from/written to- is this okay? I assume that it is, as in.txt and out.txt are always passed when calling ./simulation

"Harrison Lisle" [email protected] wrote:

I actually have already implemented it so as that the command-line arguments will be the files taken from/written to- is this okay? I assume that it is, as in.txt and out.txt are always passed when calling ./simulation

Yes. The first argument will always be in.txt (file read from) and the second will be out.txt (file written to).