From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Ada202X: Easy to use "UML private"-like components
Date: Thu, 11 Jul 2013 20:37:56 +0100
Organization: A noiseless patient Spider
Message-ID: <lyli5cvqej.fsf@pushface.org>
References: <69246de0-4b33-4d47-b5be-a45e8c911fb0@googlegroups.com>
	<wccwqpnux8n.fsf@shell01.TheWorld.com>
	<eabcaba2-a5aa-499d-a179-917f5dde79f3@googlegroups.com>
	<lya9luwg0u.fsf@pushface.org>
	<d22ab491-8be7-48e6-9f0c-af89d976619f@googlegroups.com>
	<ly61wiw6c5.fsf@pushface.org>
	<4d7e6232-1e3b-4ad8-b754-16d6e8642006@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx05.eternal-september.org;
 posting-host="c8504a89c76ea11bda6664e6198ae3cd";
	logging-data="6558"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX18HLpPoVoHPS2m+o6BABYFwdYOvRDjSH+w="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (darwin)
Cancel-Lock: sha1:Vc+2BJgr9BAosCxljeG5fXsfL+U=
	sha1:V57VfaRQ7ePy+UtrJH2uba58uWw=
Xref: news.eternal-september.org comp.lang.ada:16299
Date: 2013-07-11T20:37:56+01:00
List-Id: <comp.lang.ada>

Martin <martin@thedowies.com> writes:

> Sadly, our current UML tool comes with some strange defaults
> out-the-box, such that if you don't override the code-gen properties
> early (and preferably at top of model level) then all attributes are
> (C++) protected and not the visibly you selected for the
> attribute. And the visibility you selected for the attribute becomes
> the visibility of the set/get operations...ie what you see (on a Class
> Diagram) is _not_ what you get in the code!!! Horrific...and
> non-Do-178B (/C) compliant!!

Do you mean that it generates setters/getters for all the instance
variables? Evil! (and pointless, given what you say about the accessor
visibilities; why not just generate the attributes as required?)