Re: [xslt] Re: libxslt effects on _private member of libxml structures

So my dirty little secret is that another reason I want to keep the void 
*_private first is that you can use it as an isa pointer for Objective 
C, and then treat all the libxml data structures like Objective C 
objects.  :)

Luca Padovani wrote:

>On Wed, 2003-03-26 at 10:39, Sean McGuire wrote:
>>comments currently state it is, and add another field for holding the 
>>key() value for libxslt.
>I fear this would break binary compatibility, and would make every node
>slightly larger (aren't they too large already?)
If I understand the alternate suggestion, doesn't it also risk breaking 
binary compatibility and making every node slightly larger?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]