Lately I've often thought that the versioning policy only addresses
half of the problem: the API. While it completely neglects the other
side of the package surface: the dependencies.
I should probably mention that this springs from my work with
packaging Haskell for ArchLinux and to be honest
Rogan Creswick schrieb:
We *do* still have some trouble maintaining / enforcing the PVP in
general, and there are a few things that it doesn't cover (I don't
believe exception behavior is covered, for example, although I'd argue
that throwing more exceptions than a previous version introduces
On 30.04.2011 5:06, Rogan Creswick wrote:
On Fri, Apr 29, 2011 at 3:05 PM, Daniil Elovkov
daniil.elov...@gmail.com wrote:
Hello list
I have an idea on versioning of Haskell packages and a small question about
release model of Haskell Platform. Since the latter is shorter let's start
with it.
Hello list
I have an idea on versioning of Haskell packages and a small question
about release model of Haskell Platform. Since the latter is shorter
let's start with it.
So, what is the release model of Haskell Platform? Is it released every
N months and frozen at that point? Or some
On Sat, Apr 30, 2011 at 02:05:39AM +0400, Daniil Elovkov wrote:
Hello list
I have an idea on versioning of Haskell packages and a small
question about release model of Haskell Platform. Since the latter
is shorter let's start with it.
So, what is the release model of Haskell Platform? Is
On Fri, Apr 29, 2011 at 3:05 PM, Daniil Elovkov
daniil.elov...@gmail.com wrote:
Hello list
I have an idea on versioning of Haskell packages and a small question about
release model of Haskell Platform. Since the latter is shorter let's start
with it.
So, what is the release model of Haskell
Hello Joachim,
Wednesday, December 20, 2006, 11:22:24 AM, you wrote:
The update code would now have to unmarshall a blob of game data,
traverse it to find all instances of SomeData, wrap them in a
one-element list to turn them into SomeData1s, reconstruct the blob of
game data with the
On 12/20/06, Bulat Ziganshin [EMAIL PROTECTED] wrote:
Hello Joachim,
Wednesday, December 20, 2006, 11:22:24 AM, you wrote:
The update code would now have to unmarshall a blob of game data,
traverse it to find all instances of SomeData, wrap them in a
one-element list to turn them into
As written in my other post, I will need to update data structures that
were marshalled to disk.
Now I'm wondering how to best prepare for the situation. E.g. one of the
common situations is that a single data item gets replaced by a list of
items.
Now assume that there's a SomeData type
Hi Jo,
You seem to be describing SYB and not knowing it:
http://homepages.cwi.nl/~ralf/syb1/
That basically does exactly what you've requested, in terms of
traversing all items when only one matters. That said, serialisation
is still a hard problem - think long and hard before picking a data
10 matches
Mail list logo
