Alan Bateman said the following on 07/16/10 16:50:
Daniel D. Daugherty wrote:
:
Your choice on how to resolve this one.
Here's the updated webrev with the changes that I proposed to push for
this one:
http://cr.openjdk.java.net/~alanb/6649594/webrev.01/
Your suggestion to add a trace flag to help diagnose startup issues is
good. I'll create a bug to track that rather than squeezing it into this
change.
Not to delay this but ... why replace the always safe strncpy with an
unsafe strcpy protected by an assert ??? I though we were moving to
always safe code to get past code-checkers etc.
And out of curiousity where does this new UNIX_MAX_PATH come from (and
if it is UNIX then why isn't used on Solaris rather than Linux ;-) )
David
