threadlock 1.3.1 → 1.3.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +9 -4
  3. metadata +2 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 7bf65479043db4fdee700ed4d46fcaa08be8b463
4
- data.tar.gz: c8e5f1d8aa8c7c057231e6b386ddb44666d99936
3
+ metadata.gz: 33ebf8fec51c4c95030192a3630f9394f67f6d4d
4
+ data.tar.gz: 525d769959c4275dcf50c073b5950f076f0b8bcf
5
5
  SHA512:
6
- metadata.gz: 60290c01d87a1f99e7efd81f402bf5bd07802a46bc4e219265b1e71fe1c89e598e50af4407c8643b5424b3e240442a08fa8b95237ccf2dde77d0b4e71e08e435
7
- data.tar.gz: c254e8a7bc7e77361ad4bec9bc2e9b6276ea65024b19f785f6e2e5370059a3d615c71b40d7bdb0e3f42575bb667980cefa13d629f7caf62b39af0946c2d52406
6
+ metadata.gz: 96a12c56eda8fe667a7e5a260e75da6980cffad338bf3415f925164ff94a8cfeca0c73e2336a74d26adca8cbcb5bf2d2978f60a07a432779d223f1b629787da0
7
+ data.tar.gz: c93bc456a06b3d38039ba8f7026c24316f50c4f91d0b2b19c397133d740fa7c18aafd6abe5d02105851a001fc05d146650fa966540718df253b3145ceda263ac
data/README.md CHANGED
@@ -1,13 +1,18 @@
1
1
  threadlock
2
2
  ==========
3
3
 
4
- Use the threadlock function in your class definition to automatically run instance methods inside of an instance-wide re-entrant lock (Monitor).
4
+ Use the threadlock function in your class definition to automatically run instance methods inside of an instance-wide re-entrant lock (Monitor).
5
5
 
6
- All locked methods in an instance are protect by a single lock. You can protect all or some of your methods from being run asynchronously. The goal is to be able to easily make basic objects threadsafe with as little thought and code as using the attr_accessor family of functions to make your instance attributes accessible.
6
+ All locked methods in an instance are protect by a single lock. Alternatively, you can specify a custom lock, which need not be a Monitor; it can be anything that implements $synchronize
7
7
 
8
- The codebase is small and I intend to keep it that way, but bug reports and patches are welcome.
8
+ You can protect all or some of your methods from being run asynchronously.
9
+
10
+ In Ruby>=2.1, threadlock can also be syntactically used as a decorator.
11
+
12
+ See USAGE.rb for usage examples.
9
13
 
10
14
  Enjoy.
11
15
 
12
16
  Copyright 2013 : Joe McIlvain
13
- MIT Licensed.
17
+
18
+ (MIT License)
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: threadlock
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.3.1
4
+ version: 1.3.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Joe McIlvain
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2013-09-29 00:00:00.000000000 Z
11
+ date: 2013-10-06 00:00:00.000000000 Z
12
12
  dependencies: []
13
13
  description: 'Use the threadlock function in your class definition to automatically
14
14
  run instance methods inside of an instance-wide re-entrant lock (Monitor). All