Re: g_list_next (list->next considered harmful?)

On 17 Dec, Darin Adler wrote:

> The extra code generated by the macro to check for NULL?

A good compiler will notice that the loop itself checks for NULL and
kill the additional instruction(s).

> The loss of type checking on the list parameter to the macro, making
> errors like list = g_list_next (widget) possible?

That's indeed severe but why is the cast in place anyway?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]