std::snprintf fix for Cygwin

[Techwolfy]

Cygwin's current GCC (v4.9.3) has the same issue as described in #406. The fix described in the previous issue (using a preprocessor flag to skip the offending #define) works for this as well.

[BillyGoto]

Could we switch to std::ostringstream instead?
Its numeric formatting is actually specified in terms of printf's output,
and it's everywhere.

On Wednesday, February 10, 2016, Daniel Ring [email protected]
wrote:

Cygwin's current GCC (v4.9.3) has the same issue as described in #406
#406. The fix
described in the previous issue (using a preprocessor flag to skip the

offending #define) works for this as well.

You can view, comment on, or merge this pull request online at:

#418
Commit Summary

• std::snprintf fix for Cygwin

File Changes

• M src/lib_json/json_reader.cpp
  https://github.com/open-source-parsers/jsoncpp/pull/418/files#diff-0
  (2)
• M src/lib_json/json_writer.cpp
  https://github.com/open-source-parsers/jsoncpp/pull/418/files#diff-1
  (2)

Patch Links:

• https://github.com/open-source-parsers/jsoncpp/pull/418.patch
• https://github.com/open-source-parsers/jsoncpp/pull/418.diff

—
Reply to this email directly or view it on GitHub
#418.

ǝnɥɐuop ʎllıq

[cdunn2001]

@BillyGoto, 👍 Definitely a good idea.

But a quick fix is fine for now.