I agree. Anyway, I can't use some APIs from QuickTime.
Do you know any replacement for 64-bit Intel + 10.6 only?
MoviesTask
SetMovieDrawingCompleteProc
SetMovieGWorld
UnlockPixels
--
Leo
> Da: Sean McBride <[email protected]>
> Organizzazione: Rogue Research Inc.
> Data: Tue, 15 Dec 2009 14:22:41 -0500
> A: Jean-Daniel Dupas <[email protected]>, "gMail.com"
> <[email protected]>
> Cc: <[email protected]>
> Oggetto: Re: memcpy with 64 bit
>
> On 12/15/09 11:46 AM, Jean-Daniel Dupas said:
>
>> «Mac OS X implements a highly-tuned, threadsafe allocation library,
>> providing standard implementations of the malloc,calloc, realloc, and
>> free routines, among others. If you are allocating memory using older
>> routines such as NewPtr or NewHandle, you should change your code to use
>> malloc instead. The end result is the same since most legacy routines
>> are now wrappers for malloc anyway.»
>>
>> from http://developer.apple.com/mac/library/documentation/Performance/
>> Conceptual/ManagingMemory/Articles/MemoryAlloc.html
>
> I would think one place that using NewHandle() is still the best idea is
> when an API requires a handle. This is the case for many QuickTime
> APIs, and the OP did mention using QuickTime. Another would be the
> Alias Manager.
>
> --
> ____________________________________________________________
> Sean McBride, B. Eng [email protected]
> Rogue Research www.rogue-research.com
> Mac Software Developer Montréal, Québec, Canada
>
>
_______________________________________________
Cocoa-dev mailing list ([email protected])
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
