title: Is there a less repetitive way to forward action messages to another object?
body: <p>I'm making a calculator app to learn Objective-C and maybe improve my OO design skills a bit. In an attempt to do things more MVClike, i have separated the actual do-the-calculator-stuff code from the view controller.  For every action, pretty much all the view controller does is tell the "model" to do the operation meant for that action.</p>
  
  <p>Thing is, that gives me a bunch of methods that do basically nothing but forward the action to the model, like this:</p>
  
  <pre><code>- (IBAction)clearAll:(id)sender {
      [self.model clearAll];
  }
  
  - (IBAction)clearDisplay:(id)sender {
      [self.model clearDisplay];
  }
  
  - (IBAction)clearMemory:(id)sender {
      [self.model clearMemory];
  }
  
  - (IBAction)storeMemory:(id)sender {
      [self.model storeMemory];
  }
  
  - (IBAction)addMemory:(id)sender {
      [self.model addMemory];
  }
  
  - (IBAction) subtractMemory:(id)sender {
      [self.model subtractFromMemory];
  }
  
  - (IBAction)recallMemory:(id)sender {
      [self.model recallMemory];
  }
  </code></pre>
  
  <p>Objective-C so far seems outrageously flexible with dynamically forwarding messages, and these methods are alike enough to look rather easily automated away.  Do they really have to be there?  Or is there a less repetitive way to tell the controller to just pass certain messages through to the model (ideally, while stripping off the <code>sender</code> arg)?</p>
  
  <p>I've been looking a bit and trying some stuff with selectors and <code>NSInvocation</code>, but it seems like that'd mess with Interface Builder by taking away all the <code>(IBAction)</code> markers that let me hook up buttons to actions.  (I'd prefer if the view didn't have to know or care that the controller's just forwarding to the model in these cases.)</p>
  
  <p>So, is there a less repetitive and/or hacky way?  Or is it not worth the trouble?  (Or is it a bad idea in the first place?  Or is this trying to make the model do too much? Or...)</p>