Sylvain Hellegouarch wrote:
I'm sorry to ask but I'm not sure to understand the meaning of having an
implementation which is exactly correct. As we have already seen on this
list, RFC4287 lacks of precision in some context, therefore I wonder what
being "exactly correct" represents. I believe Jigsaw [1] is a an example
of what you mean. Sadly it seems to be hardly referenced anywhere.
1. It finds bugs in the spec.
2. When the spec isn't clear, the answer is "what the reference
implementation does"
Of course, this requires the reference implementation to be developed
with the same authority that the spec writers have. That's not at all
the case here, so I suspect "reference implementation" is a false
statement. This will not be the reference implementation, and shouldn't
call itself one.
--
Elliotte Rusty Harold [EMAIL PROTECTED]
Java I/O 2nd Edition Just Published!
http://www.cafeaulait.org/books/javaio2/
http://www.amazon.com/exec/obidos/ISBN=0596527500/ref=nosim/cafeaulaitA/