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>

diff --git a/output/sqlite3/ulogd_output_SQLITE3.c b/output/sqlite3/ulogd_output_SQLITE3.c
index 0de8145e52764e234bc83d6f879833aebbf58b66..65e320b275b061d2ab755d7e29e67d4105228943 100644 (file)
--- 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++;
        }