Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA24153; Sat, 9 Dec 95 15:43:48 EST Received: from liquor.cabi.net by MIT.EDU with SMTP id AA04603; Sat, 9 Dec 95 15:43:47 EST Received: (from listadm@localhost) by liquor.cabi.net (8.6.12/8.6.12) id PAA09060; Sat, 9 Dec 1995 15:29:54 -0500 Resent-Date: Sat, 9 Dec 1995 15:29:54 -0500 X-Sender: chapman@saul5.u.washington.edu Date: Sat, 9 Dec 1995 12:26:17 -0800 (PST) From: Randy Chapman To: Thomas Boutell Cc: java-linux@java.blackdown.org Subject: Re: Determining interfaces from .class file? In-Reply-To: <199512092023.AA01038@boutell.com> Message-Id: Foo: foo-bar Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-Id: <"qKFzX1.0._C2.Y6Vom"@liquor> Resent-From: java-linux@java.blackdown.org X-Mailing-List: archive/latest/699 X-Loop: java-linux@java.blackdown.org Precedence: list Resent-Sender: java-linux-request@java.blackdown.org javap does this job quite nicely. It can even disassemble into java assembly, if you want that for some odd reason. --randy On Sat, 9 Dec 1995, Thomas Boutell wrote: > I'm doing some work with the .class files provided in the > sun.* packages, which are separate from the java.* packages > in that there is no source code provided for them. > > Am I missing something, or is there no way to reconstruct > what interfaces are available? Is there some standard > tool for this? I want to figure out what kind of > exceptions/errors the java.net.DatagramSocket class > throws so I can catch them. > > -T > >