Same here,
we walked in the office one day and our system was broken because of
some change in petitParser.
The same thing happenned with roassal and other libraries.
We are not always (rarely) in a position where we can fix our code
to keep working with the new version of the libraries we use.
This does not mean the developers are not good, it is just that they
evolve their stuff according to their needs and our needs are not
the same.
So our solution is to rely on static revision numbers that are known
to work.
From time to time, when we are ready, we do the work to update to a
new version of the libraries.
This saves us a lot of time and even more troubles.
Depending on symbolic names like "stable" is no good because the
stable revision also moves, and not always when we are ready for it.
This is not true for everything, moose for example tends to be much
more stable that Roassal which evolves at a fast pace.
PetitParser evolves more slowly too, but for a long time, there has
been a change in it which we could not leave with (not sure what is
the status currently)
So we try to keep with the latest version when we can, but sometimes
it is not a viable solution
nicolas
On 23/06/2015 13:35, Peter Uhnák wrote: