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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,cd2949b907b1f9dd,start X-Google-Attributes: gid103376,public From: Michiel Perdeck Subject: mapping of tasking to the OS Date: 1996/12/06 Message-ID: <32A7D1E0.3682@sni.de>#1/1 X-Deja-AN: 202654470 content-type: text/plain; charset=us-ascii organization: SNI - SCAP mime-version: 1.0 newsgroups: comp.lang.ada x-mailer: Mozilla 2.02 (Win95; I) Date: 1996-12-06T00:00:00+00:00 List-Id: I am gathering ammunition to propagate the use of Ada in my company (CMG plc) and I have the following question: Ada supports tasking (multithreading) on the level of the language itself, as opposed to most other languages which leave this to OS calls who's semantics are not part of the language definition. I think that the Ada approach has the great advantage of making it possible to formally specify (a program is a formal specification) the concurrency aspect of a system. But... How does the Ada tasking map to a particular operating system? Are there standard ways for this mapping in e.g. Unix (with and without lightweight processes), OS/2, Win95, NT, etc.? And what about some of the well-know C/Unix constructs like fork/exec, does that have an equivalent in Ada? I know that some of my collegues (specifically the Unix affictionado's) will want to be certain how specific multi-tasking constructs are mapped onto the OS! (And don't tell me that one can of course use OS calls in Ada.) Regards, Michiel Perdeck ---------------------- michiel.perdeck@cmg.nl michiel.perdeck@tip.nl