However theres another funny work around for this problem
as your desired syntax is
after_destroy :update_something, true
Just tweak little bit:
after_destroy "update_something(true)"
declare the update_something method privately like:
def update_something(param = value)
#operations based on #{param}
end
I dont know your actual scenario. But i think
* If u need to perform same action on :after_save and :after_destroy
call-back then why do you need parameter
* Secondly, if update_something performs differently based on the
parameter then why don't you create two separate methods
Anyway looking for the real picture from you and hope to get the best
architectural suggestion from anyone for this kind of problem