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=0.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,534dd301375921ac
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.193.129 with SMTP id ho1mr8160453pbc.8.1339812042943;
        Fri, 15 Jun 2012 19:00:42 -0700 (PDT)
Path: 
 l9ni55650pbj.0!nntp.google.com!news1.google.com!news.glorb.com!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: BrianG <me@null.email>
Newsgroups: comp.lang.ada
Subject: Re: Is Text_IO.Put_Line() thread-safe?
Date: Fri, 15 Jun 2012 22:00:40 -0400
Organization: A noiseless patient Spider
Message-ID: <jrgpc9$a2u$1@dont-email.me>
References: <93201f1a-d668-485e-83b4-492bc283f36e@googlegroups.com>
 <jrdc48$14h2$1@adenine.netfront.net>
 <3fff1269-06f5-47a2-bc10-c2145b3a297d@googlegroups.com>
 <jrdntv$1fi9$1@adenine.netfront.net>
Mime-Version: 1.0
Injection-Date: Sat, 16 Jun 2012 02:00:42 +0000 (UTC)
Injection-Info: mx04.eternal-september.org;
 posting-host="sUrC0xRwf73oxX3tf6U0cw";
	logging-data="10334"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1+gyD0dpflzVQ+LW85a9mh1"
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.2.24) Gecko/20111108 Thunderbird/3.1.16
In-Reply-To: <jrdntv$1fi9$1@adenine.netfront.net>
Cancel-Lock: sha1:S6uJ2v9Df21UFnlesicH8T54Wx0=
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date: 2012-06-15T22:00:40-04:00
List-Id: <comp.lang.ada>

On 06/14/2012 06:17 PM, Jeffrey Carter wrote:
> On 06/14/2012 01:50 PM, awdorrin wrote:
>>
>> It is a mess, and if I could re-design the whole thing, I would.
>> Unfortunately I'm being told 'make it work' and that since the
>> application
>> has been used for 25+ years on the other platforms that there isn't
>> anything
>> wrong with the design.
>
> That hardly follows. People use badly designed things all the time. For
> decades the standard design for plumbing was 2 separate faucets (hot and
> cold) each with its own valve. That's a terrible design from a usability
> standpoint. Then came a single faucet with separate valves for hot and
> cold. That's better, but determining the valve positions for a desired
> combination of water temperature and pressure is difficult. A much
> better design is a single faucet with independent controls for
> temperature and pressure.
>
Sounds like that was part of the direction given, not a choice made (by 
the recipient of the direction).  You can't necessarily expect sense in 
what you're told to do.

On the Put_Line issue, why not simply wrap it in a protected object, and 
change Ada.Text_IO ref's to that object?  That won't help with the 
sequence-of-calls issues; you'd need individual protected calls for each 
sequence.

-- 
---
BrianG
000
@[Google's email domain]
.com