-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Bruno Haible on 5/17/2007 3:33 AM: > > I prefer to avoid #include_next for the reasons mentioned in [1].
> [1] http://lists.gnu.org/archive/html/bug-gnulib/2007-02/msg00222.html However, that quote you listed said fix_includes "should be used only to make global corrections along the lines of `fixincludes'", which is exactly what the gnulib replacement headers are doing. I agree that #include_next is the right thing to do here. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGTE2y84KuGfSFAYARArtAAJ9nbtRQyXP7h4ZSHzWZyfYgUDAQowCfaF2N F7mDYUDzaIyH/y4TZO6cPkQ= =rPTd -----END PGP SIGNATURE-----
