Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 76456 invoked by uid 500); 6 Mar 2003 22:44:00 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 76441 invoked from network); 6 Mar 2003 22:43:59 -0000 From: =?ISO-8859-1?Q?Andr=E9?= Malo Subject: introduce getword_conf_s? MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Organization: TIMTOWTDI Date: Thu, 6 Mar 2003 23:41:52 +0100 To: dev@httpd.apache.org Message-ID: User-Agent: Yes! X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N We have a PR (16631) that mentions that at least one error log entry is not= =20 assigned to the appropriate error log (in 1.3). The warning is written by= =20 ap_getword_conf, which doesn't know anything about server_rec structures. I've discovered this by trying to forward port this feature. However, I'd= =20 really like to see this warning to go into 2.1 and here written to the=20 right log. What do you think about introducing a wrapper around=20 ap_getword_conf, called ap_getword_conf_s (or similar, suggestions welcome= =20 ;-)? It would take server_rec *s as a third argument and could write the=20 warning into the right place. nd --=20 print "Just Another Perl Hacker"; # Andr=E9 Malo, #