On Fri, 12 Jul 2013 16:01:30 +0100, sebb wrote:
On 12 July 2013 15:39, Ajo Fod wrote:
I wonder what conditions justify the use of protected / public
fields?
I can see how protected fields make more sense for a single user
code
because it is easier to not have all those getter/setter method
I like the last few arguments about multi threaded environments. That makes
the getter/setter paradigm desirable even in single user environments.
Thanks for the thoughtful arguments.
On Fri, Jul 12, 2013 at 8:01 AM, sebb wrote:
> On 12 July 2013 15:39, Ajo Fod wrote:
> > I wonder what condi
On 12 July 2013 15:39, Ajo Fod wrote:
> I wonder what conditions justify the use of protected / public fields?
>
> I can see how protected fields make more sense for a single user code
> because it is easier to not have all those getter/setter methods. But
> perhaps for an API with a wide audien
I wonder what conditions justify the use of protected / public fields?
I can see how protected fields make more sense for a single user code
because it is easier to not have all those getter/setter methods. But
perhaps for an API with a wide audience, the commitment of providing a
field is a big
A somewhat more academic rationale why making fields protected may be an
issue, can be found here: http://dl.acm.org/citation.cfm?id=28702
Benedikt
2013/7/12 Ajo Fod
> I see. That makes sense now.
>
> Thanks.
>
> On Thursday, July 11, 2013, Phil Steitz wrote:
>
> > On 7/11/13 12:09 PM, Luc Mai
I see. That makes sense now.
Thanks.
On Thursday, July 11, 2013, Phil Steitz wrote:
> On 7/11/13 12:09 PM, Luc Maisonobe wrote:
> > Hi Ajo,
> >
> > Le 11/07/2013 20:38, Ajo Fod a écrit :
> >> More classes can be used/extended if fields generally default to
> protected
> >> instead of private as
On 7/11/13 12:09 PM, Luc Maisonobe wrote:
> Hi Ajo,
>
> Le 11/07/2013 20:38, Ajo Fod a écrit :
>> More classes can be used/extended if fields generally default to protected
>> instead of private as it seems it does in classes in CM now.
>>
>> Case in point is in : https://issues.apache.org/jira/bro
Hi Ajo,
Le 11/07/2013 20:38, Ajo Fod a écrit :
> More classes can be used/extended if fields generally default to protected
> instead of private as it seems it does in classes in CM now.
>
> Case in point is in : https://issues.apache.org/jira/browse/MATH-1003
In fact, having protected members i
More classes can be used/extended if fields generally default to protected
instead of private as it seems it does in classes in CM now.
Case in point is in : https://issues.apache.org/jira/browse/MATH-1003
Cheers,
Ajo
