[iPhone] xml parsing
-
The iPhone docs point you in the direction of libXML2 for parsing XML,
yet the headers for NSXML are included in the SDK headers, and i was
able to build and run fine using NSXMLDoc/element/node. (in fact i
just dropped my existing NSXML based code into a iPhone project and it
worked fine, so it never even occurred to me that this might not be
supported). Would this constitute using a private API ? (is there a
good definition of private API somewhere?)
Tx
Simon -
If you find a function/method/class declaration in a public header (an
header that is not in PrivateHeader folder) you can problably
considere it as public.
Le 10 mars 08 à 23:49, Simon Fell a écrit :
> The iPhone docs point you in the direction of libXML2 for parsing
> XML, yet the headers for NSXML are included in the SDK headers, and
> i was able to build and run fine using NSXMLDoc/element/node. (in
> fact i just dropped my existing NSXML based code into a iPhone
> project and it worked fine, so it never even occurred to me that
> this might not be supported). Would this constitute using a private
> API ? (is there a good definition of private API somewhere?)
>
> Tx
> Simon
>
-
I'm pretty sure you read the SDK release notes ;-)
If not, I think you should, that's always a good idea.
--
Julien
On Mon, Mar 10, 2008 at 11:49 PM, Simon Fell <cocoa...> wrote:
> The iPhone docs point you in the direction of libXML2 for parsing XML,
> yet the headers for NSXML are included in the SDK headers, and i was
> able to build and run fine using NSXMLDoc/element/node. (in fact i
> just dropped my existing NSXML based code into a iPhone project and it
> worked fine, so it never even occurred to me that this might not be
> supported). Would this constitute using a private API ? (is there a
> good definition of private API somewhere?)
>
> Tx
> Simon
>
-
On a similar-ish note, I'm having trouble using libxml. I'm using a
slightly modified version of the appropriate sample code. I need to
make sure that the library is in my project. Since I couldn't find the
library in a convenient place (where are you supposed to get those
anyway?), I just dragged it from the sample project to mine. However,
when I try to build the project, it says it cannot locate <libxml> or
<libxml/tree.h> or whatever I import. I can't find any significant
differences in the projects' properties... does anyone know how to get
this working?
On Mar 10, 2008, at 4:46 PM, <cocoa-dev-request...> wrote:
> If you find a function/method/class declaration in a public header (an
> header that is not in PrivateHeader folder) you can problably
> considere it as public.
>
>
> Le 10 mars 08 à 23:49, Simon Fell a écrit :
>
>> The iPhone docs point you in the direction of libXML2 for parsing
>> XML, yet the headers for NSXML are included in the SDK headers, and
>> i was able to build and run fine using NSXMLDoc/element/node. (in
>> fact i just dropped my existing NSXML based code into a iPhone
>> project and it worked fine, so it never even occurred to me that
>> this might not be supported). Would this constitute using a private
>> API ? (is there a good definition of private API somewhere?)
>>
>> Tx
>> Simon
>>
>>
-
I can't comment on the iPhone part as this is NDA (and should not be
discussed here) but, on Mac OS X, I'd add /usr/include/libxml2 to the header
search path in project (or target) build settings.
Also, I'd add the libxml2.dylib to my project using "Add existing framework"
or add -lxml2 to the "additional linker flags" of project (or target) build
settings.
Of course, this only describes what I'd do for a Mac OS X project in Xcode.
--
Julien
On Tue, Mar 11, 2008 at 1:33 AM, Jacob Bandes-Storch <jtbandes...>
wrote:
> On a similar-ish note, I'm having trouble using libxml. I'm using a
> slightly modified version of the appropriate sample code. I need to
> make sure that the library is in my project. Since I couldn't find the
> library in a convenient place (where are you supposed to get those
> anyway?), I just dragged it from the sample project to mine. However,
> when I try to build the project, it says it cannot locate <libxml> or
> <libxml/tree.h> or whatever I import. I can't find any significant
> differences in the projects' properties... does anyone know how to get
> this working?
>
> On Mar 10, 2008, at 4:46 PM, <cocoa-dev-request...> wrote:
>
>> If you find a function/method/class declaration in a public header (an
>> header that is not in PrivateHeader folder) you can problably
>> considere it as public.
>>
>>
>> Le 10 mars 08 à 23:49, Simon Fell a écrit :
>>
>>> The iPhone docs point you in the direction of libXML2 for parsing
>>> XML, yet the headers for NSXML are included in the SDK headers, and
>>> i was able to build and run fine using NSXMLDoc/element/node. (in
>>> fact i just dropped my existing NSXML based code into a iPhone
>>> project and it worked fine, so it never even occurred to me that
>>> this might not be supported). Would this constitute using a private
>>> API ? (is there a good definition of private API somewhere?)
>>>
>>> Tx
>>> Simon
>>>
>>>
>
