I'm checking this in.
Mark found a buglet in MulticastSocket.setTimeToLive.
Tom
Index: ChangeLog
from Tom Tromey <[EMAIL PROTECTED]>
PR libgcj/31093:
* java/net/MulticastSocket.java (setTimeToLive): Allow ttl==0.
Index: java/net/MulticastSocket.java
===================================================================
RCS file: /cvsroot/classpath/classpath/java/net/MulticastSocket.java,v
retrieving revision 1.28
diff -u -r1.28 MulticastSocket.java
--- java/net/MulticastSocket.java 25 Oct 2006 00:45:41 -0000 1.28
+++ java/net/MulticastSocket.java 8 Mar 2007 21:46:20 -0000
@@ -1,5 +1,5 @@
/* MulticastSocket.java -- Class for using multicast sockets
- Copyright (C) 1998, 1999, 2000, 2001, 2002, 2003
+ Copyright (C) 1998, 1999, 2000, 2001, 2002, 2003, 2007
Free Software Foundation, Inc.
This file is part of GNU Classpath.
@@ -337,7 +337,7 @@
/**
* Sets the "Time to Live" value for a socket. The value must be between
- * 1 and 255.
+ * 0 and 255, inclusive.
*
* @param ttl The new TTL value
*
@@ -350,7 +350,7 @@
if (isClosed())
throw new SocketException("socket is closed");
- if (ttl <= 0 || ttl > 255)
+ if (ttl < 0 || ttl > 255)
throw new IllegalArgumentException("Invalid ttl: " + ttl);
getImpl().setTimeToLive(ttl);
