help2002

It's UWAweek 30 (2nd semester, week 1)

Displaying selected article

Showing 1 of 1168 articles.
Currently 11 other people reading this forum.

UWA week 42 (2nd semester, week 12) ↓

4:15pm Thu 19th Oct, Christopher M.

Hello, I don't understand how the Subject: line relates to your questions, but... ANONYMOUS wrote:

>> ./mysync -r -a -i dir1 dir2 > Here, no wildcard is provided after -i

There is no wildcard, but dir1 is a valid pattern.

> ./mysync -r -a -i '*.c' '*.h' dir1 dir2 > Here, more than one wildcard is provided after -i

Then '*.h' is being provided as a (valid) directory name.

> ./mysync -r -a -i '0**~!' dir1 dir2 > Here, an invalid wildcard is provided after -i, should we report the format of wildcard character is wrong?

'0**~!' is a possible (valid) pattern.

> ./mysync -r -a dir1 dir2 > Or, the provided dir1 cannot be opened, it's an incorrect path

Then report the error as instructed on the project sheet.

> ./mysync ---a -i > Or, there is no path and the command part of the command is wrong

Then report the error as instructed on the project sheet.

> Are all five of these scenarios incorrect input? Do we need to print an error for these?

You should print error messages for each error found.

> 2. In our automated testing scenarios, will there be cases where the file name or folder name contains spaces?

There may be. It is valid for a folder name to have spaces in it.