Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 11 Aug 2001 00:16:33 -0700
From: Aaron Bannert <aaron@clove.org>
To: dev@apr.apache.org
Subject: Re: use of malloc in dso.c instead of apr_palloc?
Message-ID: <20010811001633.A22820@clove.org>
References: <Pine.LNX.4.33L2.0108111222510.3273-100000@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: 
 <Pine.LNX.4.33L2.0108111222510.3273-100000@localhost.localdomain>;
 from sterling@designmultimedia.com on Sat, Aug 11, 2001 at 12:25:11PM -0400

On Sat, Aug 11, 2001 at 12:25:11PM -0400, Sterling Hughes wrote:
> 
>     Well, as the overly long title suggests, is there any reason that
>     malloc() is used in dso.c (unix and aix)?  apr_palloc() seems
>     fine for these purposes (temporary string).  Also, as a side
>     note, sizeof(char) is used in the allocation, which is extreaneous,
>     because a char is always equivalent to one base unit of memory
>     (well, at least that's how I interpret ANSII).

If I remember my compiler class correctly, sizeof() gives a constant scalar
at compile-time. Any decent compiler will perform constant folding on
expressions like (sizeof(char)*12) before producing object code. This means
you should feel free to use sizeof() liberally if it helps readability.

-aaron