Joe Schaefer wrote: > Stas Bekman <[EMAIL PROTECTED]> writes: > > [...] > > >>I don't understand what this pool is for. the C docs for >>the record entry are totally unclear. > > > Since apr_file_t is an opaque structure in C, the > only way to extract any information about it is by > calling apr_file_info_get() and inspecting the > corresponding apr_finfo_t struct. Otherwise the > pool slot serves no useful purpose:
> ./file_io/win32/filestat.c: apr_pool_cleanup_register(finfo->pool, > pdesc, free_localheap, that is certainly an interesting use :) as philippe mentioned, if finfo->pool is clearly harmful then we should probably get rid of it. however, if people can add (meaningful) cleanups on the pool then that sounds like a good reason to keep it around, or at least a reason to not close it off just for the sake of closing it off. --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
