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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.107.14.10 with SMTP id 10mr5687085ioo.18.1518305503436; Sat, 10 Feb 2018 15:31:43 -0800 (PST) X-Received: by 10.157.94.15 with SMTP id d15mr284956oti.4.1518305503338; Sat, 10 Feb 2018 15:31:43 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.unit0.net!peer01.am4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!o66no436879ita.0!news-out.google.com!m16ni509itm.0!nntp.google.com!w142no438142ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sat, 10 Feb 2018 15:31:43 -0800 (PST) In-Reply-To: <752bb990-b70a-4fce-8cd7-91d4f8ee7ea1@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2601:191:8303:2100:7466:f44c:da21:40b1; posting-account=fdRd8woAAADTIlxCu9FgvDrUK4wPzvy3 NNTP-Posting-Host: 2601:191:8303:2100:7466:f44c:da21:40b1 References: <1892f04b-0223-4060-90a7-91983f775f18@googlegroups.com> <752bb990-b70a-4fce-8cd7-91d4f8ee7ea1@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: How to optimize use of RAM/disk access ? From: Robert Eachus Injection-Date: Sat, 10 Feb 2018 23:31:43 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Received-Body-CRC: 1101507498 X-Received-Bytes: 2031 Xref: reader02.eternal-september.org comp.lang.ada:50376 Date: 2018-02-10T15:31:43-08:00 List-Id: On Saturday, February 10, 2018 at 12:27:33 AM UTC-5, reinert wrote: > In general I would like to have an Ada function which tells how much memo= ry (in general hardware resources) is available. Maybe there is a "system f= unction" I have overlooked? If System.Memory_Size will help you, great. Look in your compiler's refer= ence manual to see what sort of a value you will get. (The Ada RM says imp= lementation defined and doesn't give hints to the implementer.) I haven't = found it of much use, since it often defines the limit of addressable (virt= ual) memory.