yes, I wss saving that trivial fix for later. (its a little less trivial
in the presence of bare struct * heads, rather than full struct
instances, but still just language mechanics.)
> Smaller point: why bother obfuscating the parameter names? You will
> need to do that for locals in macros but parameters should cause no
> name conflicts.
*shrug* either way is fine with me.
but really, I think these are DOA. having to define a single magical
structure member makes these more trouble than they're worth. I've come
to prefer wli's 'struct list' approach. It has the added benefit of
actually being sanely implementable with shared code, something
ridiculously low memory setups might appreciate. the deltion walking
function might actually be bugger than the function-calling code
overhead :)
- z
-
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/