Return-Path: Delivered-To: apmail-perl-dev-archive@perl.apache.org Received: (qmail 85885 invoked by uid 500); 20 Nov 2001 04:06:44 -0000 Mailing-List: contact dev-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@perl.apache.org Received: (qmail 85867 invoked from network); 20 Nov 2001 04:06:44 -0000 X-Authentication-Warning: mako.covalent.net: dougm owned process doing -bs Date: Mon, 19 Nov 2001 20:11:17 -0800 (PST) From: Doug MacEachern X-Sender: dougm@localhost To: Stas Bekman cc: dev@perl.apache.org Subject: Re: cvs commit: modperl-2.0/src/modules/perl modperl_config.c In-Reply-To: <3BF9D497.7010003@stason.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tue, 20 Nov 2001, Stas Bekman wrote: > which as we have discussed is not what we want, since we don't want all > the data from the two. The overlay structure should override the base > structure if the same key exists in both. I guess I should put a better > comment in place. ok, remind me why we don't want all the data from the two then. or let me ask differently: why do we want to be different from 1.x? and most important: how do you know this will not break 1.x code? seems to me PerlAddVars should be merged the same as they are in 1.x. if you're only using PerlSetVar, add will still override base, since the add entry is there first, which is what scalar $r->dir_config->get('key') will return. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org For additional commands, e-mail: dev-help@perl.apache.org