1 ------------------------------------------------------------------------------
3 -- GNAT RUN-TIME COMPONENTS --
5 -- G N A T . T A S K _ L O C K --
9 -- Copyright (C) 1998-2005, AdaCore --
11 -- GNAT is free software; you can redistribute it and/or modify it under --
12 -- terms of the GNU General Public License as published by the Free Soft- --
13 -- ware Foundation; either version 2, or (at your option) any later ver- --
14 -- sion. GNAT is distributed in the hope that it will be useful, but WITH- --
15 -- OUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY --
16 -- or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License --
17 -- for more details. You should have received a copy of the GNU General --
18 -- Public License distributed with GNAT; see file COPYING. If not, write --
19 -- to the Free Software Foundation, 51 Franklin Street, Fifth Floor, --
20 -- Boston, MA 02110-1301, USA. --
22 -- As a special exception, if other files instantiate generics from this --
23 -- unit, or you link this unit with other files to produce an executable, --
24 -- this unit does not by itself cause the resulting executable to be --
25 -- covered by the GNU General Public License. This exception does not --
26 -- however invalidate any other reasons why the executable file might be --
27 -- covered by the GNU Public License. --
29 -- GNAT was originally developed by the GNAT team at New York University. --
30 -- Extensive contributions were provided by Ada Core Technologies Inc. --
32 ------------------------------------------------------------------------------
34 -- Simple task lock and unlock routines
36 -- A small package containing a task lock and unlock routines for creating
37 -- a critical region. The lock involved is a global lock, shared by all
38 -- tasks, and by all calls to these routines, so these routines should be
39 -- used with care to avoid unnecessary reduction of concurrency.
41 -- These routines may be used in a non-tasking program, and in that case
42 -- they have no effect (they do NOT cause the tasking runtime to be loaded).
44 package GNAT
.Task_Lock
is
45 pragma Elaborate_Body
;
49 -- Acquires the global lock, starts the execution of a critical region
50 -- which no other task can enter until the locking task calls Unlock
53 pragma Inline
(Unlock
);
54 -- Releases the global lock, allowing another task to successfully
55 -- complete a Lock operation. Terminates the critical region.
57 -- The recommended protocol for using these two procedures is as
60 -- Locked_Processing : begin
69 -- end Locked_Processing;
71 -- This ensures that the lock is not left set if an exception is raised
72 -- explicitly or implicitly during the critical locked region.
74 -- Note on multiple calls to Lock: It is permissible to call Lock
75 -- more than once with no intervening Unlock from a single task,
76 -- and the lock will not be released until the corresponding number
77 -- of Unlock operations has been performed. For example:
79 -- GNAT.Task_Lock.Lock; -- acquires lock
80 -- GNAT.Task_Lock.Lock; -- no effect
81 -- GNAT.Task_Lock.Lock; -- no effect
82 -- GNAT.Task_Lock.Unlock; -- no effect
83 -- GNAT.Task_Lock.Unlock; -- no effect
84 -- GNAT.Task_Lock.Unlock; -- releases lock
86 -- However, as previously noted, the Task_Lock facility should only
87 -- be used for very local locks where the probability of conflict is
88 -- low, so usually this kind of nesting is not a good idea in any case.
89 -- In more complex locking situations, it is more appropriate to define
90 -- an appropriate protected type to provide the required locking.
92 -- It is an error to call Unlock when there has been no prior call to
93 -- Lock. The effect of such an erroneous call is undefined, and may
94 -- result in deadlock, or other malfunction of the run-time system.