kazuho/picojson

Issues

• Problem mixing PICOJSON_USE_INT64 with non-PICOJSON_USE_INT64

  #160 opened 8 months ago by radoslawkojdecki
  0

• DOes it support older versions of C++ like C++ 98 , less than C++11?

  #153 opened 2 years ago by naveenkumar638
  1

• Is it ok if I publish a NuGet package?

  #151 opened 2 years ago by diogo-strube
  1

• Proposed macro to override throw

  #148 opened 2 years ago by shun126
  0

• get<int> causes linker error in visual studio, must use int64_t with PICOJSON_USE_INT64

  #145 opened 3 years ago by jokoon
  1

• _serialize collides wtih immintrin.h

  #141 opened 4 years ago by nishiken
  2

• Support input std::wstring

  #126 opened 4 years ago by Hanam824
  2

• Any interest in sponsorship?

  #137 opened 4 years ago by nmr8acme
  0

• Build error '(': illegal token on right side of '::' on std::numeric_limits<int64_t>::min() <= ival in picojson.h

  #138 opened 4 years ago by IshaanKarnik
  1

• How to transfer to function uint8_t, uint16_t?

  #139 opened 4 years ago by GermanAizek
  0

• "assignment within conditional expression" warning with (at least) Visual Studio 2019

  #129 opened 4 years ago by GabrieleGiuseppini
  0

• cannot parse tab correctly : syntax error at line 1 near

  #124 opened 5 years ago by phoenixbai
  1

• picojson does not support -fno-exceptions

  #117 opened 6 years ago by rhysd
  3

• User-defined conversions

  #121 opened 5 years ago by Timeroot
  0

• Parse error syntax error at line 1 near:

  #82 opened 9 years ago by majimboo
  2

• error in readme; Reading JSON using the pull interface

  #120 opened 5 years ago by Ryder17z
  0

• Warning about return from void function

  #119 opened 5 years ago by f18m
  0

• numeric limits min, max

  #116 opened 6 years ago by gha88
  0

• operator== does not honor int64_t

  #113 opened 6 years ago by johannesgajdosik
  0

• parse sample with istream_iterator in README ignores whitespace in string

  #112 opened 6 years ago by sakichan
  0

• Weird issues when using custom parse contexts

  #110 opened 7 years ago by exavi
  1

• Sometimes picojson's .mkdn isn't easy to see.

  #106 opened 7 years ago by YuseiIto
  0

• Map of Maps is incorrectly parsed

  #105 opened 7 years ago by Vicfero
  1

• Why is there no `parse_object_stop` in the streaming API?

  #104 opened 7 years ago by paulreimer
  0

• Couldn't parse simply JSON string

  #100 opened 8 years ago by bl4ck5un
  1

• picojson - Abort on parsing possible DoS

  #94 opened 8 years ago by dzonerzy
  1

• picojson eats one too many characters when parsing a number

  #92 opened 8 years ago by ChrisJefferson
  3

• Warning about __STDC_FORMAT_MACROS

  #91 opened 8 years ago by chishiro
  0

• Conformance report for reference

  #90 opened 8 years ago by miloyip
  1

• Supper Integer Type

  #78 opened 9 years ago by zhoub
  1

• Get root node?

  #86 opened 9 years ago by egordorichev
  3

• missed colon in the first example in readme

  #83 opened 9 years ago by Dushistov
  0

• String to array

  #80 opened 9 years ago by tpolekhin
  2

• Hexadecimal support

  #79 opened 9 years ago by m1tk4
  5

• consider exposing value::_type or provide a value::_type to std::string utility

  #77 opened 9 years ago by weegreenblobbie
  0

• do "explicit" is needed in the constructor ?

  #76 opened 9 years ago by satoren
  0

• bug on Solaris10 (gcc version 4.4.2)

  #69 opened 9 years ago by takmatumot
  1

• Maintaining order of values when serializing.

  #54 opened 10 years ago by Ender1618
  4

• value::operator= does not allow for navigation

  #65 opened 10 years ago by GabrieleGiuseppini
  5

• new ( this ) value ( x ); won't compile on visual studio 2010

  #64 opened 10 years ago by v71
  2

• Consider adding picotest/picotest.[ch] to the release tarball

  #61 opened 10 years ago by karya0
  5

• No operator[] for const object

  #59 opened 10 years ago by JetForMe
  2

• Crashes parsing end of array or empty array

  #60 opened 10 years ago by JetForMe
  4

• Add utility `parse` function that takes a `std::string` as input

  #55 opened 10 years ago by cdeil
  3

• Support arbitrary precision numbers

  #51 opened 10 years ago by ChrisJefferson
  1

• No function to access nested values

  #44 opened 10 years ago by amikhalev
  6

• Consider add clib package.json

  #50 opened 10 years ago by quark-zju
  1

• Picojson has evil globals

  #48 opened 10 years ago by rmartinho
  1

• Adding license clause to example files.

  #41 opened 10 years ago by timothysc
  3

• is<int>() is defined even though get<int>() is not

  #35 opened 11 years ago by kazuho
  0