Paul Sokolovsky wrote:
By this criteria I happened to choose macros syntax. But it's still
merely a syntax, and I don't pledge for it. If there's more movement
towards using explicit low-level forms like 1) or 2) instead of
introducing new syntactic pattern, then macro syntax can be
Hello H.,
Wednesday, March 28, 2007, 7:32:57 PM, you wrote:
> Paul Sokolovsky wrote:
>>
>> In this respect, VTABLE(), METHOD() macros serve the same purpose as
>> container_of() and list_for_each() - they are besides offering (more)
>> convenient syntax, also carry important annotattion and
Paul Sokolovsky wrote:
In this respect, VTABLE(), METHOD() macros serve the same purpose as
container_of() and list_for_each() - they are besides offering (more)
convenient syntax, also carry important annotattion and educational
messages, like "it's ok, and encouraged to embed one structure
Paul Sokolovsky wrote:
In this respect, VTABLE(), METHOD() macros serve the same purpose as
container_of() and list_for_each() - they are besides offering (more)
convenient syntax, also carry important annotattion and educational
messages, like it's ok, and encouraged to embed one structure
Hello H.,
Wednesday, March 28, 2007, 7:32:57 PM, you wrote:
Paul Sokolovsky wrote:
In this respect, VTABLE(), METHOD() macros serve the same purpose as
container_of() and list_for_each() - they are besides offering (more)
convenient syntax, also carry important annotattion and
Paul Sokolovsky wrote:
By this criteria I happened to choose macros syntax. But it's still
merely a syntax, and I don't pledge for it. If there's more movement
towards using explicit low-level forms like 1) or 2) instead of
introducing new syntactic pattern, then macro syntax can be
6 matches
Mail list logo
