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-Thread: 103376,5b518364bbeba851
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!postnews1.google.com!k17g2000odb.googlegroups.com!not-for-mail
From: "Mattias Lindblad" <ml_news@matli.net>
Newsgroups: comp.lang.ada
Subject: Re: POSIX_Generic_Shared_Memory
Date: 22 Sep 2004 09:18:14 -0700
Organization: http://groups.google.com
Message-ID: <1095869894.188174.69560@k17g2000odb.googlegroups.com>
References: <1095700990.407634.230970@k26g2000oda.googlegroups.com>
   <slrncl34dr.mke.Colin_Paul_Gloster@vasa.acc.umu.se>
NNTP-Posting-Host: 136.163.203.3
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1095869894 28720 127.0.0.1 (22 Sep 2004 16:18:14
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Wed, 22 Sep 2004 16:18:14 +0000 (UTC)
User-Agent: G2/0.2
Complaints-To: groups-abuse@google.com
Injection-Info: k17g2000odb.googlegroups.com; posting-host=136.163.203.3;
   posting-account=5JRrfA0AAAB-ausM18rPNDG9yeoDg7W4
Xref: g2news1.google.com comp.lang.ada:3946
Date: 2004-09-22T09:18:14-07:00
List-Id: <comp.lang.ada>

I'm afraid that protected objects are not a possible solution in the
situation at hand. However, I have two different workarounds for the
issue. One is a simple patch to the Florist lib (which of course would
not be very portable given that Florist follows the standard), the
other is to ignore the functions in POSIX_Generic_Shared_Memory and do
the relevant function calls manually.

A third solution would of course be to create wrappers for the
corresponding C functions, but I'm trying to avoid such things.

But while I can solve the problem, I'm still interested in hearing if I
should blame the standards committee, the Florist programmers or myself
:)