Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx05.eternal-september.org!.POSTED!not-for-mail From: Jim Janney Newsgroups: comp.lang.java.programmer Subject: Re: multiple inheritance in Java Date: Fri, 05 Jul 2013 11:17:18 -0600 Organization: bilaterally symmetric Lines: 24 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx05.eternal-september.org; posting-host="c75a2e3068ccf6c98395286f3e40b97d"; logging-data="8037"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/qnTMdN3OzTN+N5myl2yFc" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) Cancel-Lock: sha1:1NgONASawMzhpQiLkoR6Yi65M+4= sha1:GFgQJYjBiRVpFTCL6OVDkbdiSOA= Xref: csiph.com comp.lang.java.programmer:24656 Jim Janney writes: > On the other hand, and this is probably more important, the Java > community sets great store on always doing things the usual way, and > this has turned into a strength for the language: you can pull a > third-party library library into a project and expect that it will work > with and follow the same conventions as the rest of the code. Recently I've been looking at an interesting exception to this, JSch: http://www.jcraft.com/jsch/ If you do a little searching on the web you can find lots of complaints that the code isn't very Java-ish, and on my own reading of the source I tend to agree. It nevertheless continues to be a successful project with widespread use, and I think there's a reason for that. SSH has a well-defined standard and the code is a faithful implementation of that. Once you study the standards document, the JSch code starts to make sense. It's also a stable protocol that seems unlikely to change, so there's not a lot of reason to want to extend it yourself. But most projects aren't like that. -- Jim Janney