Hi Raif,
The synchronization is still not completely right. If a method operates
on two different BigIntegers, they both need to be protected from
asynchronous finalization. Note also that when you synchronize on two
different objects, you need to protect against deadlock.
Also, could you please
hello Jeroen,
On Sunday 08 October 2006 22:44, Jeroen Frijters wrote:
Hi Raif,
The synchronization is still not completely right. If a method operates
on two different BigIntegers, they both need to be protected from
asynchronous finalization. Note also that when you synchronize on two
Robert Schuster wrote:
The other thing that is used from VMPlainDatagramSocketImpl is the connect()
method. Is it possible for DGRAM sockets to just use VMChannel.connect
instead?
Yes. The original just called the common method _javanet_connect, anyway.
Great. However there is just one
Hi,
this patch removes the above mentioned class and implements their functions
elsewhere. DatagramImpl.connect() has a different exception clause than
SocketImpl.connect() and fixing that required some changes in method signatures
and the native implementation of VMChannel.
These changes are
