Hi/2 all.

Tomas, argv[ 0 ] is not assumed to be a full path, really ?

I know, at leat in recent, 0th parameter must be a full path to

executable file. Sure, other argv except 0th need not be a full path.

They are just parameters.

However, if we shouldn't modify argv probably, we should modify

ParamStr to return a full path as 0th parameter.

Of course, the best solution is to modify both argv and ParamStr.

I don't think that FSearch could solve this problem in DOS, because

all executable file are in directory specfied in 'PATH' and current.

I think that in OS/2, DosGetInfoBlocks is the appropriate API, is not ?

For better FPC !!!

from KO Myung-Hun...

argv is for C compatibility and should be the same as argv in C programs.

They are just parameters. However, if we shouldn't modify argv probably, we should modify ParamStr to return a full path as 0th parameter.

true, paramstr(0) should return full path.

To:
From: Peter Vreman
Subject: Re: [fpc-devel]argv[ 0 ] is not assumed to be a full path ? Date sent: Sun, 12 Nov 2000 13:06:29 GMT
Send reply to:

argv is for C compatibility and should be the same as argv in C programs.

BTW, can somebody verify this works correctly for GO32v2, please (I don't have the GO32v2 version installed at the moment)? I'm asking because ParamStr (0) returns the argv value without any modification there currently.

Tomas

Date sent: Sun, 12 Nov 2000 21:24:36 +0900
From: KO Myung-Hun
To: FPC mail
Subject: [fpc-devel]argv[ 0 ] is not assumed to be a full path ? Send reply to:

I don't think that FSearch could solve this problem in DOS, because all executable file are in directory specfied in 'PATH' and current.

This should work. How does DOS locate a program specified on the command line:
1) Checks, whether you didn't give the full (or relative) path.
2) Looks in the current directory.
3) Searches throughout directories specified in PATH. I must have a look at it, there might be some DOS function for getting the full executable path as well, which would be easier, of course (_if_ it would be supported under EMX/RSX).

I think that in OS/2, DosGetInfoBlocks is the appropriate API, is not?

Yes, it is.

Tomas