🚀 go-pugleaf

> ...
>Or, more succinctly:
>
>inline const char *ProgramName()
>{	return  strrchr(__argv[0], '\\')+1;
>}
> ...

Which, other than formatting, is IDENTICAL to what 
I had in the code before.  I then thought of how many 
times I have been beaten up in messages on here from 
people who speak of how '/' also works in path names. 

I changed it because some one, some where is likely to 
know of the one situation in which '/' would appear in 
__argv[0] and I didn't want to get into the '\\' vs '/' 
fight again! <g>

.  Ed 


>Bob Gonder wrote:
>Ed Mulroy [TeamB] wrote:
>
>>inline const char *ProgramName()
>>  {
>>  char *arg0 = __argv[0];
>>  char *s = strrchr(arg0, '\\');
>>  if (!s)
>>    s = strrchr(arg0, '/');
>>  if (s)
>>    ++s;
>>  else
>>    s = arg0;
>>
>>  return s;
>>  } // end ProgramName
>
>What if the program was started as \\server\disk/dir/program.exe
>Hmm... they might also start it with X:program.exe
>Rats...Windows translates everything and gives 
>proper '\' everywhere.
>Wonder why you had the extra test for '/' ?
>Is that for 'nix portablility?
>
>inline const char *ProgramName()
>  {
>  char *arg0 = __argv[0];
>  char *s = strrchr(arg0, '\\');
>/*	Windows fixes these 'problems'
>  char *t = strrchr(arg0, '/');
>	if( t > s )	s = t;
>  	t = strrchr(arg0, ':');
>	if( t > s )	s = t;
>*/
>  return s? ++s: arg0;
>  }
>Or, more succinctly:
>
>inline const char *ProgramName()
>{	return  strrchr(__argv[0], '\\')+1;
>}
>Maybe there's documentation somewhere that says 
>this isn't guaranteed?
>
>>    handle =
>>      InternetOpen(
>>        pname,
>>        INTERNET_OPEN_TYPE_PRECONFIG,
>>        NULL,
>>        NULL,
>>        0);
>
>Yeah, I like that better than what I had....
>
>   InternetOpen(
>	"Microsoft Internet Explorer",   // agent
>	INTERNET_OPEN_TYPE_PROXY,        // access
>	"ftp-gw",                        // proxy 
>	NULL,                            // defaults
>	0)) )                            // synchronous
>
>And the Ftp functions still work!