httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Prud'hommeaux" <e...@w3.org>
Subject Re: Letting Table store non-char data
Date Thu, 23 Aug 2001 14:45:59 GMT
On Wed, Aug 22, 2001 at 09:03:21PM -0700, Ian Holsman wrote:
> On Wed, 2001-08-22 at 20:58, Greg Stein wrote:
> > On Wed, Aug 22, 2001 at 03:59:56PM -0700, Ian Holsman wrote:
> > > On Wed, 2001-08-22 at 15:41, Brian Pane wrote:
> > > > Ian Holsman wrote:
> > > > >On Wed, 2001-08-22 at 14:12, Ryan Bloom wrote:
> > > > >>We had binary tables, but we removed them, because that is what
hash
> > > > >>tables are for.
> > > > >>
> > > > >agreed.
> > > > >but there are no hash tables on the request rec structure.
> > 
> > Yes there is. apr_pool_userdata_set(..., r->pool)
> Thanks.
> never knew about this function.

I am switching my code to use pool userdata but wonder if swapping the
parms make make the calling convention more consistent with the other
pool methods that take the pool as first parm.

- apr_status_t apr_pool_userdata_get(void **, char *, apr_pool_t *);
+ apr_status_t apr_pool_userdata_get(apr_pool_t *, char *, void **);
#				      this ptr      attr    value

-- 
-eric

(eric@w3.org)
Feel free to forward this message to any list for any purpose other than
email address distribution.

Mime
View raw message