Return-Path: Delivered-To: apmail-incubator-abdera-dev-archive@locus.apache.org Received: (qmail 613 invoked from network); 28 Sep 2006 15:45:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Sep 2006 15:45:30 -0000 Received: (qmail 18823 invoked by uid 500); 28 Sep 2006 15:45:29 -0000 Delivered-To: apmail-incubator-abdera-dev-archive@incubator.apache.org Received: (qmail 18806 invoked by uid 500); 28 Sep 2006 15:45:29 -0000 Mailing-List: contact abdera-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: abdera-dev@incubator.apache.org Delivered-To: mailing list abdera-dev@incubator.apache.org Received: (qmail 18797 invoked by uid 99); 28 Sep 2006 15:45:29 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Sep 2006 08:45:29 -0700 Authentication-Results: idunn.apache.osuosl.org header.from=rooneg@gmail.com; domainkeys=good X-ASF-Spam-Status: No, hits=0.5 required=5.0 tests=DNS_FROM_RFC_ABUSE DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 Received: from [66.249.82.225] ([66.249.82.225:30882] helo=wx-out-0506.google.com) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id FA/05-17533-71EEB154 for ; Thu, 28 Sep 2006 08:45:28 -0700 Received: by wx-out-0506.google.com with SMTP id s13so612737wxc for ; Thu, 28 Sep 2006 08:45:25 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=aK9LuGs+JJl4qHPa6lePMq8zm7bVpxAdHv2xB5tt1it2F15GmTEOgsV0/zmWC225QATwQkgJGxr590zO7ZRCppXK5E2JPoRsZGWbGKNP6/4x2eQXB3jpG8Lg6f/58djJUNPUqgrP2JRuQQ/1HzbPO+vK2/zTJJ1eM7wuoR/Lmsk= Received: by 10.70.113.15 with SMTP id l15mr3083293wxc; Thu, 28 Sep 2006 08:45:25 -0700 (PDT) Received: by 10.70.71.8 with HTTP; Thu, 28 Sep 2006 08:45:25 -0700 (PDT) Message-ID: <7edfeeef0609280845i4315c751g88748b844c1000fb@mail.gmail.com> Date: Thu, 28 Sep 2006 11:45:25 -0400 From: "Garrett Rooney" Sender: rooneg@gmail.com To: abdera-dev@incubator.apache.org Subject: Re: Coding/Language Standards In-Reply-To: <77474ff30609280838n77effebbh2d4f7a7923578b47@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <77474ff30609280725o42b1919coe672b575cfaed7c4@mail.gmail.com> <7edfeeef0609280729v42cdf83en57f0ad21c5a6ff65@mail.gmail.com> <77474ff30609280818v5e606bf3k8c9b05248cf24693@mail.gmail.com> <7edfeeef0609280828i52ea570bud7d75622b1e13184@mail.gmail.com> <77474ff30609280838n77effebbh2d4f7a7923578b47@mail.gmail.com> X-Google-Sender-Auth: 0445eb427c021486 X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 9/28/06, Harris Boyce III wrote: > Right and I think this is where the rub lies. I've been "brought-up" > that, unless the data is read-only, you just generally implement > read/write properties so I can easily implement it as: > > List Entries { > get; > } > > But even with that, nothing prevents the user accessing the feed from > calling theFeed.Entries.Add(someEntry); Now, the implementation could > return a read-only List and then any modifying operations would > generate exceptions. But...why would I do that? > > Does that make any sense? I'm hoping that this doesn't seem like an > immature conversation, but it's one that I struggle with when I study > Java. Why wouldn't I just use those conveience methods to modify the > list if and when I need to do so? > > Thanks again for the discussion! I'm learning lots! I wouldn't object to returning read-only lists in that sort of situation. Heck, I wouldn't object to doing so in Java either ;-) -garrett