Return-Path: Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Delivered-To: mailing list dev@apr.apache.org Received: (qmail 51981 invoked from network); 2 Jan 2001 14:17:55 -0000 Received: from 3ff8faf3.dsl.flashcom.net (HELO koj.covalent.net) (63.248.250.243) by h31.sny.collab.net with SMTP; 2 Jan 2001 14:17:55 -0000 Received: from rbb (helo=localhost) by koj.covalent.net with local-esmtp (Exim 3.16 #1) id 14DSJD-0004yb-00; Tue, 02 Jan 2001 06:21:03 -0800 Date: Tue, 2 Jan 2001 06:21:02 -0800 (PST) From: rbb@covalent.net X-Sender: rbb@koj To: Greg Stein cc: dev@apr.apache.org Subject: Re: cvs commit: apr-util/src/buckets ap_buckets_file.c In-Reply-To: <20010101224758.V10567@lyra.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > > > hehe... poor example. I use apr_get/set_filedata() :-) > > > > > > We've gone this far without the accessor functions. Adding > > > apr_mmap_from_file would obviate the need. > > > > Which doesn't solve the problem. How did you allocate the data? If you > > used a pool, you have to be careful of which one you used. If you don't > > get it from the file itself, then you have to pass the pool along with the > > file. > > > > It isn't a question of calling apr_set_userdata. It is a question of > > which pool was used to allocate the userdata. > > Sure sure :-) > > But back to the point: the problem at hand is to construct an mmap from a > file. We have a simple alternative for that. No, that isn't the problem. The problem at hand is to get access to the pool within an APR type. An example is to be able to create an mmap from a file. Ryan _______________________________________________________________________________ Ryan Bloom rbb@apache.org 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------