In article <uce-6D5AE7.07581914062007@[EMAIL PROTECTED]
>,
Gregory Weston <uce@[EMAIL PROTECTED]
> wrote:
> In article <these3rt0only-7554ED.13013214062007@[EMAIL PROTECTED]
>,
> Roelf Toxopeus <these3rt0only@[EMAIL PROTECTED]
> wrote:
>
> > Are they moving Carbon out?
>
> If they are it's going to take years just to deprecate, let alone
> eliminate. There's a lot of stuff you simply can't do in straight Cocoa
> today. And a lot more that's either horribly inefficient, or horribly
> convoluted to make efficient.
>
> > http://www.apple.com/macosx/leopard/technology/64bit.html
> > http://lists.apple.com/archives/carbon-dev/2007/Jun/msg00260.html
>
> I would note that:
> 1) Some parts of Carbon already deal with 64-bit values.
> 2) The comment is about Carbon specifically. There's no indication that
> there will be no 64-bit procedural code. I think the thing to question
> is what parts of the Carbon API as it exists today would benefit from
> "64-bitness" - what that would actually mean to them.
>
> > I had an inclination about this already looking at the new Quicktime,
> > Core 'this and that' frameworks, which are written in Obj-C and thus
> > Cocoa. Some have an interface, so you can access them from outside
> > Cocoa, others not. You'll have to use Quicktime (sic).
> > Also Core Audio has new functions and warnings things will be
deprecated.
> > The current Carbon API references are loaded with deprecate warnings.
>
> That's because the current Carbon API has a lot of legacy and
> (im****tantly) redundant cruft.
>
> I wouldn't read too much into this quite yet.
The 'yet' is of course the crux here.
http://lists.apple.com/archives/carbon-dev/2007/Jun/thrd3.html
follow the '64-bit Carbon' and 'Is Carbon Viable?' threads
Some interesting and 'familiar feeling' issues are discussed here.
Also the 64-bitness now or later of certain Carbon parts are explained.
I can certainly sympathize with those developers who were told last WWDC
they would get 64-bit Carbon and based their strategy on that. It's all
to the dogs: time, energy, money (including attending that last WWDC).
Even if it's only delayed, it may be too late for some: customers
affected by the 64b-bit buzzword want it now.
It looks to me all unnecessary created grief.
Anyway it's very difficult to speculate, who knows what's happening?
Again I would suggest to be prepared with any new big development
wrt a Forth system: let it be GUI independent, let possible changes not
bite too hard.
|
