Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: =?UTF-8?Q?Josef_M=C3=B6llers?= <josef@invalid.invalid>
Newsgroups: comp.lang.c
Subject: Re: Which newsgroup for json parsing?
Date: Mon, 27 May 2024 13:51:53 +0200
Lines: 29
Message-ID: <lbjaepFm1vbU1@mid.individual.net>
References: <la1bjoF2anmU1@mid.individual.net> <v25c4k$1lhfu$1@dont-email.me> <lamvvbFb0g2U1@mid.individual.net> <v2aa1g$2q337$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net 1CSr+avAxW79TPbfDHuGPQEmrsWsJ6Q9J33PdUzDS06N/tWKph
Cancel-Lock: sha1:2nZFmFizp6DvAu1C4ms54CxHN7Y= sha256:1MdIC/10d2DisX2Oce47Ifw/f3GA8FkkciQxgGVoDV8=
User-Agent: Mozilla Thunderbird
Content-Language: en-US
In-Reply-To: <v2aa1g$2q337$1@dont-email.me>
Xref: csiph.com comp.lang.c:385179

On 18.05.24 15:21, Mikko wrote:
> On 2024-05-16 18:01:15 +0000, Josef Möllers said:
[...]
>> What one could do would be to use LEX to recognize the tokens and the 
>> write a recursive descent parser in plain C.
> 
> As YACC is too heavy I would use only LEX and do with C what LEX alone
> cannot do.

That is exactly what I wrote.

[...]


>> But, as I wrote in another posting, I have switched to libjson-c5 and 
>> the code works fine.
> 
> That the code works fine is the most important aspect.

In my 40+ years of experience in IT/programming (I graduated 1981 from a 
Dutch polytechnic "HIO" in Computer Science and have retired in 2022) I 
have learnt that "works fine" is only part of the work. Maintainability 
should be added as well. Even if it is code written for one's personal 
use only, it may need some work later and then it's crucial to have it 
maintainable.

But maybe you think so too,

Josef