| [CDT 9.2] Run/Debug Configurations are HORROR ... [message #1782898] |
Sun, 04 March 2018 10:18  |
|
Where is the fucking manual for arguments specification ???
Else what is the logic ???
Use Case :
Here is submitted to the argument line (Debug configuations -> Arguments -> Program arguments) :
${project_loc_loc}${system_property:file.separator}intern${system_property:file.separator}
What is expected on Windows :
<project effective path>\intern\
What is actually obtained :
<project effective path>intern
Ok ! anti-slash is the special character. Well, I adapt :
${project_loc}\${system_property:file.separator}intern\${system_property:file.separator}
Obtained :
<project effective path>\\\\intern\\\\
My god ...
As a result :
The argument line interpreter acts like this :
- if there is a single anti-slash, then delete it
- if there are two consecutive anti-slashes, then double them.
So, it never returns a single anti-slash.
Don't mind ... trying with single quote enclosure :
${project_loc}'${system_property:file.separator}intern${system_property:file.separator}'
Obtained:
<project effective path>'\\intern\\'
Great ... not only anti-slashes are doubled inside single quotes but single quotes are preserved ...
True to its principle: follow no functional logic...
trying with double quote enclosure :
${project_loc}"${system_property:file.separator}intern${system_property:file.separator}"
Obtained ... A nightmare :
<project effective path>\\intern\"
The opening double quote is removed but the closing one, the first anti-slash is double but not the second one while it is in the same condition as the first one.
Can't be understood.
The software designer was drunk...
Is there a documentation about the argument line syntax ?
Else, how to make this right ?
I fed up.
Thanks a lot.
The one who has the solution must be rewarded.
[Updated on: Mon, 05 March 2018 11:36] Report message to a moderator |
|
|
|
|
Powered by
FUDForum. Page generated in 0.03771 seconds
] 
Search
Help
Register
Login
Home
