Bug 14925

Summary: getsubopt isn't poisonous enough
Product: Base System Reporter: Garrett A. Wollman <wollman>
Component: binAssignee: freebsd-standards (Nobody) <standards>
Status: Closed Not Enough Information    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.0-CURRENT   
Hardware: Any   
OS: Any   

Description Garrett A. Wollman 1999-11-16 17:30:00 UTC 
	The second argument to getsubopt(3) is declared as a `pointer
	to const pointer to char'.  Since the contents of the tokens
	array are typically string literals, and since getsubopt(3)
	doesn't make any attempt to change them, it would be better
	declared as `pointer to const pointer to const char' (`const
	char * const * tokens') so that code can be compiled with
	const string literals (`-Wwrite-strings').  This is
	unfortunately type-incompatible with existing programs, and
	SUSv2 codifies the bogus type.

Fix: 

Complain to P1003 so that this mistake doesn't get carried
	over into the POSIX update.
How-To-Repeat: 
	man getsubopt
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2008-03-08 18:36:09 UTC 
State Changed
From-To: open->suspended

This is really a standards problem.  I don't think this is anything 
that FreeBSD can solve; OTOH, flag it as 'suspended' in case anyone 
on -standards has some thoughts about it.
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2008-03-08 18:36:09 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-standards
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 00:26:29 UTC 
This is a standards bug, and no one has touched this since it was reported. Closing.