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=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,19e4a2b12c5b43fa X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-01-22 14:08:35 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!newsfeed.vmunix.org!news-peer.gradwell.net!not-for-mail Newsgroups: comp.lang.ada From: porton@ex-code.com (Victor Porton) Date: Thu, 23 Jan 2003 01:29:16 +0500 References: Organization: Extreme Code Software (http://ex-code.com) Subject: Re: Intermixing two storage pools Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Content-Type: text/plain; charset=us-ascii X-URL: http://www.ex-code.com/ Message-ID: <3e2f1662$0$33931$bed64819@news.gradwell.net> NNTP-Posting-Date: 22 Jan 2003 22:08:34 GMT NNTP-Posting-Host: 195.149.39.13 X-Trace: 1043273314 news.gradwell.net 33931 mail2news/195.149.39.13 X-Complaints-To: news-abuse@gradwell.net Xref: archiver1.google.com comp.lang.ada:33356 Date: 2003-01-22T22:08:34+00:00 List-Id: In article , Robert A Duff writes: > porton@ex-code.com (Victor Porton) writes: > >> Are you sure, which item of Standard deprecates this? > > 13.11.2(16). How could it be otherwise? I meant the case when two pool variables share the same memory (e.g. one pool uses other for allocation). Well, I realize that eliminating this restriction would have bad impact on memory debuggers.