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

["oiaohm at gmail dot com" <sourceware-bugzilla@sourceware.org>]

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

oiaohm at gmail dot com changed:

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

--- Comment #3 from oiaohm at gmail dot com 2012-02-21 02:26:28 UTC ---
Joseph Myers would it be possible to place a forth entry.

argc avgv environment flags and to know if 4 is or is not provided.  Call old
exec functions no flags call new exec function flags.  This would keep
backwards compatibility if it possible.

"papers for WG14 (C) and the Austin Group (POSIX)"

Basically I cannot do up papers for these if I don't know what is possible.

Also my English skill is not that great.  Creating papers I am not that good
at.

I am going to hit you over head with a ten tone book POSIX.

POSIX.1-2008 ’s “base definitions” document section 4.7 (“Filename
Portability”) specifically says “Portable filenames shall not have the <hyphen>
character as the first character since this may cause problems when filenames
are passed as command line arguments”

So why can glibc create files with at - at start.  That is not to POSIX
standard.  POSIX solution is no -* file-names at all so solving problem.  glibc
is non conforming same with Linux filesystem drivers.

So if you wish to keep -* filenames really a proposal has to be put forward to
POSIX making the case that they can be used safely this is how to achieve it.

So POSIX standard solution is not "./*" or "--" options this is why this is a
problem.

WG14 you need a working reference implementation to get stuff up.  What I do
not have the skill to create.  Also WG14 does not apply that much because WG14
still gets to presume it exists in worlds without shells that can do wild-card
solving.

"the design and get agreement from multiple stakeholders"
Glibc is one of the largest stakeholders in this problem.

Basically if what I am putting forward is not workable with glibc I might as
well not put it forwards.

I am bring the same issue up with bash at the moment.
http://savannah.gnu.org/support/index.php?107960

Any other parties I should contact.

The issue I am referring is only happening because the implementations are
breaching POSIX standard.  The error does not exist in 100 percent POSIX
conforming enforcing portable filenames.

No point tell me to go to POSIX and get a ruling when there is a ruling that
you are not following so causing issue.  This is a case of how are we going to
fix this to put something up to POSIX so you can keep on doing what you are
doing.

Invalid would be true if what you were doing was POSIX confirming.

-- 
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.