Unfortunately, not good. You get code like:
foo = (struct mylist *) slist_pop((slist *) &somelist->next);
So type safety goes out the window, and you gain some niceness in the
definition in exchange for ugliness in usage, the wrong tradeoff imho.
> struct slist
> {
> struct slist *next;
> };
>
>
> static inline void slist_add(struct slist *head, struct slist *elem)
> {
> elem->next = head->next;
> head->next = elem;
> }
>
> #define slist_push(head, elem) slist_add(head, elem)
>
> static inline struct slist *slist_pop(struct slist *head)
> {
> struct slist *elem = head->next;
>
> if (elem) {
> head->next = elem->next;
> elem->next = NULL;
> }
> return elem;
> }
-- Daniel - 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/