summaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorJeremy Harris <jgh146exb@wizmail.org>2020-05-06 14:04:44 +0100
committerJeremy Harris <jgh146exb@wizmail.org>2020-05-06 14:04:44 +0100
commita368cc11b211657f86f2495002823bc09b71a9f1 (patch)
tree29caa815cad21555c70aa4b81a92f1f939aad1e0 /src
parent824ac9569a44ae411785f7ba2014d243e85b992d (diff)
docs & more debug
Diffstat (limited to 'src')
-rw-r--r--src/src/match.c10
1 files changed, 2 insertions, 8 deletions
diff --git a/src/src/match.c b/src/src/match.c
index ec769b3a9..db02b37bd 100644
--- a/src/src/match.c
+++ b/src/src/match.c
@@ -271,12 +271,6 @@ if ((semicolon = Ustrchr(pattern, ';')) == NULL)
/*
XXX looks like $0 may be usable
-XXX could add setting of *valueptr to all the OK returns; seems doable here, the Q
- is: what effect would it have at config-file level. domain_data & local_part_data
- would get filled in... might anyone be checking it for emptiness? I think the docs
- do not say "will be empty otherwise", so that seems ok.
-XXX WORRY: we get new caching of named-list match results. Is that cache checked
- for the key being matched?
*/
}
@@ -698,7 +692,7 @@ while ((sss = string_nextinlist(&list, &sep, NULL, 0)))
nb->cache_data = p;
if (*valueptr)
DEBUG(D_lists) debug_printf("data from lookup saved for "
- "cache for %s: %s\n", ss, *valueptr);
+ "cache for %s: key '%s' value '%s'\n", ss, p->key, *valueptr);
}
}
}
@@ -710,7 +704,7 @@ while ((sss = string_nextinlist(&list, &sep, NULL, 0)))
else
{
DEBUG(D_lists) debug_printf("cached %s match for %s\n",
- ((bits & (-bits)) == bits)? "yes" : "no", ss);
+ (bits & (-bits)) == bits ? "yes" : "no", ss);
cached = US" - cached";
if (valueptr)