scoped_attr_accessor 1.0.1 → 1.0.2

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 9fd58a73e8641fcfbd9205039fad4c77fb1920a2
+  data.tar.gz: 788bb68336faabada51d7454d56769bea5924830
+SHA512:
+  metadata.gz: 4edfae715f4bbb70688ba3326e4928f174e2174d646834f9772d4aeb75c453c092accce186762805148e88a3a63fa4ee57a4a89d5a9524da701615f8d98af08a
+  data.tar.gz: f92e78883d16dc0d5220ef4aeab45fd1fd956c79de9bfb963390ca2bf58e389a6287992aa190c25dcd15e65edf7f45c2b05862f53f9db194b0fade829bec1a0e

data/README.md

@@ -59,7 +59,9 @@ classes able to have protected and private accessors.
 
 The '/include' form of this gem is a ruby-wide monkeypatch. Please
 remember that it's perfectly fine to use it this way in your own
-applications, but quite rude to use it this way in a library.
+applications, but quite rude to use it this way in a library. People
+who use your library would then be infected by this monkeypatch as
+well. Not cool.
 
 If you use scoped accessors in a gem or library of your own, please
 consider using the non-include version, or, in Ruby 2.0, use
@@ -85,12 +87,12 @@ general is somewhat divided on the meaning of the concept of privacy
 in ruby. For some, especially those who come from Java, C++, VB, or
 some other language that enforces encapsulation with privacy, ruby's
 ability to get around privacy means that encapsulation cannot be
-enforced. Most of us (I count myself in this camp) have discarded the
-use of privacy in ruby altogether, as if it were nothing more than a
-half-hearted nod to other languages' encapsulation practices. Make
-everything public, since everything's ultimately public anyway, we
-say; using the private keyword is merely a speedbump which adds no
-security but does add hassle and headache.
+enforced. Most of us (I have counted myself in this camp until now)
+have discarded the use of privacy in ruby altogether, as if it were
+nothing more than a half-hearted nod to other languages' encapsulation
+practices. Make everything public, we say; since everything's
+ultimately public anyway, using the private keyword is merely a
+speedbump which adds no security but does add hassle and headache.
 
 I am becoming more and more aware of a number of rubyists who consider
 the use of private and protected methods in ruby to be a useful way to
@@ -105,23 +107,42 @@ maintainers of the code, meaning that a maintainer will understand the
 intent of the privacy, and be less likely to *accidentally* create an
 external dependency on on a method that should have been kept private.
 
-I am becoming more and more swayed by this second way of thinking, but
-I find that it falls short in one key area: accessors. It is easy to
-create a private method in ruby, but creating a private accessor
-method is actually a bit tortuous. As a result, I see programmers who
-strongly believe in using privacy to communicate undependable
-interfaces frequently making use of either instance variables or
-public accessors for their private variables. These variables are not
-dependable, at least from a "stable interface" standpoint, so both
-solutions offer an unfavorable tradeoff. While instance variables
-communicate privacy, they force the object to depend on its own
-undependable internal interface. Meanwhile, public accessors allow the
-class to isolate itself from its undependable interface, but by making
-it public the communication to the maintainer is that other classes
-can and should depend on that undependable interface.
-
-The reason programmers make this tradeoff is that there doesn't seem
-to be an easy, clean, *elegant* way to create private and protected
-accessors in ruby. My goal with this gem, then, is to create such a
-way, so that those who wish to communicate "this variable is
-undependable and it should be kept isolated for now" can do so easily.
+Another way of looking at this difference of opinion is that the old
+way of thinking is that `private` is there to protect my code from
+your prying eyes, which implies that I think I am smarter than every
+programmer ever, even all the ones who come from the future. It also
+means, at least in ruby, that I think hiding stuff inside a wet paper
+bag is a pretty good way of securing such code from you future
+programmers. This new way of thinking admits to the wet paper bag, but
+more importantly it reverses the direction of the protection: it is
+only a speedbump, but it is there to protect YOU, a smart future
+programmer, from code that I, a programmer from the past who knows he
+will never be as dumb as he is right now, wrote and got working but
+it's volatile and dangerous to depend upon. You may figure out a way
+to use that code safely, and if you do, then by all means cut through
+that paper bag.
+
+I have become swayed by this second way of thinking, but I find that
+it falls short in one key area: accessors. It is easy to create a
+private method in ruby, but creating a private accessor method is
+actually a bit tortuous. As a result, I see programmers who strongly
+believe in using privacy to communicate undependable interfaces
+frequently making one of two bad tradeoffs: they either use instance
+variables or public accessors for their private variables. These
+variables are not dependable, at least from a "stable interface"
+standpoint, so both solutions are suboptimal. While instance variables
+communicate privacy, they force the class to depend on its own
+undependable internals. Making an accessor allows the class to create
+an internal interface to isolates itself from its own undependable
+internals, but by making it public the communication to the maintainer
+is that other classes can and should depend on that interface.
+
+What is needed is a clean, easy, *elegant* way to create private and
+protected accessors, so that classes can create internal interfaces
+to their instance variables, reducing their exposure to their own
+volatility WITHOUT communicating that interface publically.
+
+We need a clean and easy way to create private and protected accessors
+in ruby. My goal with this gem, then, is to create such a way, so that
+those who wish to communicate "this variable is undependable and it
+should be kept isolated for now" can do so easily.

