Error in GCC 8 compiler :static assertion failed: std::map must have the same value_type as its allocator

samyak darshan — Tue, 11 Jan 2022 09:30:14 -0000

Hello,

Greetings!

While porting to GCC 9, I'm getting an error which says static assertion failed, std::map must have same value as it allocator.

I understand that the json allocator doesn't provide same value type and it should be const specified.

Can you please help me with this?

P.S : I have found similar type of error in this json repo: https://github.com/moya-lang/Allocator/issues/12

Thank you

Error in GCC 8 compiler :static assertion failed: std::map must have the same value_type as its allocator

samyak darshan — Tue, 11 Jan 2022 09:29:22 -0000

Hello,

Greetings!

While porting to GCC 9, I'm getting an error which says static assertion failed, std::map must have same value as it allocator.

I understand that the json allocator doesn't provide same value type and it should be const specified.

Can you please help me with this?

P.S : I have found similar type of error in this json repo: https://github.com/moya-lang/Allocator/issues/12

Thank you

turning JSON_CASE_INSENSITIVE_FUNCTIONS on leads to linker error

Antony Paul Raj — Fri, 05 Mar 2021 11:36:08 -0000

Hi,

I want to use "find_nocase()" method. To get this function, I enabled "JSON_CASE_INSENSITIVE_FUNCTIONS" this flag in JSONOptions.h.
I am able to use in my method but while compiling, I get linker error "error LNK2001: unresolved external symbol "public: struct JSONNode::const_iterator __cdecl JSONNode::find_nocase"

Please help me to get out this issue.

Need help understanding why std::length error is thrown

Tanu Mathur — Wed, 17 Jul 2019 17:23:12 -0000

The code -
JSONNode topNode;
topNode.push_back(JSONNode("Connected", true));

Sometimes this results in std::length error thrown. The decoded callstack -

Exception Type: std::length_error
Exception what(): basic_string::_S_create
<libstdc++ stuff="">
internalJSONNode::Set(bool)
JSONNode::JSONNode(std::basic_string<char, std::char_traits<char="">, std::allocator<char> > const&, bool)</char></char,></libstdc++>

Your help in understanding why these two lines of code results in the exception sometimes is much appreciated.
Thanks

Request for permissions to submit a patch

cristi fati — Wed, 12 Sep 2018 08:58:57 -0000

Created a Makefile that works for MinGW on Win (when fired from cmd - no additional wrappers (e.g. Cygwin, MSYS*) involved)
Fixed some errors in the Ux Makefile (install, test targets)

More details on [SO]: How to create libjson.lib using makefile on windows? (@CristiFati's answer).

Error in 7.6.1 visual studio project file

Phil Rosenberg — Fri, 22 Jun 2018 12:59:50 -0000

There is a missing > on line 240 of the .vcproj file which stops the project loading. You can open this in notepad (it is an xml file) and manually insert it to make the file work again.

Solution and problem identified at https://stackoverflow.com/a/21582957/1051805

Phil

Please consider moving project to a new forum

Jeffrey Walton — Tue, 17 Oct 2017 06:42:40 -0000

Hi Everyone.

My apologies for making this request. It would be helpful to other developers and users if libjson moved to another forum, like GitHub. There's a lot of places you could move libjson to if interested. Confer, https://en.wikipedia.org/wiki/Comparison_of_source_code_hosting_facilities.

It would help developers because the code would be more accessible with fewer barriers. For example, we could directly download the latest release tarball with wget and code it into a script. Currently we cannot do that due to barriers placed by SourceForge.

It would help users because SourceForge is known to package and repackage source code and progams with additional unwanted programs. Some users consider the repackaged programs harmful because they install trojans and other malware on a users system. Confer, https://notepad-plus-plus.org/news/notepad-plus-plus-leaves-sf.html. I'm part of the Crypto++ project and we left SourceForge for the same reasons.

The reason I am making the request is, ClamAV uses libjson, and I need to script the download of the latest relase tarball to build ClamAV. But I really don't want it from SourceForge because I know the site tampers with files and packages.

Thanks for considering the suggestion.

Question to Jonathan about the decRef

Jakes — Mon, 09 Oct 2017 11:20:33 -0000

Anyone can help here?

Question to Jonathan about the decRef

Jakes — Sat, 07 Oct 2017 08:14:32 -0000

DId you find any solution, please share...

Floating point values "inf" and "nan" are parsed not correctely

Grzegorz Sejnota — Mon, 06 Feb 2017 13:50:07 -0000

Floating point values like std::numeric_limits<double>::quiet_NaN() and std::numeric_limits<double>::infinity() are not properly parsed from json string. Additional handling of inf and nan values (with taking into account their different versions eg. "NaN", "-nan", "+inf") should be taken into account during parsing string into node (file internalJSONNode.cpp method internalJSONNode::internalJSONNode(const json_string & name_t, const json_string & value_t)). I wanted to report this as a bug, but I do not have rights.

Example:

void check_double_nan()
{
    double value = std::numeric_limits<double>::quiet_NaN();

    // create a node
    JSONNode root;
    JSONNode node( "name", value );
    root.push_back( node );

    double value_from_node = node.as_float( );

    // std::isnan(value_from_node) == true
    std::cout << "Is value_from_node nan? " << std::isnan(value_from_node) << std::endl;

    // convert to string - serialize
    std::string serialized = root.write( );     // serialized = "{"name": nan}"

    // parse from string to node - deserialize
    JSONNode root_parsed = libjson::parse( serialized );
    JSONNode node_parsed = root_parsed.at( "node_with_nan" );

    // unfortunately, node is parsed as null node ->
    // method internalJSONNode::internalJSONNode(const json_string & name_t, const json_string & value_t)
    // catches that first letter is 'N' or 'n' and treats node as null
    double after_parsing = node_parsed.as_float( ); 

    // std::isnan(after_parsing) == false
    std::cout << "Is after_parsing nan? " << std::isnan(after_parsing) << std::endl;
}

Recent posts to Discussion

Error in GCC 8 compiler :static assertion failed: std::map must have the same value_type as its allocator

Error in GCC 8 compiler :static assertion failed: std::map must have the same value_type as its allocator

turning JSON_CASE_INSENSITIVE_FUNCTIONS on leads to linker error

Need help understanding why std::length error is thrown

Request for permissions to submit a patch

Error in 7.6.1 visual studio project file

Please consider moving project to a new forum

Question to Jonathan about the decRef

Question to Jonathan about the decRef

Floating point values "inf" and "nan" are parsed not correctely