XCode and Codewarrior are completely different environments, and
Codewarrior long predates XCode. Moving to XCode from Codewarrior is no
small matter, and there was never any reason to do it. Codewarrior had
always been a stalwart and reliable tool. It was always the most
professional tool available for the Mac platform, I think going all the
way back to the 1980s.
There are many things to berate MM for, but staying with Codewarrior is
not one. Apple is totally to blame here for a choosing a direction that
they publicly and vehemently denied right up until practically the day
before they announced it. In doing so, they left Codewarrior (and all
its legions of users) high and dry. (My understanding is that
Codewarrior had sold off its Intel compiler a few months before Apple
made its move.) I for one will almost be delighted if MM does drop
support for Macs. Apple would utterly deserve it.
As bad as the compiler issue (which is far bigger than any non
C-programmer probably realizes) is the issue of integer endian-ness.
It's a highly technical problem, but one that will throw a wrench into
any complicated program like Finale no matter what compiler it's on.
While I use Codewarrior to create both Apple and Win plugins, I believe
MM uses CW for Mac and Microsoft VC++ for Win.
--
Robert Patterson
http://RobertGPatterson.com
_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale
