Re: [Caml-list] [ANN] Lambda Soup - HTML scraping and rewriting with CSS selectors

["François Bobot" <francois.bobot@cea.fr>]

On 22/11/2015 08:58, Anton Bachin wrote:
>> Does the types are as powerful as the one in tyxml? Is it possible to have
>> this kind of selectors on top of tyxml?
>
> The types are not as powerful as the ones in tyxml, in the sense of being
> precise. Lambda Soup only distinguishes between "definitely elements",
> "definitely documents", and "anything, including an element, or document, or any
> other node". It doesn't know about element types or any constraints on their
> composition.
>
> It does, however, seem to be possible to have the selectors on top of tyxml. I
> am not very familiar with tyxml, but I do see types Xml.elt and Xml.econtent,
> and value content. It may be possible to either use those directly as the
> internal DOM representation of Lambda Soup, and build traversals over them, and
> it is almost certainly possible to convert them to Lambda Soup's current
> internal representation, the same way Lambda Soup currently converts Nethtml’s
> parse trees.

Nice to know.

> If there is interest in this, perhaps with some study Lambda Soup can be
> modified to use tyxml – perhaps functorized.

It is just for not creating another xml type and simpler composition of ocaml libraries.

The functor solution used by cohttp (for allowing lwt or async) for example is a nice one, and 
flambda should eliminate most of the cost of it (on a side note, does @inline work for functor 
application?)

However in this case since the differences is about typing and not just the implementation, I'm not 
sure you can define a generic functor that could be applied with instance (NetHttp, tyxml, yours) 
that restricts differently the function applications.

-- 
François