Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.arch.embedded > #28656

Re: Static JSON parser for embedded

From pozz <pozzugno@gmail.com>
Newsgroups comp.lang.c, comp.arch.embedded
Subject Re: Static JSON parser for embedded
Date 2019-06-06 09:54 +0200
Organization A noiseless patient Spider
Message-ID <qdagrt$fb$1@dont-email.me> (permalink)
References <qblnbg$402$1@dont-email.me> <2hODE.56712$8B4.29775@fx02.iad> <qd8kff$j0t$1@dont-email.me> <4xYJE.48747$RP3.172@fx11.iad>

Cross-posted to 2 groups.

Show all headers | View raw


Il 06/06/2019 01:48, Clifford Heath ha scritto:
> On 6/6/19 12:44 am, pozz wrote:
>>> So there is existing work, and no doubt community support for more.
>>> You could do a lot worse than start with ASN1CC.
>>
>> I eventually take a look at asn1scc and found a big limitation: it 
>> doesn't support extensibility feature of ASN.1.
> 
> One more comment. You mention (in other messages) that JSON is difficult 
> without using dynamic memory. ASN1CC is designed to avoid using dynamic 
> memory (for the same reason; embedded system constraints), which is why 
> it cannot implement arbitrary extensions. The best it could do is to 
> skip unknown extensions. 

Yes, many times this behaviour is good, instead of breaking at all the 
system.

> But in PER, items are not tagged or 
> length-delimited, and skipping an extension requires at least a 
> knowledge of how big it is.

Ok, PER can't be used to skip extended variables. However I can use BER. 
Why do asn1scc refuses to compile definitions file with extensions when 
BER is used?

Back to comp.arch.embedded | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

Re: Static JSON parser for embedded Clifford Heath <no.spam@please.net> - 2019-06-06 09:48 +1000
  Re: Static JSON parser for embedded pozz <pozzugno@gmail.com> - 2019-06-06 09:54 +0200

csiph-web