From e434bff7425f4873555ef3d59815ad3bad658baa Mon Sep 17 00:00:00 2001 From: Thomas Punt Date: Tue, 13 Feb 2018 12:17:03 +0000 Subject: [PATCH] Properly remove renamed files... (I hate svn) git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@344252 c90b9560-bf6c-de11-be94-00142212c4b1 --- reference/pht/atomicinteger.xml | 82 -------------------------------- reference/pht/hashtable.xml | 84 --------------------------------- reference/pht/queue.xml | 77 ------------------------------ reference/pht/runnable.xml | 69 --------------------------- reference/pht/thread.xml | 74 ----------------------------- reference/pht/threaded.xml | 75 ----------------------------- reference/pht/vector.xml | 84 --------------------------------- 7 files changed, 545 deletions(-) delete mode 100644 reference/pht/atomicinteger.xml delete mode 100644 reference/pht/hashtable.xml delete mode 100644 reference/pht/queue.xml delete mode 100644 reference/pht/runnable.xml delete mode 100644 reference/pht/thread.xml delete mode 100644 reference/pht/threaded.xml delete mode 100644 reference/pht/vector.xml diff --git a/reference/pht/atomicinteger.xml b/reference/pht/atomicinteger.xml deleted file mode 100644 index a9e0e6532d..0000000000 --- a/reference/pht/atomicinteger.xml +++ /dev/null @@ -1,82 +0,0 @@ - - - - - - The AtomicInteger class - AtomicInteger - - - - -
- &reftitle.intro; - - The AtomicInteger class is currently the only - supported atomic value. It allows for an integer to be safely passed around - between, and manipulated, by multiple threads. The methods exposed by this - class do not need mutex locking, since they will acquire the internal mutex - lock implicitly. AtomicInteger::lock and - AtomicInteger::unlock are still exposed, however, - for when multiple operations involving the same - AtomicInteger object need to be grouped together. - - - The mutex locks of the atomic values are reentrant safe. - -
- - -
- &reftitle.classsynopsis; - - - - AtomicInteger - - - - - AtomicInteger - - - - Threaded - - - - - &Methods; - - - - - -
- -
- - &reference.pht.entities.atomicinteger; - -
- - diff --git a/reference/pht/hashtable.xml b/reference/pht/hashtable.xml deleted file mode 100644 index 6f478271de..0000000000 --- a/reference/pht/hashtable.xml +++ /dev/null @@ -1,84 +0,0 @@ - - - - - - The HashTable class - HashTable - - - - -
- &reftitle.intro; - - The HashTable class is one of the Inter-Thread - Communication (ITC) data structures exposed by pht. It can be safely passed - around between threads, and manipulated by multiple threads using the mutex - locks that have been packed in with the data structure. It is - reference-counted across threads, and so it does not need to be explicitly - destroyed. - - - The HashTable class enables for array access upon - its objects (along with the isset and - unset functions). The - ArrayAccess interface is not explicitly implemented, - however, because it is only needed for such abilities by userland classes. - -
- - -
- &reftitle.classsynopsis; - - - - HashTable - - - - - HashTable - - - - Threaded - - - - - &Methods; - - - - - -
- -
- - &reference.pht.entities.hashtable; - -
- - diff --git a/reference/pht/queue.xml b/reference/pht/queue.xml deleted file mode 100644 index e0ac57ac37..0000000000 --- a/reference/pht/queue.xml +++ /dev/null @@ -1,77 +0,0 @@ - - - - - - The Queue class - Queue - - - - -
- &reftitle.intro; - - The Queue class is one of the Inter-Thread - Communication (ITC) data structures exposed by pht. It can be safely passed - around between threads, and manipulated by multiple threads using the mutex - locks that have been packed in with the data structure. It is - reference-counted across threads, and so it does not need to be explicitly - destroyed. - -
- - -
- &reftitle.classsynopsis; - - - - Queue - - - - - Queue - - - - Threaded - - - - - &Methods; - - - - - -
- -
- - &reference.pht.entities.queue; - -
- - diff --git a/reference/pht/runnable.xml b/reference/pht/runnable.xml deleted file mode 100644 index 47cf15f540..0000000000 --- a/reference/pht/runnable.xml +++ /dev/null @@ -1,69 +0,0 @@ - - - - - - The Runnable interface - Runnable - - - - -
- &reftitle.intro; - - The Runnable interface enforces the - implementation of a run() method on classes that should be threaded. This - method acts as the entry point of the threaded class. - -
- - -
- &reftitle.interfacesynopsis; - - - - Runnable - - - - - Runnable - - - - &Methods; - - - - - -
- -
- - &reference.pht.entities.runnable; - -
- - diff --git a/reference/pht/thread.xml b/reference/pht/thread.xml deleted file mode 100644 index ae33c3ba76..0000000000 --- a/reference/pht/thread.xml +++ /dev/null @@ -1,74 +0,0 @@ - - - - - - The Thread class - Thread - - - - -
- &reftitle.intro; - - The Thread class abstracts away a native thread. It - has an internal task queue, where the methods - Thread::addClassTask, - Thread::addFunctionTask, and - Thread::addFileTask push new tasks onto this - queue. Invoking the Thread::start method will - cause the new thread to be spawned, where it will then begin working - through the task queue. A thread may be reused for any number of tasks. - -
- - -
- &reftitle.classsynopsis; - - - - Thread - - - - - Thread - - - - &Methods; - - - - - -
- -
- - &reference.pht.entities.thread; - -
- - diff --git a/reference/pht/threaded.xml b/reference/pht/threaded.xml deleted file mode 100644 index 066ad164cf..0000000000 --- a/reference/pht/threaded.xml +++ /dev/null @@ -1,75 +0,0 @@ - - - - - - The Threaded interface - Threaded - - - - -
- &reftitle.intro; - - The Threaded interface is an internal interface used - by the Inter-Thread Communication (ITC) data structures - (HashTable, Queue, and - Vector). It allows those data structures to be - threaded and ensures that the mutex locking API - (Threaded::lock and - Threaded::unlock) is implemented by each of the - ITC data structures. It is not implementable by userland classes (since - standalone mutex locks are not exposed). - -
- - -
- &reftitle.interfacesynopsis; - - - - Threaded - - - - - Threaded - - - - &Methods; - - - - - -
- -
- - &reference.pht.entities.threaded; - -
- - diff --git a/reference/pht/vector.xml b/reference/pht/vector.xml deleted file mode 100644 index 37d4d18f38..0000000000 --- a/reference/pht/vector.xml +++ /dev/null @@ -1,84 +0,0 @@ - - - - - - The Vector class - Vector - - - - -
- &reftitle.intro; - - The Vector class is one of the Inter-Thread - Communication (ITC) data structures exposed by pht. It can be safely passed - around between threads, and manipulated by multiple threads using the mutex - locks that have been packed in with the data structure. It is - reference-counted across threads, and so is does not need to be explicitly - destroyed. - - - The Vector class enables for array access upon - its objects (along with the isset and - unset functions). The - ArrayAccess interface is not explicitly implemented, - however, because it is only needed for such abilities by userland classes. - -
- - -
- &reftitle.classsynopsis; - - - - Vector - - - - - Vector - - - - Threaded - - - - - &Methods; - - - - - -
- -
- - &reference.pht.entities.vector; - -
- -