The module contains the static variable MasterConfig, which all other

Petidomo routines can access via getMasterConfig(). The routine
getListConfig(), which is defined in config.c, too, used the "correct"
mechanism to access MasterConfig, even though it could access it
directly. Since I chose the same name ("MasterConfig" :->) for the
local copy of the pointer, gcc warns that this variable shadows the
static one. To get rid of this warning, and since it doesn't make one
bit a difference, getListConfig() accessse the static variable
directly now.
This commit is contained in:
Peter Simons 2001-01-19 20:51:11 +00:00
parent ac901a4e1c
commit f651fa8224

View File

@ -148,7 +148,6 @@ static char* ack_file;
const struct List_Config* getListConfig(const char * listname)
{
const struct PD_Config * MasterConfig;
struct List_Config * ListConfig;
Node node;
int rc;
@ -198,10 +197,6 @@ const struct List_Config* getListConfig(const char * listname)
address_file = "list";
ack_file = "acks";
/* Get the master configuration. */
MasterConfig = getMasterConfig();
/* Did we read this config file already? */
node = FindNodeByKey(ListConfigs, listname);