caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Richard Jones <rich@annexia.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Calendar library: version 2.0
Date: Wed, 13 Feb 2008 10:24:13 +0000	[thread overview]
Message-ID: <20080213102413.GE16784@annexia.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0802131013260.18556@serveur9-10.lri.fr>

On Wed, Feb 13, 2008 at 10:30:47AM +0100, Julien Signoles wrote:
> 
> >OK, I take that back.  Everything is now packed under CalendarLib.*
> >which makes the issue of module names moot.
> 
> Indeed it is one of my arguments for packing calendar.
> 
> >Also it means nothing is backwards compatible :-(  That could be a
> >problem because it means I need to release two different versions of
> >everything which uses the calendar library, but at least that's just a
> >one-off event.
> 
> You're obviously right: as calendar is now packed, everything which uses 
> calendar v1.* does not work anymore with calendar v2.* (and vice-versa).
> 
> But the only change to do in your code is: add "open CalendarLib" at the 
> top of your files and all is fine because the API is backward compatible 
> inside the pack.

It may be a tiny change, but it still needs two versions of the code
to deal with.

API changes aren't handled gracefully in OCaml.  The same thing
happens whenever the lablgtk API changes incompatibly - I end up using
the C preprocessor or Makefile hacks.

Rich.

-- 
Richard Jones
Red Hat


  parent reply	other threads:[~2008-02-13 10:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09  9:45 Julien Signoles
2008-02-12 18:20 ` [Caml-list] " Richard Jones
2008-02-12 18:26   ` Richard Jones
2008-02-13  9:30     ` Julien Signoles
2008-02-13 10:00       ` Nicolas Pouillard
2008-02-13 12:53         ` David Allsopp
2008-02-13 10:24       ` Richard Jones [this message]
2008-02-12 19:38   ` Stéphane Glondu
2008-02-12 19:49     ` Richard Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080213102413.GE16784@annexia.org \
    --to=rich@annexia.org \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).