title: Keeping legacy Carbon code alive
body: <p>Apple has killed Carbon for 64 bit applications.  I've got a pile of legacy code that targets carbon UI widgets that I'd like to keep alive for a while.   Most of it is in the form of plugins and bundles that will have to go 64-bit in sync with their host platform.</p>
  
  <p>The choice that Apple seems to be assuming is to throw all the legacy code away
  and rewrite using Cocoa.  It's not going to happen in the short run, if only because 
  the same legacy code is tied to a PC binding as well.</p>
  
  <p>I'm considering 3 Options</p>
  
  <p>(1) Dive into cocoa, create a compatibility package that supports the small subset
  of carbon that I actually need.</p>
  
  <p>(2) use Cocoatron as the new target.  In the short run bridge carbon-to-cocotron, and maybe in the longer run convert to cocoatron native for both mac and pc.  (ref: <a href="http://cocotron.org/" rel="nofollow">http://cocotron.org/</a>)</p>
  
  <p>(3) use QT as the new target. See option (2). (ref: <a href="http://qt.nokia.com/" rel="nofollow">http://qt.nokia.com/</a>)</p>
  
  <p>What I would really prefer is a fourth option, such as a bootleg copy of the 64 bit
  Carbon beta that Apple killed, or a compatibility package explicitly intended just
  to emulate carbon.</p>