On Wed, 27 Jun 2001, William A. Rowe, Jr. wrote:
> It brings up a deeper issue. I'm thinking we actually need a
> composite magic number... the apr and apr-util changes we make also
> impact new-httpd, but there is no clear way to signal those to the
> httpd list when apr is mucking things up.
>
> Do you all suppose we ought to have an APR magic number, that assures
> the httpd people that the arguments to existing apr functions haven't
> been flipped about? This way the apr list can assume responsibility
> for their changes, while the httpd RM doesn't have to review that
> work?
+1. I'd been wondering about that myself as I've been tweaking various
API's.
--Cliff
--------------------------------------------------------------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
