Carlos Konstanski writes:
> Richard M Kreuter writes:
> > Carlos Konstanski writes:
> > > `sb-bsd-sockets:socket-make-stream' recently has had its :name keyword
> > > removed from the argument list. This is causing problems with
> > > existing code. What was the purpose behind this change?
> > Wishful thinking. Out of curiosity, what are you using that
> > argument for?
> Araneida uses it...
The decision to remove the keyword was more of an innocent act than a
plot to infuriate. The two or three of us who cared about the patch
that removed the argument looked around and didn't think we saw anything
using it. The keyword can be reinstated.
> This is not the first non-backward-compatible change I have had to
> contend with. I have to maintain a list of patches for araneida and
> clsql because both have current compatibility issues that did not
> exist at one time. Put yourself in my place: my boss expresses
> disdain that we have to patch 3rd party lisp libraries, when such
> patching is not necessary for .NET libraries...
For my part, I have never worked on any nontrivial software project,
with any languages or technologies, that didn't have its own tools and
practices for maintaining local patches, compatibility interfaces, and
regression testing machinery for dealing with third-party software.
Perhaps I've lived a peculiarly uncharmed life. In any event, such
tools and practices are particularly useful for investigating the
consequences of a prospective upgrade. As a friendly suggestion, I'd
encourage you to find or develop an approach of this sort.