lcsmuller / jscon Goto Github PK

I got this error from the latest code. It seems it's not defined.

The following is the quote from the manual of fcvt.

Both the ecvt() and fcvt() functions return a pointer to a static string containing the ASCII representation of number. The static string is overwritten by each call to ecvt() or fcvt().
Conforming To

SVr2; marked as LEGACY in POSIX.1-2001. POSIX.1-2008 removes the specifications of ecvt() and fcvt(), recommending the use of sprintf(3) instead (though snprintf(3) may be preferable).

I want to run the code under test folder, but it seems there is no test data. It would be great if some sample test data is checked in.

str is

{
   "discord": {
      "token": "XXX"
   },
   "logging": {
      "filename": "YYY",
      "level": debug
   }
}

jscon_scanf(str,
              "%s[discord][token] %s[logging][filename] %s[logging][level]",
              settings->discord.token,
              settings->logging.filename, 
              settings->logging.level);

Does this work?

scanf example:

 char string[3];
 scanf("%3s", string);

scanf can be limited with how many characters to be read from the input string by format specifier like %3s. If json_scanf has this feature, we can convert many internal fields of discord-public-user.c to static arrays without worrying about buffer overruns.

file:/jscon-parser.c::105, 5
free(item->key); // item->key can be null.

While this is ok by C standard, the mismatching of malloc/free invoked at runtime could makes debugging memory leak harder.

json_scanf is very clever. But If I have a nested json object, can I still use json_scanf?

For example, given the following string

"{
   'project-configurations': 
   [
        { 'name':  'p1',   'build': 'b1' },
        { 'name':  'p2',   'build': 'b2' }
   ]
}"

Can I still use json_scanf to de-serialize it?