2008-12-26 04:25:01 +01:00
|
|
|
|
/*
|
|
|
|
|
|
SYNC-CLASSLOCK.hpp - special case of object based locking tied directly to a type
|
2010-12-17 23:28:49 +01:00
|
|
|
|
|
Copyright: clarify and simplify the file headers
* Lumiera source code always was copyrighted by individual contributors
* there is no entity "Lumiera.org" which holds any copyrights
* Lumiera source code is provided under the GPL Version 2+
== Explanations ==
Lumiera as a whole is distributed under Copyleft, GNU General Public License Version 2 or above.
For this to become legally effective, the ''File COPYING in the root directory is sufficient.''
The licensing header in each file is not strictly necessary, yet considered good practice;
attaching a licence notice increases the likeliness that this information is retained
in case someone extracts individual code files. However, it is not by the presence of some
text, that legally binding licensing terms become effective; rather the fact matters that a
given piece of code was provably copyrighted and published under a license. Even reformatting
the code, renaming some variables or deleting parts of the code will not alter this legal
situation, but rather creates a derivative work, which is likewise covered by the GPL!
The most relevant information in the file header is the notice regarding the
time of the first individual copyright claim. By virtue of this initial copyright,
the first author is entitled to choose the terms of licensing. All further
modifications are permitted and covered by the License. The specific wording
or format of the copyright header is not legally relevant, as long as the
intention to publish under the GPL remains clear. The extended wording was
based on a recommendation by the FSF. It can be shortened, because the full terms
of the license are provided alongside the distribution, in the file COPYING.
2024-11-17 23:42:55 +01:00
|
|
|
|
Copyright (C)
|
|
|
|
|
|
2008, Hermann Vosseler <Ichthyostega@web.de>
|
|
|
|
|
|
2023, Hermann Vosseler <Ichthyostega@web.de>
|
2010-12-17 23:28:49 +01:00
|
|
|
|
|
Copyright: clarify and simplify the file headers
* Lumiera source code always was copyrighted by individual contributors
* there is no entity "Lumiera.org" which holds any copyrights
* Lumiera source code is provided under the GPL Version 2+
== Explanations ==
Lumiera as a whole is distributed under Copyleft, GNU General Public License Version 2 or above.
For this to become legally effective, the ''File COPYING in the root directory is sufficient.''
The licensing header in each file is not strictly necessary, yet considered good practice;
attaching a licence notice increases the likeliness that this information is retained
in case someone extracts individual code files. However, it is not by the presence of some
text, that legally binding licensing terms become effective; rather the fact matters that a
given piece of code was provably copyrighted and published under a license. Even reformatting
the code, renaming some variables or deleting parts of the code will not alter this legal
situation, but rather creates a derivative work, which is likewise covered by the GPL!
The most relevant information in the file header is the notice regarding the
time of the first individual copyright claim. By virtue of this initial copyright,
the first author is entitled to choose the terms of licensing. All further
modifications are permitted and covered by the License. The specific wording
or format of the copyright header is not legally relevant, as long as the
intention to publish under the GPL remains clear. The extended wording was
based on a recommendation by the FSF. It can be shortened, because the full terms
of the license are provided alongside the distribution, in the file COPYING.
2024-11-17 23:42:55 +01:00
|
|
|
|
**Lumiera** is free software; you can redistribute it and/or modify it
|
|
|
|
|
|
under the terms of the GNU General Public License as published by the
|
|
|
|
|
|
Free Software Foundation; either version 2 of the License, or (at your
|
|
|
|
|
|
option) any later version. See the file COPYING for further details.
|
2008-12-26 04:25:01 +01:00
|
|
|
|
|
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
|
|
/** @file sync-classlock.hpp
|
|
|
|
|
|
** A special implementation of lib::Sync, where the storage of the object monitor
|
|
|
|
|
|
** is associated directly to a type rather then to a single object instance. While
|
|
|
|
|
|
** being problematic in conjunction with static startup/shutdown, doing so is sometimes
|
|
|
|
|
|
** necessary to setup type based dispatcher tables, managing singleton creation etc.
|
|
|
|
|
|
**
|
2008-12-26 05:44:49 +01:00
|
|
|
|
** @note simply using the ClassLock may cause a Monitor object (with a mutex) to be
|
|
|
|
|
|
** created at static initialisation and destroyed on application shutdown.
|
2018-04-01 05:33:44 +02:00
|
|
|
|
** @see depend.hpp usage example
|
2018-04-01 05:58:11 +02:00
|
|
|
|
** @see SyncClasslock_test
|
2008-12-26 04:25:01 +01:00
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#ifndef LIB_SYNC_CLASSLOCK_H
|
|
|
|
|
|
#define LIB_SYNC_CLASSLOCK_H
|
|
|
|
|
|
|
2009-01-26 01:09:49 +01:00
|
|
|
|
#include "lib/nobug-init.hpp"
|
2018-04-01 05:33:44 +02:00
|
|
|
|
#include "lib/zombie-check.hpp"
|
2018-10-01 05:51:21 +02:00
|
|
|
|
#include "lib/meta/util.hpp"
|
2008-12-26 04:25:01 +01:00
|
|
|
|
#include "lib/sync.hpp"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
namespace lib {
|
|
|
|
|
|
|
2008-12-26 05:44:49 +01:00
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
|
* A synchronisation protection guard employing a lock scoped
|
|
|
|
|
|
* to the parameter type as a whole, not an individual instance.
|
|
|
|
|
|
* After creating an instance, every other access specifying the same
|
|
|
|
|
|
* type is blocked.
|
2009-01-21 13:04:28 +01:00
|
|
|
|
* @note the Lock is recursive, because several instances within the same
|
|
|
|
|
|
* thread may want to acquire it at the same time without deadlock.
|
|
|
|
|
|
* @note there is a design sloppiness, as two instantiations of the
|
|
|
|
|
|
* ClassLock template with differing CONF count as different type.
|
|
|
|
|
|
* Actually using two different configurations within for a single
|
|
|
|
|
|
* class X should be detected and flagged as error, but actually
|
2025-06-07 23:59:57 +02:00
|
|
|
|
* just two non-shared lock instances get created silently. Beware!
|
2008-12-26 05:44:49 +01:00
|
|
|
|
* @see Sync::Lock the usual simple instance-bound variant
|
|
|
|
|
|
*/
|
2009-01-21 13:04:28 +01:00
|
|
|
|
template<class X, class CONF = RecursiveLock_NoWait>
|
2025-06-07 23:59:57 +02:00
|
|
|
|
class ClassLock
|
2008-12-26 04:25:01 +01:00
|
|
|
|
: public Sync<CONF>::Lock
|
|
|
|
|
|
{
|
2025-07-05 20:08:18 +02:00
|
|
|
|
using Lock = Sync<CONF>::Lock;
|
|
|
|
|
|
using Monitor = sync::Monitor<CONF>;
|
2008-12-26 04:25:01 +01:00
|
|
|
|
|
2009-01-21 13:04:28 +01:00
|
|
|
|
struct PerClassMonitor : Monitor {};
|
|
|
|
|
|
|
2008-12-26 05:44:49 +01:00
|
|
|
|
Monitor&
|
|
|
|
|
|
getPerClassMonitor()
|
2008-12-26 04:25:01 +01:00
|
|
|
|
{
|
2018-04-01 05:33:44 +02:00
|
|
|
|
static PerClassMonitor classMonitor;
|
2018-10-01 05:51:21 +02:00
|
|
|
|
static ZombieCheck zombieCheck{util::typeStr(this)};
|
2009-01-21 13:04:28 +01:00
|
|
|
|
|
2018-04-01 05:33:44 +02:00
|
|
|
|
zombieCheck();
|
|
|
|
|
|
return classMonitor;
|
2008-12-26 04:25:01 +01:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
public:
|
2023-10-14 23:40:57 +02:00
|
|
|
|
ClassLock()
|
|
|
|
|
|
: Lock{getPerClassMonitor()}
|
|
|
|
|
|
{ }
|
2008-12-26 04:25:01 +01:00
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
} // namespace lib
|
2018-03-31 17:27:13 +02:00
|
|
|
|
#endif /*LIB_SYNC_CLASSLOCK_H*/
|