Re: [Caml-list] Smells like duck-typing

[Alain Frisch <alain@frisch.fr>]

Dario Teixeira wrote:
>> To me your problems looks like a good candidate for XML-modelling and 
>> reusing all the tools for working in XML. The more so because XML was 
>> made... exactly for that! Why don't  you give it at least a somewhat 
>> serious thought?
> 
> Hi,
> 
> You mean like CDuce and/or OCamlduce?

I'm not particularly encouraging the use of OCamlduce here, but FWIW, a 
solution would look like:

type title = {{ { title=Latin1 ..} }}
type intro = {{ { intro=Latin1 ..} }}
type blurb_t = {{ { id=Int .. } ++ title ++ intro }}
type fresh_t = {{ { body=Latin1 .. } ++ title ++ intro }}
type full_t = {{ blurb_t & fresh_t }}   (* intersection type *)

let print_metadata s =
   Printf.printf "%d: %s\n" {:s.id:} {:s.title:}

If you're ok duplicating fields, the type definitions can be simplified:

type blurb_t = {{ {id=Int title=Latin1 intro=Latin1 ..} }}
type fresh_t = {{ {body=Latin1 title=Latin1 intro=Latin1 ..} }}
type full_t = {{ {id=Int body=Latin1 title=Latin1 intro=Latin1 ..} }}


-- Alain