data/lib/scoped_attr_accessor/version.rb

@@ -1,3 +1,3 @@
 module ScopedAttrAccessor
-  VERSION = "1.0.1"
+  VERSION = "1.0.2"
 end

data/lib/scoped_attr_accessor.rb

@@ -25,22 +25,22 @@ module ScopedAttrAccessor
   end
 
   def private_attr_accessor(*names)
-    attr_accessor(*names)
-    names.each {|name| private name; private "#{name}=" }
+    private_attr_reader(*names)
+    private_attr_writer(*names)
   end
 
   def protected_attr_reader(*names)
-    protected
     attr_reader(*names)
+    names.each {|name| protected name}
   end
 
   def protected_attr_writer(*names)
-    protected
     attr_writer(*names)
+    names.each {|name| protected "#{name}=" }
   end
 
   def protected_attr_accessor(*names)
-    protected
-    attr_accessor(*names)
+    protected_attr_reader(*names)
+    protected_attr_writer(*names)
   end
 end

data/scoped_attr_accessor.gemspec

@@ -20,6 +20,6 @@ Gem::Specification.new do |spec|
 
   spec.add_development_dependency "bundler", "~> 1.3"
   spec.add_development_dependency "debugger", "~> 1.5"
-  spec.add_development_dependency "rake"
+  spec.add_development_dependency "rake", "~> 10.0"
   spec.add_development_dependency "minitest", "~> 4.0"
 end

data/test/scoped_attr_accessor_test_module.rb

@@ -120,19 +120,30 @@ module ScopedAttrAccessorTests
   # Happy path test 1. If priv_read1-3 are private, they should be
   # inaccessible
   def test_private_readers_are_in_fact_private
-    lambda { @foo.priv_read1 }.must_raise NoMethodError
-    lambda { @foo.priv_read2 }.must_raise NoMethodError
-    lambda { @foo.priv_read3 }.must_raise NoMethodError
+    -> { @foo.priv_read1 }.must_raise NoMethodError
+    -> { @foo.priv_read2 }.must_raise NoMethodError
+    -> { @foo.priv_read3 }.must_raise NoMethodError
+    -> { @bar.priv_read1 }.must_raise NoMethodError
+    -> { @bar.priv_read2 }.must_raise NoMethodError
+    -> { @bar.priv_read3 }.must_raise NoMethodError
   end
 
   def test_private_writers_are_in_fact_private
-    lambda { @foo.priv_write1 = "OH NOES" }.must_raise NoMethodError
-    lambda { @foo.priv_write2 = "OH NOES" }.must_raise NoMethodError
+    -> { @foo.priv_write1 = "OH NOES" }.must_raise NoMethodError
+    -> { @foo.priv_write2 = "OH NOES" }.must_raise NoMethodError
+    -> { @bar.priv_write1 = "OH NOES" }.must_raise NoMethodError
+    -> { @bar.priv_write2 = "OH NOES" }.must_raise NoMethodError
   end
 
   def test_private_accessors_are_in_fact_private
