Sorry, but I can't make sense of what you write now.
My interest is not so much which functions that are added to a POSIX module, but which that are ___moved___ there, as in _copied_ and then _removed_(*) elsewhere. The only example you named that I agreed on in that regard is crypt. Then you said that you didn't want them removed elsewhere afterall, but now you again say that you want to _move_ them.
Believe me, I really do not intentionally try to misunderstand you or nitpick words here. You earlier said (8970535) that there would be compatibility issues with the POSIX module exactly because the functions added to it would be _moved_ there, which can only happen if they are removed(*) elsewhere. Then you said (8974606) that you never suggested that they should be removed(*). It's apparently a contradiction and not just a simple misunderstanding of what "move" means.
So what do you really mean? Should these example functions be removed outside the POSIX module or not? Note that whether they are left in compatibility mode or not is not the issue at all here (they obviously must be).
(And no, I don't expect a complete list. I never said so, but otoh I never said explicitly that I don't.)
*) Notwithstanding compatibility fixes that are activated with #pike or -V, of course.
/ Martin Stjernholm, Roxen IS
Previous text:
2002-09-04 17:04: Subject: argv[0]?
man, do you expect me to list ALL the functions I would like to see there? Also note that in my comment to your text I wrote "for example:" in the intention to give a sample selection of functions which _might_ be moved there. Want me to list all the ones I'd like to see there? Fine, I can do that, but it's gonna be a long post.
/ Marek Habersack (Grendel)