Re: Automatic generation of accessor functions for a subview

I agree completely against default generation.
The generation should be selectable.

--- In anthemion-devtools%40yahoogroups.com">anthemion-devtoolsyahoogroups.com, Alec Ross <alec...> wrote:
&gt;
> In message <es45k4+icuv...>, Bengt Nilsson
> <bengt.nilsson11...> writes
&gt; >--- In anthemion-devtools%40yahoogroups.com">anthemion-devtoolsyahoogroups.com, Alec Ross <alec> wrote:
&gt; >>
> >> Hi Julian,
> >>
> >> -1 for accessors to be generated s a default.
> >
>; >Explain please.
>
> Hi Bengt,
&gt;
> What I mean is that I'm expressing a vote against accessors to be
> provided as a default. (Sorry about the typo in the original " s "
> should have been " as ".)
>
> I would be quite happy with generation of getters and/or setters being
> selectable, say by use of a checkbox. (Or two, if they were
separately
> selectable.)
>
> My reason for the vote is that I usually try to avoid using
accessors as
> far as possible. This is because they encourage leakage of information
> on implementation details, and that they offer a view that is often,
> IMHO, lower level than I'm attempting to achieve. That is not to say
> that sometimes they are not "just right";. Rather that over a range of
> apps, I don't find them appropriate for most data members.
>
> If they were generated I could always chose not to use them, of course;
> but they'd clutter up my view of the .cpp and, more importantly, the .h
> interface files.
&gt;
> Regards,
>
> Alec
>;
> [remainder of prior content snipped]
> --
> Alec Ross
>;

Messages in this topic (6) Reply (via web post) | Start a new topic

.