-    lambda { @foo.priv_access1 = "OH NOES" }.must_raise NoMethodError
-    lambda { @foo.priv_access2 = "OH NOES" }.must_raise NoMethodError
+    -> { @foo.priv_access1 = "OH NOES" }.must_raise NoMethodError
+    -> { @foo.priv_access2 = "OH NOES" }.must_raise NoMethodError
+    -> { @foo.priv_access1 }.must_raise NoMethodError
+    -> { @foo.priv_access2 }.must_raise NoMethodError
+    -> { @bar.priv_access1 = "OH NOES" }.must_raise NoMethodError
+    -> { @bar.priv_access2 = "OH NOES" }.must_raise NoMethodError
+    -> { @bar.priv_access1 }.must_raise NoMethodError
+    -> { @bar.priv_access2 }.must_raise NoMethodError
   end
 
   # Happy path test 2. priv_read1 and priv_read2 may be inaccessible, but are they
@@ -160,9 +171,9 @@ module ScopedAttrAccessorTests
   # Happy path test 3. If prot_read1-3 are protected, they should be
   # inaccessible
   def test_protected_readers_are_in_fact_private
-    lambda { @foo.prot_read1 }.must_raise NoMethodError
-    lambda { @foo.prot_read2 }.must_raise NoMethodError
-    lambda { @foo.prot_read3 }.must_raise NoMethodError
+    -> { @foo.prot_read1 }.must_raise NoMethodError
+    -> { @foo.prot_read2 }.must_raise NoMethodError
+    -> { @foo.prot_read3 }.must_raise NoMethodError
   end
 
   # Happy path test 4. prot_read1 and prot_read2 may be inaccessible, but are they
@@ -188,17 +199,19 @@ module ScopedAttrAccessorTests
   # private scope, after we created protected reader 3, did
   # attr_accessor priv_read3 still get created privately?
   def test_private_readers_AFTER_protected_accessors_are_STILL_private
-    lambda { @foo.peek_at_priv_read3_via_protected_access_BAD }.must_raise NoMethodError
+    -> { @foo.peek_at_priv_read3_via_protected_access_BAD }.must_raise NoMethodError
   end
 
   def test_protected_writers_are_in_fact_protected
-    lambda { @bar.prot_write1 = "OH NOES" }.must_raise NoMethodError
-    lambda { @bar.prot_write2 = "OH NOES" }.must_raise NoMethodError
+    -> { @bar.prot_write1 = "OH NOES" }.must_raise NoMethodError
+    -> { @bar.prot_write2 = "OH NOES" }.must_raise NoMethodError
   end
 
   def test_protected_accessors_are_in_fact_protected
-    lambda { @bar.prot_access1 = "OH NOES" }.must_raise NoMethodError
-    lambda { @bar.prot_access2 = "OH NOES" }.must_raise NoMethodError
+    -> { @bar.prot_access1 }.must_raise NoMethodError
+    -> { @bar.prot_access2 }.must_raise NoMethodError
+    -> { @bar.prot_access1 = "OH NOES" }.must_raise NoMethodError
+    -> { @bar.prot_access2 = "OH NOES" }.must_raise NoMethodError
   end
 
   def test_protected_writers_do_in_fact_work_as_writers

metadata

@@ -1,20 +1,18 @@
 --- !ruby/object:Gem::Specification
 name: scoped_attr_accessor
 version: !ruby/object:Gem::Version
-  version: 1.0.1
-  prerelease: 
+  version: 1.0.2
 platform: ruby
 authors:
 - David Brady
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-04-29 00:00:00.000000000 Z
+date: 2013-05-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -22,7 +20,6 @@ dependencies:
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -30,7 +27,6 @@ dependencies:
 - !ruby/object:Gem::Dependency
   name: debugger
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -38,7 +34,6 @@ dependencies:
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -46,23 +41,20 @@ dependencies:
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - ~>
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '10.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
-    - - ! '>='
+    - - ~>
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '10.0'
 - !ruby/object:Gem::Dependency
   name: minitest
   requirement: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -70,7 +62,6 @@ dependencies:
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
-    none: false
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
@@ -99,33 +90,26 @@ files:
 homepage: https://github.com/dbrady/scoped_attr_accessor.git
 licenses:
 - MIT
+metadata: {}
 post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
-      segments:
-      - 0
-      hash: -2597970377507506024
 required_rubygems_version: !ruby/object:Gem::Requirement
-  none: false
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
-      segments:
-      - 0
-      hash: -2597970377507506024
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.25
+rubygems_version: 2.0.0.rc.2
 signing_key: 
-specification_version: 3
+specification_version: 4
 summary: Adds private_* and protected_* attr_reader, attr_writer, and attr_accessor
 test_files:
 - test/lib/test_scoped_attr_accessor.rb