[email protected]
[Top] [All Lists]

Re: bin/38327: uu{en,de}code - any reason to use non-portable [sg]etprog

Subject: Re: bin/38327: uu{en,de}code - any reason to use non-portable [sg]etprogname?
From: Christos Zoulas
Date: Sat, 29 Mar 2008 14:45:02 +0000 UTC
The following reply was made to PR bin/38327; it has been noted by GNATS.

From: [email protected] (Christos Zoulas)
To: [email protected], [email protected], [email protected], 
        [email protected]
Cc: 
Subject: Re: bin/38327: uu{en,de}code - any reason to use non-portable 
[sg]etprogname?
Date: Sat, 29 Mar 2008 10:42:04 -0400

 On Mar 29,  1:40pm, [email protected] (Aleksey Cheusov) wrote:
 -- Subject: Re: bin/38327: uu{en,de}code - any reason to use non-portable [sg
 
 |  Is there anybody who call uuencode as foobar? :)
 |  Seriously, if an independance of executable name is really your goal,
 |  close this PR.
 
 This suggestion is very similar to a suggestion from someone else a decade
 ago to remove err() and change it to fprintf(stderr + exit( for portability.
 Get on with the program. If your OS of choice does not have setprogname()
 make them add it instead of making our own code "more portable".
 
 christos
 

<Prev in Thread] Current Thread [Next in Thread>