Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
Ruby
Method wrapping
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
Reply to thread
Message
[QUOTE="Jim Weirich, post: 4420493"] The distinction between *what* and *kind* alludes me for the moment. However, I would tend to suspect that a wrapper depends upon the primary method in the same way client software depends upon the methods it calls. In other words, they depend upon the arguments, return value and semantics (as defined by a DbC style contract), but not upon actual implementation. I would suspect that most method replacements would honor the same argument lists, return types and basic semantics. Otherwise replacing a method would cause *everyone* who calls that method to be modified, not just the wrapper methods. [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
Ruby
Method wrapping
Top