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!.POSTED!not-for-mail
From: "Jeffrey R. Carter" <spam.jrcarter.not@spam.not.acm.org>
Newsgroups: comp.lang.ada
Subject: Re: A little trouble with very large arrays.
Date: Sat, 6 Oct 2018 23:40:52 +0200
Organization: Also freenews.netfront.net; news.tornevall.net;
 news.eternal-september.org
Message-ID: <ppba57$98m$1@dont-email.me>
References: <3f2828df-d54a-4427-bc3c-dc5ef0dc8069@googlegroups.com>
 <g1oe5gFjk04U1@mid.individual.net>
 <c457fabd-54ab-4294-a268-f3af228b241e@googlegroups.com>
 <g1plu7Frjb1U1@mid.individual.net>
 <13fa128f-5ec7-453e-9231-2260dd4adcbc@googlegroups.com>
 <ppamf9$ebu$1@dont-email.me>
 <3226be36-848e-4793-b52c-3295f8e9a67b@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sat, 6 Oct 2018 21:40:55 -0000 (UTC)
Injection-Info: reader02.eternal-september.org;
 posting-host="d522ac35df2215f299a458549273e036";
	logging-data="9494"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1+lU3GTcFs4NX4qr4tcTMRqG9dt43tzXDo="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
Cancel-Lock: sha1:CtP9OEGNlEX7EnAL+es7kSqkdUw=
In-Reply-To: <3226be36-848e-4793-b52c-3295f8e9a67b@googlegroups.com>
Content-Language: en-US
Xref: reader02.eternal-september.org comp.lang.ada:54510
Date: 2018-10-06T23:40:52+02:00
List-Id: <comp.lang.ada>

On 10/06/2018 08:49 PM, Shark8 wrote:
> 
> For our specific usage *RIGHT NOW*, sure.
> All that's *REALLY* required, for the Telescope's production-side is writing out those blocks, this is true... but doing it this way would be kneecapping myself in the sense of maintenance & usability. (Like global-variables/states.)

Of course you'd also implement

Image : FITS.Image_Handle := FITS.Read ("George");

But there still doesn't seem to be a reason to store a FITS object.

-- 
Jeff Carter
"We burst our pimples at you."
Monty Python & the Holy Grail
16