mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Todo for release?
Date: Wed, 15 Aug 2012 12:20:29 +0200	[thread overview]
Message-ID: <20120815102029.GL20243@port70.net> (raw)
In-Reply-To: <CAPLrYETGvq9L-AEcTj9wOqrMtuJ+890WMnucwF_CVuZvNdcQfg@mail.gmail.com>

* Daniel Cegie?ka <daniel.cegielka@gmail.com> [2012-08-15 10:55:06 +0200]:
> >> - Support for __progname (Daniel)
> >
> > Daniel, any more thoughts on this? Are there lots of programs that
> > want it that can't easily be patched to simply use argv[0] themselves?
> 
> This is not something that is absolutely necessary. __progname quite
> often is used on *BSD and less on Linux (eg. Owl's msulogin,
> popa3d)... but __progname is always easy to fix.
> 

i think the fact that *bsd uses it
is not enough justification

openbsd uses it because it's part of
their style guide for whatever reason

"The __progname string may be used instead
of hard-coding the program name."
http://www.openbsd.org/cgi-bin/man.cgi?query=style&sektion=9

but we don't support many things from
there (like sys/queue.h)


i don't think many linux tools uses it
as it's not part of the lsb and glibc
has its own silly
program_invocation_name and
program_invocation_short_name
(which are aliases to __progname and
__progname_full)

the main justification i see is that
we already support bsd err and warn
apis which are required to print
the __progname as well
(currently they don't and actually
a simple warn("hi"); segfaults here
with musl but i havent investigated
it)


  reply	other threads:[~2012-08-15 10:20 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 18:53 Rich Felker
2012-08-13 21:31 ` Szabolcs Nagy
2012-08-13 21:53   ` Rich Felker
2012-08-13 22:06     ` Solar Designer
2012-08-14 15:02       ` Szabolcs Nagy
2012-08-15  0:30         ` Szabolcs Nagy
2012-08-13 22:20   ` Solar Designer
2012-08-14  1:46     ` Rich Felker
2012-08-14  2:13       ` Solar Designer
2012-08-14  2:35         ` Rich Felker
2012-08-14  2:49           ` Solar Designer
2012-08-14  2:58             ` Rich Felker
2012-08-14  3:35               ` Solar Designer
2012-08-14  4:49                 ` Rich Felker
2012-08-15  4:08 ` Rich Felker
2012-08-15  8:55   ` Daniel Cegiełka
2012-08-15 10:20     ` Szabolcs Nagy [this message]
2012-08-15 10:53       ` Daniel Cegiełka
2012-08-15 13:10         ` John Spencer
2012-08-15 13:23           ` Daniel Cegiełka
2012-08-15 13:32       ` Szabolcs Nagy
2012-08-15 14:36         ` Rich Felker
2012-08-17  9:49           ` Szabolcs Nagy
2012-08-17 12:10             ` Rich Felker
2012-08-22 17:45               ` Daniel Cegiełka
2012-08-22 18:57                 ` Rich Felker
2012-08-22 19:15                   ` Daniel Cegiełka
2012-08-22 20:24                   ` Richard Pennington
2012-08-22 22:44                     ` Rich Felker
2012-08-15 12:36     ` Rich Felker
2012-08-15 12:57   ` Luca Barbato
2012-08-15 14:34     ` Rich Felker
2012-08-15 18:28       ` Luca Barbato
2012-08-15 18:35         ` Rich Felker
2012-08-15 21:25         ` Rich Felker
2012-08-16 17:11           ` Luca Barbato
2012-08-15 13:27   ` Richard Pennington
2012-08-15 22:44 ` boris brezillon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120815102029.GL20243@port70.net \
    --to=nsz@port70.net \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).