bump max node depth from 32 to 64 - json2tsv - JSON to TSV converter
 (HTM) git clone git://git.codemadness.org/json2tsv
 (DIR) Log
 (DIR) Files
 (DIR) Refs
 (DIR) README
 (DIR) LICENSE
       ---
 (DIR) commit d9eb13696d70c0d87f13438cd9cb34d34102fb82
 (DIR) parent 9f4ab639718e4351b02b4bde6035cd588c32b169
 (HTM) Author: Hiltjo Posthuma <hiltjo@codemadness.org>
       Date:   Tue, 15 Oct 2019 19:00:17 +0200
       
       bump max node depth from 32 to 64
       
       32 is already insanely high, but bump to 64 to be on the very safe side.
       I Compared this value to a few other JSON parsers.
       
       Diffstat:
         M json2tsv.1                          |       2 +-
         M json2tsv.c                          |       2 +-
       
       2 files changed, 2 insertions(+), 2 deletions(-)
       ---
 (DIR) diff --git a/json2tsv.1 b/json2tsv.1
       @@ -39,5 +39,5 @@ can change the meaning of the nodename field.
        The JSON parser handles all valid JSON.
        It also handles some invalid JSON like object key strings without quoting (").
        .It
       -The maximum depth of objects or arrays is hard-coded to 32 levels deep.
       +The maximum depth of objects or arrays is hard-coded to 64 levels deep.
        .El
 (DIR) diff --git a/json2tsv.c b/json2tsv.c
       @@ -20,7 +20,7 @@ enum JSONType {
                TYPE_OBJECT    = 'o'
        };
        
       -#define JSON_MAX_NODE_DEPTH 32
       +#define JSON_MAX_NODE_DEPTH 64
        
        struct json_node {
                enum JSONType type;