Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 9088 invoked by uid 500); 17 Feb 2003 14:59:42 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 9075 invoked from network); 17 Feb 2003 14:59:42 -0000 Message-ID: <3E50F900.2050808@attglobal.net> Date: Mon, 17 Feb 2003 10:00:16 -0500 From: Jeff Trawick Reply-To: trawick@attglobal.net User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Damir Dezeljin CC: APR Subject: Re: Question about apr_sockaddr_ip_get() References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Damir Dezeljin wrote: > I want to retrive an IP addr string from the apr_sockaddr_t so I used > apr_sockaddr_ip_get(). The first argument of this function is char ** . ... > So the question is ... do I have to first alocate the memory for the > destination string? APR allocates the storage from the pool for the apr_sockaddr_t. You don't have to do any preparation. I'll add a comment to that effect to the description of the function. Thanks, Jeff