[Bug libc/13712] Add Type Cast to Main and Exec Calls

["jsm28 at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=13712

Joseph Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |INVALID

--- Comment #4 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-02-21 03:14:10 UTC ---
There is a difference in POSIX between filenames, defined as "A name consisting
of 1 to {NAME_MAX} bytes used to name a file. The characters composing the name
may be selected from the set of all character values excluding the <slash>
character and the null byte.", and portable filenames.  glibc and most
filesystems on POSIX systems support all valid filenames, not just portable
filenames.

http://austingroupbugs.net/view.php?id=251

is a proposal for disallowing newlines in filenames, as the most problematic
characters - all other characters can be handled in shell scripts significantly
more easily.  There has been a huge amount written on that subject on the
Austin Group mailing list over the past couple of years, and anyone seriously
interested in addressing such issues needs to digest the previous discussion
and engage with the main forum where they are discussed, which is the Austin
Group - you need to argue how a new C API should be part of the solution.

In any case, it is not possible to implement such a feature in glibc without
the underlying kernel interfaces supplementing execve, so having a well-defined
and accepted kernel interface would be required for a meaningful request to
implement such a feature in glibc.

Bug trackers are simply not an appropriate place for designing features
involving multiple components because they do not support discussion of the
interactions between those components.  Thus, if you wish to discuss this
further, please do not do it here; raise it on appropriate mailing lists that
deal with those interactions.  In practice the Austin Group lists would be the
best place; for changes specific to GNU/Linux, you could consider the linux-api
list which deals with the kernel/userspace interface.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.