httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <s...@stason.org>
Subject Re: apreq2 style question
Date Wed, 23 Apr 2003 23:10:25 GMT
Joe Schaefer wrote:
> Stas Bekman <stas@stason.org> writes:
> 
> 
>>Any special reasons why APREQ_ENV, which is not a macro, is using
>>upcase and macros apreq_env_* are using lowercase? 
> 
> 
> It just worked out that way.  I was making so many changes to
> the apreq_env struct that I just started using the macros.
> They saved me some editing time whenever I changed the struct.
> 
> The good news is that the macros are mapped to plain-old 
> function calls, so they behave like functions.  You just can't
> use the macro name as a function pointer.
> 
> 
>>Won't it be more intuitive to have things the other way around?
> 
> 
> Perhaps, but other than the logging stuff, apreq_env.h shouldn't
> be applicable to end-user code.  It's really only there to make
> libapreq work within a given environment; and those are maintained
> by *us*, in the httpd-apreq-2/env/ directory.

I wasn't questioning macros *usage*, I was asking why do we have functions in 
upper case and macros in lower case. And suggesting that we may consider to 
have it the other way around: macros in upper case, functions in lowercase.

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com


Mime
View raw message