Jan Steinman wrote:
> I am an Apple
> developer. I get a bi-monthly CD-ROM in the mail full of stuff like,
> "This function is deprecated, and will quit working in the next major
> release." Or even, "If you have to do 'A', do it this way, because
> doing it the 'B' way is unsupported, and may stop working in the
> future."
The problem is that a lot of the time, they just say "don't do X any
more", but they don't provide a new way to do things. QDGetCursorData,
for instance, is QuickDraw era, has been deprecated for heaven knows how
long, but _there's nothing else that does that_, so we're stuck using
it. (and no, it's not exactly what you'd call "documented"..)
That said, when I reported a bug in it for Tiger, they not only said
they'd fix it, they offered to FedEx a Mac system to me to verify that
it was working with the particular internal build they were using at the
time, so I can't complain about the levels of developer support.
-- dan
==============================================
List usage info: http://www.zuikoholic.com
List nannies: olympusadmin@xxxxxxxxxx
==============================================
|