From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=AWL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by yquem.inria.fr (Postfix) with ESMTP id 3F916BBC1 for ; Fri, 28 Mar 2008 12:53:49 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkUBADd57EfVpUAUlGdsb2JhbACRMwEBAQEJBQkHFJlD X-IronPort-AV: E=Sophos;i="4.25,569,1199660400"; d="scan'208";a="10095711" Received: from mail.gmx.net ([213.165.64.20]) by mail1-smtp-roc.national.inria.fr with SMTP; 28 Mar 2008 12:53:48 +0100 Received: (qmail invoked by alias); 28 Mar 2008 11:53:48 -0000 Received: from p57B1E6D8.dip.t-dialin.net (EHLO pc21b.local) [87.177.230.216] by mail.gmx.net (mp038) with SMTP; 28 Mar 2008 12:53:48 +0100 X-Authenticated: #20477425 X-Provags-ID: V01U2FsdGVkX19fgBIcm7lfBHS6xOS8YvLSXHJMRiBMw7jhuJ5wSi IKlFgIIHE/GRt3 From: Michael Wohlwend To: "Jim Farrand" Subject: Re: [Caml-list] The Bridge Pattern in OCaml Date: Fri, 28 Mar 2008 12:52:41 +0100 User-Agent: KMail/1.9.7 References: <4a051d930803190929q60d31012kb6c9d2b03a2d2ca6@mail.gmail.com> <1206703811.47ecd6c379853@webmail.in-berlin.de> In-Reply-To: Cc: caml-list@yquem.inria.fr MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200803281252.41824.micha-1@fantasymail.de> X-Y-GMX-Trusted: 0 X-Spam: no; 0.00; ocaml:01 serialize:01 caml-list:01 functions:01 behaviour:01 data:02 structures:02 pattern:04 implement:06 implement:06 michael:07 schrieb:08 file:11 framework:11 framework:11 Am Freitag, 28. M=E4rz 2008 12:45:26 schrieb Jim Farrand: > > The opposite in fact. I want to be able to serialize things I (the > framework designer) never even thought of. I want the users of my > framework to have maximum flexibility to implement whatever behaviour > they like, without restricted them to the things I thought of putting > into the file format. couldn't the user implement and somehow register functions for serializing = his=20 own data structures?