httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <>
Subject Re: Allow modules to add libraries
Date Sun, 06 Jun 1999 09:49:44 GMT
oh: and I just realized that I was a bit terse on this email (saturday
night drinking, sorry :-)...

What I'd like to say is that I believe declarative is better than
programmatic. for various reasons, but I simply felt like omitting that
in my email. Yes, we can get into a big discussion about declarative vs.
programmatic, but I felt it best to try to avoid that and simply provide
my position :-)  (rationale can be provided later :-)


Greg Stein wrote:
> Ralf S. Engelschall wrote:
> >...
> > Hmmm... I've no great objection to Ben's patch and idea in general, except
> > that it looks inconsistent. When we allow to adjust the libraries via "Libs:",
> > we also should allow "CFlags:", "LdFlags:", etc. But this OTOH is not really
> > necessary, because inside ConfigStart...ConfigEnd you're more flexible (you
> > can expand variables, etc.). So I still don't see a great advantage from
> > having "Libs:" in contrast to ``LIBS="$LIBS ..."''. Instead I've to conclude
> > that just providing "Libs:" is only a half-way solution and will confuse
> > people more than it provides advantages. Ben, where exactly is the benefit
> > from using "Libs:" above a config section instead of changing LIBS in the
> > config section itself? I guess I've overlooked an important intention here,
> > right?
> I believe that it is significantly better to use the Libs: type
> approach, as opposed to the LIBS= programmatic approach.
> In other words: declarative is much better than programmatic.
> Corollary: the more that you can move from a programmatic approach to a
> declarative approach, then the better off you are.
> In this sense, I fully support Ben's patch over the more general
> programmatic style offered by ConfigStart/ConfigEnd.
> Cheers,
> -g
> --
> Greg Stein,

Greg Stein,

View raw message