Hi,

TCustomApplication, fpc-2.6.0

./mycmdtool --inputfile=myfile withspace.txt
GetOptionValue('i','inputfile') returns only "myfile" same thing happens if I try:
./mycmdtool "--inputfile=myfile withspace.txt"
./mycmdtool --inputfile="myfile withspace.txt"
./mycmdtool --inputfile='myfile withspace.txt'

How to fix this (have param value with space) ? Any workarounds if it's bug in TCustomApplication or whatever ?

This is tested on linux, but I need it on windows too.

zeljko

That is normal.

same thing happens if I try: ./mycmdtool "--inputfile=myfile withspace.txt" ./mycmdtool --inputfile="myfile withspace.txt" ./mycmdtool --inputfile='myfile withspace.txt'

This is not normal.

How to fix this (have param value with space) ? Any workarounds if it's bug in TCustomApplication or whatever ?

I created the following TCustomApplication program:

procedure TMyApplication.DoRun;
var
   ErrorMsg: String;
begin
   writeln(getoptionvalue('f','file'));
   Terminate;
end;

When run it prints the correct output:

araminta: >./tc --file='my file is here.txt'
my file is here.txt
araminta: >./tc '--file=my file is here.txt'
my file is here.txt
araminta: >./tc "--file=my file is here.txt"
my file is here.txt

So I doubt the problem is there. What gets printed if you do a

For I:=0 to ParamCount do
   Writeln(Paramstr(i));

Just to rule out TCustomApplication.

You mention TProcessUTF8, that is a complicating factor. You then need to see (using strace) what the calling app actually sends. I suspect the problem is there.

Are you using the new 'parameters' or still the old 'CommandLine' ? If the latter, then it is a safe bet that the problem is there.

Michael.

I'm using what TCustomApplication offers: HasOption and GetOptionValue. TProcessUTF8 isn't guilty here definitelly since I'm calling my utility from application with it, but my utility in console returns bad results, so something with TCustomApplication could be. Besides that I'm not using only one param, it's combination of short and long params. Only problem is param with spaces.

zeljko

I called my app from the console and all worked fine.

TCustomApplication has no special treatment of spaces, it doesn't need that. It just uses what it gets from the OS.

Besides that I'm not using only one param, it's combination of short and long params. Only problem is param with spaces.

Well, according to my tests, TCustomApplication works fine as you can see from the output I posted. I use TCustomApplication, and often have spaces in the arguments. Never had a problem, so I do not believe the issue is there.

Please post the output (by the tool) of

For I:=0 to ParamCount do
   Writeln(Paramstr(i));

This will shed some light on the issue.

Michael.

ahhhhhhh :) now I see. It works when I call my utility from console, but I've called my utility via script which have same name (but it's in $HOME/bin directory), so when such params are passed to script it calls /path_to_my_utility/myutility $@
So shell kills quotes and passes garbage to the utility.

zeljko

You can use $* normally ?

Michael.

Using the above as a test app, I get exactly the same results and Michael. It works fire here under Linux (OpenSUSE 12.2)

----8<-------------8<-------------8<-------------8<-------------8<---- [tmp]$ ./project1

[tmp]$ ./project1 -f "my long file.txt"
my long file.txt
[tmp]$ ./project1 -f 'my long file.txt'
my long file.txt
[tmp]$ ./project1 --file="my long file.txt"
my long file.txt
[tmp]$ ./project1 "--file=my long file.txt"
my long file.txt
[tmp]$ ./project1 --file='my long file.txt'
my long file.txt
----8<-------------8<-------------8<-------------8<-------------8<----

Regards,
- Graeme -

Yes, everything is ok, I've used script instead of cmd program directly.

zeljko