From owner-freebsd-java Tue Jan 2 9:47:41 2001 From owner-freebsd-java@FreeBSD.ORG Tue Jan 2 09:47:39 2001 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from crewsoft.com (ns.aenet.net [157.22.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 5956237B400 for ; Tue, 2 Jan 2001 09:47:38 -0800 (PST) Received: from [172.17.1.64] (HELO wireless-networks.com) by crewsoft.com (CommuniGate Pro SMTP 3.3b5) with ESMTP id 395528 for freebsd-java@freebsd.org; Tue, 02 Jan 2001 09:50:06 -0800 Message-ID: <3A52145F.5092DD41@wireless-networks.com> Date: Tue, 02 Jan 2001 09:48:15 -0800 From: Cedric Berger X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD Java mailing list Subject: Re: Java ports References: <20010102122359.A786@c187104187.telekabel.chello.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Oh, and IMO, a .jar file is definitely a binary distro, it's *not* half-way > between source and binary, it's simply a binary. I've said it's half-way source/binary for the following reasons: 1) James Gosling said that he designed the java bytecode to match the often stack/tree-based intermediate representation you find between the front-end and the back-end of a compiler toolchain. 2) With any of the free java decompiler available, you can very very accurately recreate the full source code of any non-obfuscated jar file. You don't get the comments, but you have *everything* else. Boy, that's useful when, like me, you sometimes lose your sources. So "paranoid" sysadmins like Joshua can review the code. BTW a think the code should always be shipped along with the jar file. 3) You can patch it easily with jardiff or any basic zip tool. Cedric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message