On Fri, Jan 05, 2007 at 12:49:13PM +0000, Gerrit Renker wrote:
>
> Since the old definition is not used in the way "before(x, y) && !before(y,
> x)", but rather in the
> fashion "before(x, y)" or "after(y, x)", the main advantage of the new
> definition is that it makes
> this type of use a safe case.
This is not true because
if (before(x, y))
goto drop;
means that you're effectively using it as !before(x, y). In other words,
the change is good if our code read
if (before(x, y))
process_packet();
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
