Re: program_invocation_name

2010-12-26 Thread Christopher Faylor
On Sun, Dec 26, 2010 at 12:20:33AM -0500, Christopher Faylor wrote: >On Sat, Dec 25, 2010 at 08:39:53PM -0600, Yaakov (Cygwin/X) wrote: >>On Fri, 2010-12-24 at 14:58 -0700, Eric Blake wrote: >>> Porting of some programs originally written for glibc over to cygwin >>> would be easier if cygwin could

Re: program_invocation_name

2010-12-25 Thread Christopher Faylor
On Sat, Dec 25, 2010 at 08:39:53PM -0600, Yaakov (Cygwin/X) wrote: >On Fri, 2010-12-24 at 14:58 -0700, Eric Blake wrote: >> Porting of some programs originally written for glibc over to cygwin >> would be easier if cygwin could provide the global variables char* >> program_invocation_{short_,}name,

Re: program_invocation_name

2010-12-25 Thread Yaakov (Cygwin/X)
On Fri, 2010-12-24 at 14:58 -0700, Eric Blake wrote: > Porting of some programs originally written for glibc over to cygwin > would be easier if cygwin could provide the global variables char* > program_invocation_{short_,}name, set automatically to match argv[0] of > main(), and declared in when

program_invocation_name

2010-12-24 Thread Eric Blake
Porting of some programs originally written for glibc over to cygwin would be easier if cygwin could provide the global variables char* program_invocation_{short_,}name, set automatically to match argv[0] of main(), and declared in when strict standards compliance isn't requested. Is it worth my