Fix:
  => Alias_method for booleans. I don't like using bool instead of BOOL
  (the obj-c standard):
    The problem happen when an alias_method is created on a method
    receiving a BOOL as parameter, which inside is a char. So when you
    invoke it in RubyMotion it generates an error that such a method
    receiving a char is not precompiled.

    RubyMotion is correct in send a char, but internally something goes
    wrong and fails. It gets fixed if in the bridge support we change
    the BOOL B for a char c, the problem with this solution is that
    everytime the bridgesupport is generated we must patch it.

    The long term solution is to change every BOOL to bool :'(, also its
    needed to test it a lot to ensure this does not break anything.