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

[Anton Bachin <antonbachin@yahoo.com>]

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

That’s a worthwhile goal. I certainly intend to look into it. I want
there to be some “canonical” set of libraries that work together nicely.

> 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?)

Since you just made me aware of the existence of @inline (thank you),
I’m going to have to hope someone else answers the side note
question :) I would have to gain some experience with it first in
normal usage.

> 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.

Let me make sure we are focusing on the same issue. I am supposing that
you would like to construct a tree using tyxml’s “richly-typed”
functions, then be able to walk around it using Lambda Soup, and make
edits in the tree using the mutation interface (or some improved
variant of it) or tyxml. However, when making the edits, you would want
the “rich” tyxml types preserved, to benefit from the static constraints
they impose on your code. Is this right?

I think that is the only trouble. Lamdba Soup doesn’t actually expose
any XML type, and I think it can ported or functorized to work with just
about any low-level XML representation.

Regards,
Anton