g_list_next (list->next considered harmful?)

On 12/17/01 11:01 AM, "Sven Neumann" <sven gimp org> wrote:

> another good reason for using list = g_list_next (list) instead.

What are the other good reasons?

The extra code generated by the macro to check for NULL? The loss of type
checking on the list parameter to the macro, making errors like list =
g_list_next (widget) possible? The fact that the macro's parameter is
evaluated twice, but the macro doesn't have an ALL_UPPERCASE name to make
programmers wary?

    -- Darin

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