[lkml]   [2019]   [Dec]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Improving documentation for programming interfaces
On Fri, Dec 20, 2019 at 05:23:27PM +0100, Markus Elfring wrote:
> >> Some functions allocate resources to which a pointer (or handle) is returned.
> >> I would find it nice then if such a pointer would contain also the background
> >> information by which functions the resource should usually be released.
> >>
> >> Can it become easier to determine such data?
> …
> > It's unclear to me what you are requesting/proposing?
> I suggest to clarify combinations for object construction and proper resource release.
> > Can you be a bit more concrete?
> Further examples:
> * kmalloc ⇒ kfree
> * kobject_create ⇒ kobject_put
> * device_register ⇒ put_device
> Can preprocessor macros help to express any more relationships for similar function pairs?

Sorry, this is still not making sense. You said "a pointer would
contain also the background information by which the resource should
usually be released". Huh? There's no room for a pointer to also
store context of whether it was allocated using kmalloc, or malloc,

Did you have some concrete idea of how a preprocessor macros could be
used to perform what appears to be completely impractical?

And how would that information be used by the kernel? And for what
benefit? And can you show that the benefits will be worth the costs?

- Ted

 \ /
  Last update: 2019-12-20 18:18    [W:0.067 / U:4.448 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site