From 24582e4a271597c3382cd894c8478586e146b302 Mon Sep 17 00:00:00 2001 From: Jeff Hill Date: Thu, 1 May 2003 22:33:41 +0000 Subject: [PATCH] reformmatting --- src/cas/io/bsdSocket/casDGIntfIO.cc | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/src/cas/io/bsdSocket/casDGIntfIO.cc b/src/cas/io/bsdSocket/casDGIntfIO.cc index 29f61bc0a..7299586e7 100644 --- a/src/cas/io/bsdSocket/casDGIntfIO.cc +++ b/src/cas/io/bsdSocket/casDGIntfIO.cc @@ -96,9 +96,9 @@ casDGIntfIO::casDGIntfIO ( caServerI & serverIn, clientBufMemoryManager & memMgr // { osiSockAddrNode *pAddr; - ELLLIST tmpList; + ELLLIST tmpList; - ellInit ( &tmpList ); + ellInit ( &tmpList ); osiSockDiscoverBroadcastAddresses (&tmpList, this->sock, &serverAddr); // match addr removeDuplicateAddresses ( &BCastAddrList, &tmpList, 1 ); @@ -184,17 +184,18 @@ casDGIntfIO::casDGIntfIO ( caServerI & serverIn, clientBufMemoryManager & memMgr } } - // + // // Solaris specific: - // If they are binding to a particular interface then - // we will also need to bind to the broadcast address - // for that interface (if it has one). This allows + // If they are binding to a particular interface then + // we will also need to bind to the broadcast address + // for that interface (if it has one). This allows // broadcast packets to be received, but we must reply // through the "normal" UDP binding or the client will // appear to receive replies from the broadcast address. // Since it should never be valid to fill in the UDP // source address as the broadcast address, then we must - // conclude that the Solaris implementation is broken. + // conclude that the Solaris implementation is at least + // partially broken. // // WIN32 specific: // On windows this appears to only create problems because