Re: CFProxySupportTool sample and CFNetworkCopyProxiesForAutoConfigurationScript API change?
Re: CFProxySupportTool sample and CFNetworkCopyProxiesForAutoConfigurationScript API change?
- Subject: Re: CFProxySupportTool sample and CFNetworkCopyProxiesForAutoConfigurationScript API change?
- From: Quinn <email@hidden>
- Date: Tue, 29 Jul 2008 12:41:16 +0100
At 18:11 -0400 17/7/08, Alfred J. Eisenberg wrote:
I'm a bit new to Mac development, so please bear with me for my questions.
I'm using the XCODE 3.1 environment and I downloaded the
CFProxySupportTool sample from the API documentation.
It seems that the Mac OS X 10.5 SDK that ships with Xcode 3.1 has a
bug <rdar://problem/6108728> in the prototype for
CFNetworkCopyProxiesForAutoConfigurationScript (that is, the extra
parameter you're seeing). The CFProxySupportTool sample was
originally built with Xcode 3.0, which has a Mac OS X 10.5 SDK
without this bug. This bug explains why the sample, which built and
ran just fine when I released it, now won't compile.
I'm still trying to determine the extent of the problems with the
Xcode 3.1 Mac OS X 10.5 SDK. It could be just this one routine, or
it could be more widespread. I'll post more info once I have more
time to investigate this.
In the meantime, you should be able to work around this specific
problem by passing CFNetworkCopyProxiesForAutoConfigurationScript to
the error parameter. The Mac OS X 10.5 implementation of
CFNetworkCopyProxiesForAutoConfigurationScript will just ignore that
extra parameter.
I apologise for confusion that this bug has caused.
S+E
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden