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=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,94e5dd5646e21259
X-Google-Attributes: gid103376,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news1.google.com!news.glorb.com!newsgate.cistron.nl!xs4all!news.tele.dk!news.tele.dk!small.news.tele.dk!lnewsinpeer00.lnd.ops.eu.uu.net!emea.uu.net!peer-uk.news.demon.net!kibo.news.demon.net!mutlu.news.demon.net!news.demon.co.uk!demon!not-for-mail
From: Simon Wright <simon.j.wright@mac.com>
Newsgroups: comp.lang.ada
Subject: Re: Interfacing to C: multithreaded callbacks
Date: Wed, 13 Jun 2007 20:57:35 +0100
Organization: Pushface
Message-ID: <m2ps3z7hlc.fsf@mac.com>
References: <1181678190.757347.67290@x35g2000prf.googlegroups.com>
NNTP-Posting-Host: pogner.demon.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: news.demon.co.uk 1181764655 6015 62.49.19.209 (13 Jun 2007 19:57:35
 GMT)
X-Complaints-To: abuse@demon.net
NNTP-Posting-Date: Wed, 13 Jun 2007 19:57:35 +0000 (UTC)
Cancel-Lock: sha1:ektq02DsqrNgryK53cwgTDi/p+U=
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.95 (darwin)
Xref: g2news1.google.com comp.lang.ada:16181
Date: 2007-06-13T20:57:35+01:00
List-Id: <comp.lang.ada>

Maciej Sobczak <see.my.homepage@gmail.com> writes:

> Suppose there is a C library that creates additional threads
> (system- level threads in the pthread_create sense) and can call the
> client code back via function pointers that the client code provides
> to the library. Asynchronous I/O library that notifies the client
> about state changes can be a good motivating example.
>
> It is possible to pass Ada callback to the C library - it's enough
> to pragma Export(C, My_Procedure) and pass appropriate access to
> procedure. This way we could, for example, use the standard C
> function qsort.
>
> The problem is when the C library creates additional threads and
> calls the client back in the context of those threads. ARM says
> nothing (?)  about the relaion between Ada tasks and system
> threads. If the relation is 1:1 (ie. tasks are implemented as system
> threads), then the whole scheme might work just fine, provided that
> there is no task- specific data that Ada runtime expects and will
> not find. On the other hand, if the relation between tasks and
> threads is not 1:1, we will just enjoy undefined behavior.  Looks
> like a shaky ground.
>
> Is there any water-proof implementation pattern for such problems?
> Consider both the general case and then GNAT as the target Ada
> compiler on POSIX systems.

For GNAT, see GNAT.Threads.Register/Unregister_Thread -- they seem to
think it's quite tricky, maybe other vendors have a different slant.