Re: [xml] about xmlReadMemory()

[nicolas bats via xml]

Thank you Nick for your answer, I'll give a try to xmlReadIO.
thanks again.
++

Le mar. 2 mars 2021 à 18:02, Nick Wellnhofer  a écrit :

> On 02/03/2021 16:28, nicolas bats via xml wrote:
> > Hi,
> > is there's a reason why xmlReadMemory
> > () accepts
> int as
> > the size of the array to transform to xmlDocPtr.
> > no doubt there's one...
>
> That's simply a design mistake. The API was created 20 years ago when
> 64-bit
> systems were rare.
>
> > and in that case how could I retrieve a xmlDocPtr from
> > memory where size is type of size_t?
>
> If you want to process memory buffers larger than INT_MAX, you can use
> xmlReadIO with a custom read callback that uses a size_t to store the
> offset.
>
> Nick
>
___
xml mailing list, project page  http://xmlsoft.org/
xml@gnome.org
https://mail.gnome.org/mailman/listinfo/xml

Re: [xml] about xmlReadMemory()

[Nick Wellnhofer via xml]

On 02/03/2021 16:28, nicolas bats via xml wrote:

Hi,
is there's a reason why xmlReadMemory 
() accepts int as 
the size of the array to transform to xmlDocPtr.

no doubt there's one...


That's simply a design mistake. The API was created 20 years ago when 64-bit 
systems were rare.


and in that case how could I retrieve a xmlDocPtr from 
memory where size is type of size_t?


If you want to process memory buffers larger than INT_MAX, you can use 
xmlReadIO with a custom read callback that uses a size_t to store the offset.


Nick
___
xml mailing list, project page  http://xmlsoft.org/
xml@gnome.org
https://mail.gnome.org/mailman/listinfo/xml

[xml] about xmlReadMemory()

[nicolas bats via xml]

Hi,
is there's a reason why xmlReadMemory
() accepts int as
the size of the array to transform to xmlDocPtr.
no doubt there's one... and in that case how could I retrieve a xmlDocPtr
from memory where size is type of size_t?

thank you,
best regards,
nicolas
___
xml mailing list, project page  http://xmlsoft.org/
xml@gnome.org
https://mail.gnome.org/mailman/listinfo/xml