diff options
| author | Pablo Neira Ayuso <pablo@netfilter.org> | 2011-02-25 18:40:30 +0100 |
|---|---|---|
| committer | Pablo Neira Ayuso <pablo@netfilter.org> | 2011-02-25 18:40:30 +0100 |
| commit | a99693efa30139c7d5ce42cdb32618fe24b99234 (patch) | |
| tree | c86db61e9108025146e7f4a02c701319e0370654 | |
| parent | 24d635a48ba16e97ef3d6c089c942470141d80b6 (diff) | |
sqlite3: use continue instead of goto in sqlite3_interp()
Use continue instead of goto inside loop. I don't need to scroll
up and down in the code to know what the jump is performing.
I think this improve code readability. It's a comestic cleanup,
of course.
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
| -rw-r--r-- | output/sqlite3/ulogd_output_SQLITE3.c | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/output/sqlite3/ulogd_output_SQLITE3.c b/output/sqlite3/ulogd_output_SQLITE3.c index 0de8145..65e320b 100644 --- a/output/sqlite3/ulogd_output_SQLITE3.c +++ b/output/sqlite3/ulogd_output_SQLITE3.c @@ -151,7 +151,8 @@ sqlite3_interp(struct ulogd_pluginstance *pi) if (f->key == NULL || !IS_VALID(*k_ret)) { sqlite3_bind_null(priv->p_stmt, i); - goto next_field; + i++; + continue; } switch (f->key->type) { @@ -221,8 +222,6 @@ sqlite3_interp(struct ulogd_pluginstance *pi) ulogd_log(ULOGD_NOTICE, "unknown type %d for %s\n", f->key->type, f->key->name); } - - next_field: i++; } |