Re: Style question: Should one check for NULL pointers?

From: Horst von Brand (vonbrand@inf.utfsm.cl)
Date: Sat Jul 12 2003 - 13:40:20 EST

Next message: Horst von Brand: "Re: SECURITY - data leakage due to incorrect strncpy implementation"
Previous message: Andrew Morton: "Re: 2.5 'what to expect'"
In reply to: Alan Stern: "Re: Style question: Should one check for NULL pointers?"
Next in thread: Alan Stern: "Re: Style question: Should one check for NULL pointers?"
Reply: Alan Stern: "Re: Style question: Should one check for NULL pointers?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Alan Stern <stern@rowland.harvard.edu> said:

[...]

> But if you look very far through the kernel sources you will see many
> occurrences of code similar to this:
>
> static void release(struct xxx *ptr)
> {
> if (!ptr)
> return;
> ...
>
> I can't see any reason for keeping something like that.

Just like free(3)

-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Next message: Horst von Brand: "Re: SECURITY - data leakage due to incorrect strncpy implementation"
Previous message: Andrew Morton: "Re: 2.5 'what to expect'"
In reply to: Alan Stern: "Re: Style question: Should one check for NULL pointers?"
Next in thread: Alan Stern: "Re: Style question: Should one check for NULL pointers?"
Reply: Alan Stern: "Re: Style question: Should one check for NULL pointers?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Jul 15 2003 - 22:00:46 EST