title: Naming issue with AngularJS controllers
body: <p>I just started playing around with <code>AngularJS</code>. I did however stumble upon a case that had me quite puzzled, when trying to use the <a href="http://angular-ui.github.io/bootstrap/" rel="nofollow">angular bootstrap directives</a> for creating tabbed panes. I followed <a href="http://plnkr.co/edit/PCkokTwUEblmrREKzcvI" rel="nofollow">this example</a>, and the only thing I changed was renaming the <code>TabsCtrl</code> variable to <code>TabsController</code>, because I had been using *Controller convention in the rest of my application.</p>
  
  <p>What I found really strange is that this renaming broke the entire thing! The <code>TabsController</code> function was never executed after the renaming. You can test it yourself on the <a href="http://plnkr.co/edit/PCkokTwUEblmrREKzcvI" rel="nofollow">plunker link</a>.</p>
  
  <p>I need to get this straight, as it seems scary that renaming an object like this would make it break without me knowing why. Is the *Controller variable name reserved somehow? How come I have been able to use the *Controller naming convention for the rest of my controllers without problems?</p>
  
  <p>Edit: It seems that it is the exact word <code>TabsController</code> that is causing the issue. I tried naming it BajsController instead, and that worked..</p>