Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 53123 invoked from network); 12 Dec 2000 11:49:50 -0000 Received: from unknown (HELO slim.silverstream.com) (216.142.115.9) by locus.apache.org with SMTP; 12 Dec 2000 11:49:50 -0000 Received: by slim.silverstream.com with Internet Mail Service (5.5.2650.21) id ; Mon, 11 Dec 2000 21:01:23 -0500 Received: from ROSEN ([10.129.101.130]) by shady.silverstream.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id YWNY3J5H; Mon, 11 Dec 2000 20:59:26 -0500 From: "Rosen, Alex" To: ant-dev@jakarta.apache.org Subject: RE: ant 2 Date: Mon, 11 Dec 2000 21:01:06 -0500 Message-ID: <005901c063df$647a5710$8265810a@silverstream.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal In-Reply-To: <3.0.6.32.20001212111526.00b31410@latcs2.cs.latrobe.edu.au> X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > I guess we need some way to tell > other developers which parts are static and "public" and which are > "private" parts of project. Sounds like a good idea, although I think that actually enforcing this, like Java does, is too heavy-handed. A naming convension suggested in the doc might be the way to go here - e.g. either prefix all the private elements with "pv", or the public ones with "pub". This would serve as a warning not to use anything marked private, but you could do it if you had to. --Alex