Conflicts between unix path types and preprocessor command line arguments

[nealkruis]

On unix systems, absolute paths begin with a / character. If the CSE input file is specified using an absolute path on the command line, and the directory begins with a D, U, or I, CSE will try to parse it as a preprocessor definition/undefine/include. On Mac, most user content is found under /Users/<user_name>/....

This is happening on this line of code.

[nealkruis]

@chipbarnaby, can we simply remove the / option for preprocessor command line arguments? (i.e., only allow -?)

[chipbarnaby]

I think the '/' options should be removed. This is a problem even for Windows, since '/' is accepted in at least some circumstances as a filepath separator.

Associated issues

• Make sure CBECC uses the - form of switches
• Search all documentation examples etc. for / form.

I'll work on this tomorrow.