4e2f174667
Added test for good measure to ensure class instances do not share protected member values
2011-03-07 00:19:56 -05:00
e05a65d5fa
Initial concept of inheriting protected/private members
2011-03-07 00:14:43 -05:00
30bfde50cd
Tada! Private members.
2011-03-06 23:03:39 -05:00
c1765cd720
Using visibility fallback for browsers that do not support getters/setters
2011-03-06 22:43:14 -05:00
bc9e2bb7b2
Fix setting public properties
...
- This currently only works with ES5 engines
- Fallback to follow so this will work with pre-ES5 engines
- As such, I do not recommend using this commit outside of ES5-compliant engines that work properly with getters/setters
- This does NOT include IE8, as IE8 only works with getters/setters on DOM elements
2011-03-02 23:21:10 -05:00
74c2fc57c1
Initial implementation of protected members
...
- This was quite the pain in the ass
- There are additional considerations. I DO NOT recommend using this commit. Check out a later commit.
2011-03-02 20:43:24 -05:00
02d0c07f98
Extended existing visibility tests to include methods
2011-01-27 22:39:52 -05:00
38c16048cb
Began adding protected/private member support
...
- No longer adding ANY properties to prototype
- protected/private members no longer part of the public access level
2011-01-27 22:35:40 -05:00
Mike Gerwitz