Browse thread
[ANN] OCaml Reins 0.1 - Persistent Data Structure Library
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Daniel_Bünzli <daniel.buenzli@e...> |
| Subject: | Re: [Caml-list] Re: Cherry-picking modules (was Re: [ANN] OCaml Reins 0.1 - Persistent Data Structure Library) |
Le 26 sept. 07 à 01:33, Sylvain Le Gall a écrit : > Anyway, embeding any external code into your project is a nightmare > for > security/maintenance in the long term... I would avoid this > solution if > i want things that doesn't have problem. As I explained I don't think so. In the best case you delegate the nightmare to the user. Can you explain exactly where the nightmare is with embedding ? If the distributed modules you integrate are labelled with a version, I don't see it. The work needed for maintenance in the long term is exactly the same, except only the developer has to care. As for security updates in ocaml, you cannot anyway rely on dynamic linking. Which I see as a good thing, for applications dynamic linking creates more problems than it solves and should be avoided most of the time (except of course for system libraries). Best, Daniel