Date:	Thu, 3 Jun 1993 01:36 EST
From:	"Wonkoo Kim, EE, U. of Pittsburgh" <WKIM AT vms DOT cis DOT pitt DOT edu>
Subject:	Re: command argument 0 (go32)
To:	pynq AT midway DOT uchicago DOT EDU, djgpp AT sun DOT soe DOT clarkson DOT EDU

>Date: Wed, 2 Jun 93 16:05:26 CDT
>From: Jeremy Mathers <pynq AT midway DOT uchicago DOT EDU>
>Subject: RE: command argument 0 (go32)
>
> ....
>Still, GO32 *could*, in theory, artificially construct a lookalike
>argv[0], based on where it finds the executable.  In fact, a further
>wish would be for GO32 to search the path, so that you could say:
>
>	go32 myprog
>
>and have myprog be somewhere on the path.  In this case:
>	1) GO32 would be acting much like user shell.
>	2) This would reduce the need for STUBbing.
>
>Still, all of this is, of course, wish list material...

Yes, I like this idea.

Since MSDOS passes full path info of x.exe to argv[0] and since go32 is for
*MSDOS*, it is natural to expect that go32 x passes full path info of x to
program.  I think this is irrelevant with unix at least in go32's argument 
passing.

Regards,

Wonkoo Kim.

- Raw text -