caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: Julien Signoles <julien.signoles@lri.fr>
Cc: rich <rich@annexia.org>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Calendar library: version 2.0
Date: Wed, 13 Feb 2008 11:00:04 +0100	[thread overview]
Message-ID: <1202896751-sup-7384@port-ext6.ensta.fr> (raw)
In-Reply-To: <Pine.LNX.4.63.0802131013260.18556@serveur9-10.lri.fr>

[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]

Excerpts from Julien Signoles's message of Wed Feb 13 10:30:47 +0100 2008:
> 
> > 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.
> 
> For your application(s), a possible trade-off is:
> - do this tiny change
> - release a new version requiring calendar v2.*

Why not releasing a last version of the v1 adding an empty CalendarLib.ml?

-- 
Nicolas Pouillard aka Ertai

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 186 bytes --]

  reply	other threads:[~2008-02-13 10:01 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 [this message]
2008-02-13 12:53         ` David Allsopp
2008-02-13 10:24       ` Richard Jones
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=1202896751-sup-7384@port-ext6.ensta.fr \
    --to=nicolas.pouillard@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=julien.signoles@lri.fr \
    --cc=rich@annexia.org \
    /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).