-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Bob Friesenhahn on 6/7/2008 10:01 AM: |> Marking a macro obsolete does not mean that existing projects have to |> remove it, nor that we will break its behavior. Rather, it means that |> new projects don't have to worry about needing to use it | | My own project does include support for signal handlers which return | 'int'. It is using this macro. Without this provision, the code would | fail to compile on some systems due to prototype mismatch. Again, obsoleting a macro does not mean that existing code that relied on the macro will break. As long as you don't delete AC_TYPE_SIGNAL from your configure.ac, your project will not be impacted (other than the fact that if you run 'autoconf -Wall' you will get a new warning, mentioning that the macro is obsolete when porting to modern targets). - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@xxxxxxx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkhKxHUACgkQ84KuGfSFAYA0gACgjfOTBUNzpOpqI0o87Qi7vkOA U5AAoNggGt5d8iWcURnDAnafgroed1X2 =3mB4 -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
