Xml & Svg : namespace conflict

[hhugo]

Xml & Svg can easily collide with other libraries.
It would be better to have them packed.

[Drup]

Agreed, and same for Html5 and all the _f, _sigs and _types (all of them are exported, yes ...) which I find is a poor design choice to export for other to use (it's perfectly fine as internal stuff).

First thing would be to pack everything inside a Tyxml module, but I think we could make the whole thing a bit nicer.

[kit-ty-kate]

The problem with packing is that it cause bad performances, in particular, it grow the weight of the resulting binary.

Note that the problem should be solved in ocaml 4.02.

[hnrgrgr]

Hi Drup,

I do not always appreciate your delicate free speech.

Agreed, and same for Html5 and all the _f, _sigs and _types (all of
them are exported, yes ...) which I find is a poor design choice to
export for other to use (it's perfectly fine as internal stuff).

The functorial interface is required for Eliom and we have to export
all those _f things (or those f* things as it appears you would like
to say). The 'META' file was designed in order to hide the functors:
the default 'tyxml' package does not contain them, only the
'tyxml.functor' does.

That said, back to the initial request, I agree the name conflict
should be avoided. Either by packing or by prefixing the file name.

[Drup]

Ok, my vote goes for the pack, as it's the simpler for users. Do we pack the tyxml_f library too ?

[Drup]

So either we pack everything into a Tyxml module (and a Tyxml_f module for the tyxml_f library), or we prefix everything by "Ty" (TyXml, TySvg, TyHtml5). I find the second prettier. The first may involve slightly less changes (not sure). It would only affect people using tyxml directly anyway (eliom and js_of_ocaml users wouldn't be affected).

@balat, do you prefer an option ? If you don't, I'm going to go for the prefix one.

[sagotch]

While waiting for a fix, is there any workaround for using another lib with a xml module?

ocsigenserver: ocsigen:main: Fatal - While loading /[...]/.opam/4.02.3/lib/xml-light/xml-light.cma: interface mismatch on Xml

(Few minutes later, I am not sure anymore it is a tyxml related issue or a ocsigenserver related one...)

[Drup]

Fixed in master.