3 ms·
You can do this. I tried to draw up a quick gist, but I am late, and I've been writing too much Rust... The basic idea is this: module Mst def self.incl
by steveklabnik 11y ago
You can do this. I tried to draw up a quick gist, but I am late, and I've been writing too much Rust...
The basic idea is this:
module Mst
def self.included(base)
# define a method on base using define_method named :before, which takes an
# argument and a block
# in that method, you grab the method with that name, using .method()
# you then define a new method, named method, which calls the block and
# then calls the original method
end
end
class Foo
include Mst
def test
puts "test"
end
before :test do
puts "before"
end
end
Module named after you. You can see how the logic only changes a bit for after and around. You could then wrap this up as a library, and all you'd need to do is the include.
http://api.rubyonrails.org/classes/ActiveSupport/Callbacks/Filters.html http://api.rubyonrails.org/classes/ActiveSupport/Callbacks/F... has an example, I think.
- mst 11y agoThat's really cute. I hope, however, that you can understand from the POV of somebody who keeps being driven off ruby by ruby being too much work, that "you could make it less work by first porting all the perl5 libraries that make perl5 OO more pleasant" isn't really a convincing solution :)
- steveklabnik 11y agoOne of my Twitter followers posted a gist: https://gist.github.com/paulodiniz/39698ac1fe5f62e3180e https://gist.github.com/paulodiniz/39698ac1fe5f62e3180e Sure, I was just addressing the "I don't know how to do that." Rails offer this for models in certain circumstances, for example.
- mst 11y agoThat's very cute. Yeah, I was responding to a post that claimed it was trivial; that's cute but not trivial - although it does demonstrate that using 'alias' to rename isn't necessary, which is nice to know. I can absolutely see how I'd turn this into a full Class::Method::Modifiers re-implementation, so I'll totally stipulate to 'trivial if' :D
- steveklabnik 11y agoI'm not interested in being condescended to, so
- Mithaldu 11y agomst might speak for himself at another time, but i have a personal reason to post, so i will say this: Please do not take this conversation as an affront and throw away what has so far come of it. It has shown you, and Ruby at large, an API that has been proven to be good and useful, and the Ruby community has come up with a way to implement it in a generalized way. I hope to someday be able to learn Ruby and use its OO with similar ease and pleasure as i can use the OO system in Perl 5. So please, do not throw this away. It is a valuable chance to do the same thing Perl has done so many times: Recognize something useful and make it your own.
- mst 11y agoSteve and I had a previous similar conversation; this one got further subject wise, but the original was also a fair few posts deep and we didn't accidentally piss each other off that time. Pretty sure we'll manage to resolve the confusion shortly.
- mst 11y agoWut? I just complimented the code you posted, and changed my mind from "the unconstructive guy upthread said trivial, which it isn't, but steve's been kind enough to give me enough information to see it's trivial if I write a port of CMM, and said port is basically identical rather than requiring the crappy alias approach". I've genuinely no idea why you think I was being condescending.
- kbenson 11y agoI don't know where steveklabnik hails from, but in the US "cute" is sometimes meant with a condescending overtone. I seem to recall you are from the UK (Scotland?) from the last YAPC I was at, so I suspect this is a dialect difference causing a misunderstanding.
- wycats 11y agoFor what it's worth, the `prepend` API in Ruby, which I advocated for back when I was working on Rails, works pretty nicely: https://gist.github.com/wycats/0a354a96d00d47fa4e04 https://gist.github.com/wycats/0a354a96d00d47fa4e04
- mst 11y agoOh, that's even better. Is there an around/after equivalent or are those still best implemented with Steve's thing?
- dragonwriter 11y ago"before", "after", and "around" method modifiers are pretty common in Ruby Aspect-Oriented Programming libraries (AOP has pretty much fallen out of favor for Ruby, but I'm pretty sure at least some of these are still maintained.)