Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 14505 invoked from network); 13 Apr 2002 16:45:11 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 13 Apr 2002 16:45:11 -0000 Received: (qmail 8158 invoked by uid 97); 13 Apr 2002 16:45:13 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 8142 invoked by uid 97); 13 Apr 2002 16:45:13 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 8131 invoked from network); 13 Apr 2002 16:45:12 -0000 Date: Sat, 13 Apr 2002 12:45:10 -0400 (EDT) From: Henri Yandell X-X-Sender: To: Jakarta Commons Developers List Subject: Re: WeakHashSet collection In-Reply-To: <000d01c1e27d$7ce07a00$1200a8c0@dsl6419231101.telocity.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N It sounds lke it fits the purpose, unless there is a way in Java 1.2 to emulate the functionality. Generally the way to submit a single class like this would be to send an email with [SUBMIT] WeakHashSet as the title, briefly describe the class and attach the source. The person who submits would normally handle the licencing I believe. Another option is, rather than attaching the source code, to provide a url which has the javadoc, source code, and a description at. This is mainly a courtesy thing as a large email onto a mail list can be bad. So if you've got a 50k source jar or something, this might be the approach to take. For a single class it's not worth it. In terms of marketing your class, the email gets direct attention, the url provides the ability to easily read javadoc which is often a nice way to get into code. I don't believe there are any project standard styles (beyond the java ones) so after someone reviews the code the most likely changes would either be javadoc improvement if it was felt that something wasn't being said, or some aspect of the Set interface not being adhered to. For example, when you return elements to the set through an iterator, are they weak links still and does the remove() still work. Usuaully this is a big deal with Maps and the netrySet() method. I hope that helps. Just throw the source code out here. :) [Oh, and I probably should have given you a URL about code submission. http://jakarta.apache.org/site/getinvolved.html and http://jakarta.apache.org/site/contributing.html although they're not Commons specific.] Hen On Fri, 12 Apr 2002, Jeff Keyser wrote: > Hello, > > I recently created a WeakHashSet collection for a project I am currently > working on. (Items in the Set can be garbage collected if references to > them outside the Set are released.) I believe it may also be useful to > others, and would like to contribute it to the Collections project. Would > such a collection fit the intended purpose of this project? If so, what > would be the best way to contribute it, and what specific changes might I > need to make to the code (project, license comments, etc.)? > > Thanks. > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > -- To unsubscribe, e-mail: For additional commands, e-mail: