This is the mail archive of the
mailing list for the Cygwin project.
Re: Support for sa_sigaction
"Larry Hall (Cygwin)" ha escrito:
> JoaquÃn MÂª LÃ³pez MuÃ±oz wrote:
> > Corinna Vinschen ha escrito:
> >> Use `cvs annotate' to find the date when sa_sigaction has been
> >> introduced and then check against the release dates. So, from what I
> >> can tell, 1.5.7 should already have sa_sigaction. sa_sigaction has been
> >> introduced immediately when introducing the file include/cygwin/signal.h
> >> on 2003-11-03, while Cygwin 1.5.7 has been released on 2004-01-31.
> > These dates are correct, but there's no include/cygwin/signal.h in my
> > local copy of cygwin. I don't know which exact Cygwin package would
> > bring that header in.
Umm... I think the implied result that cygwin/signal.h *begun* to be supported
in Cygwin 1.5.11 is not correct, as it looks like 1.5.11 is as far in the past as
the package grep tool can go:
> >> However, why is it important to know? Just use the latest Cygwin
> >> version and you're done.
> > In order to support legacy environments. I'm doing this reasearch in connection with
> > the Boost Config Library (http://boost.org/libs/config/config.htm ).
> Still not clear why it's important for you to live in the past. What
> exactly about upgrading is the problem?
Boost policy is to try to support as many platforms as possible, within
reasonable limits, rather than forcing users to upgrade to the latest version
of their particular environment. Boost.Config merely codifies the particular
features and quirks of each platform so as to ease the task of writing
cross-platform code; I'm trying to fine tune an aspect of Boost.Config
(a macro called BOOST_HAS_SIGACTION) for the Cygwin familiy.
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html