> It may be the case that on the other side of the routine the system is
> returning a cached object, but you can't depend on that behavior
> because there is no way to tell what might happen in the next version.
You can if it is documented behavior. But I guess I am not going to run into
that problem ;)
> I don't think it's unreasonable for Apple to ask you to make the assumption
> that, unless otherwise documented, any call with create it it's name has the
> possibility of failing.
If this is the assumption we are expected to make then fine. But the
documentation should be consistent. You can't have half the CGCreate functions
documented as possibly failing and returning NULL while other half mention
nothing. Pick one and stick to it.
Matt.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartz-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
