This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Doubtful about unison

On 3/3/2011 8:06 AM, Andy Koppe wrote:
In a slightly different line of thought, isn't it rather brittle of
Cygwin that a minor upgrade (I was already at some 1.7 version)
breaks applications? Think, a contrario, of how you can still run
ancient Windows apps on XP.

The problem you had was a case of broken forward compatibility, whereas your Windows example is talking about backward compatibility.

Yes, you're right, I had it mostly backwards.

However in this case it seems the problem wasn't that Unison used new
features of Cygwin but that somehow the layout of the Cygwin DLL had
changed, in a way that broke applications. I am not much of a system-
level programmer but in higher-level languages you'd expect things to
keep working as long as functionality (i.e., method signatures) has not
changed or that the new functionality is a strict superset of the older
one. I am sure I am betraying a woeful ignorance of C-level programming,
of linkers etc (which maybe isn't such a wise thing to do in a public
forum; oh well) with this question but isn't there a way to pin down
entry points and suchlike to ensure better forward compatibility? Would
rebaseall have helped? This is just for my enlightenment: I am not
suggesting you twist yourself into pretzel shapes trying to ensure
stellar forward compatibility; I suspect Cygwin programming is tricky
enough as it is.

-- O.L.

-- Problem reports: FAQ: Documentation: Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]