Skip to content

Commit 10f03df

Browse files
floriflori
committed
initial commit
0 parents  commit 10f03df

File tree

119 files changed

+38028
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

119 files changed

+38028
-0
lines changed

‎.gitignore

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
.*.sw[pon]
2+
coverage
3+
pkg

‎CHANGES

+127
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,127 @@
1+
2009-08-23 (1.1.8)
2+
* Applied a patch by OZAWA Sakuro <[email protected]> to make json/pure
3+
work in environments that don't provide iconv.
4+
* Applied patch by okkez_ in order to fix Ruby Bug #1768:
5+
http://redmine.ruby-lang.org/issues/show/1768.
6+
* Finally got around to avoid the rather paranoid escaping of ?/ characters
7+
in the generator's output. The parsers aren't affected by this change.
8+
Thanks to Rich Apodaca <[email protected]> for the suggestion.
9+
2009-06-29 (1.1.7)
10+
* Security Fix for JSON::Pure::Parser. A specially designed string could
11+
cause catastrophic backtracking in one of the parser's regular expressions
12+
in earlier 1.1.x versions. JSON::Ext::Parser isn't affected by this issue.
13+
Thanks to Bartosz Blimke <[email protected]> for reporting this
14+
problem.
15+
* This release also uses a less strict ruby version requirement for the
16+
creation of the mswin32 native gem.
17+
2009-05-10 (1.1.6)
18+
* No changes. І tested native linux gems in the last release and they don't
19+
play well with different ruby versions other than the one the gem was built
20+
with. This release is just to bump the version number in order to skip the
21+
native gem on rubyforge.
22+
2009-05-10 (1.1.5)
23+
* Started to build gems with rake-compiler gem.
24+
* Applied patch object/array class patch from Brian Candler
25+
<[email protected]> and fixes.
26+
2009-04-01 (1.1.4)
27+
* Fixed a bug in the creation of serialized generic rails objects reported by
28+
Friedrich Graeter <[email protected]>.
29+
* Deleted tests/runner.rb, we're using testrb instead.
30+
* Editor supports Infinity in numbers now.
31+
* Made some changes in order to get the library to compile/run under Ruby
32+
1.9.
33+
* Improved speed of the code path for the fast_generate method in the pure
34+
variant.
35+
2008-07-10 (1.1.3)
36+
* Wesley Beary <[email protected]> reported a bug in json/add/core's DateTime
37+
handling: If the nominator and denominator of the offset were divisible by
38+
each other Ruby's Rational#to_s returns them as an integer not a fraction
39+
with '/'. This caused a ZeroDivisionError during parsing.
40+
* Use Date#start and DateTime#start instead of sg method, while
41+
remaining backwards compatible.
42+
* Supports ragel >= 6.0 now.
43+
* Corrected some tests.
44+
* Some minor changes.
45+
2007-11-27 (1.1.2)
46+
* Remember default dir (last used directory) in editor.
47+
* JSON::Editor.edit method added, the editor can now receive json texts from
48+
the clipboard via C-v.
49+
* Load json texts from an URL pasted via middle button press.
50+
* Added :create_additions option to Parser. This makes it possible to disable
51+
the creation of additions by force, in order to treat json texts as data
52+
while having additions loaded.
53+
* Jacob Maine <[email protected]> reported, that JSON(:foo) outputs a JSON
54+
object if the rails addition is enabled, which is wrong. It now outputs a
55+
JSON string "foo" instead, like suggested by Jacob Maine.
56+
* Discovered a bug in the Ruby Bugs Tracker on rubyforge, that was reported
57+
by John Evans [email protected]. He could produce a crash in the JSON
58+
generator by returning something other than a String instance from a
59+
to_json method. I now guard against this by doing a rather crude type
60+
check, which raises an exception instead of crashing.
61+
2007-07-06 (1.1.1)
62+
* Yui NARUSE <[email protected]> sent some patches to fix tests for Ruby
63+
1.9. I applied them and adapted some of them a bit to run both on 1.8 and
64+
1.9.
65+
* Introduced a JSON.parse! method without depth checking for people who like
66+
danger.
67+
* Made generate and pretty_generate methods configurable by an options hash.
68+
* Added :allow_nan option to parser and generator in order to handle NaN,
69+
Infinity, and -Infinity correctly - if requested. Floats, which aren't numbers,
70+
aren't valid JSON according to RFC4627, so by default an exception will be
71+
raised if any of these symbols are encountered. Thanks to Andrea Censi
72+
<[email protected]> for his hint about this.
73+
* Fixed some more tests for Ruby 1.9.
74+
* Implemented dump/load interface of Marshal as suggested in ruby-core:11405
75+
by murphy <[email protected]>.
76+
* Implemented the max_nesting feature for generate methods, too.
77+
* Added some implementations for ruby core's custom objects for
78+
serialisation/deserialisation purposes.
79+
2007-05-21 (1.1.0)
80+
* Implemented max_nesting feature for parser to avoid stack overflows for
81+
data from untrusted sources. If you trust the source, you can disable it
82+
with the option max_nesting => false.
83+
* Piers Cawley <[email protected]> reported a bug, that not every
84+
character can be escaped by ?\ as required by RFC4627. There's a
85+
contradiction between David Crockford's JSON checker test vectors (in
86+
tests/fixtures) and RFC4627, though. I decided to stick to the RFC, because
87+
the JSON checker seems to be a bit older than the RFC.
88+
* Extended license to Ruby License, which includes the GPL.
89+
* Added keyboard shortcuts, and 'Open location' menu item to edit_json.rb.
90+
2007-05-09 (1.0.4)
91+
* Applied a patch from Yui NARUSE <[email protected]> to make JSON compile
92+
under Ruby 1.9. Thank you very much for mailing it to me!
93+
* Made binary variants of JSON fail early, instead of falling back to the
94+
pure version. This should avoid overshadowing of eventual problems while
95+
loading of the binary.
96+
2007-03-24 (1.0.3)
97+
* Improved performance of pure variant a bit.
98+
* The ext variant of this release supports the mswin32 platform. Ugh!
99+
2007-03-24 (1.0.2)
100+
* Ext Parser didn't parse 0e0 correctly into 0.0: Fixed!
101+
2007-03-24 (1.0.1)
102+
* Forgot some object files in the build dir. I really like that - not!
103+
2007-03-24 (1.0.0)
104+
* Added C implementations for the JSON generator and a ragel based JSON
105+
parser in C.
106+
* Much more tests, especially fixtures from json.org.
107+
* Further improved conformance to RFC4627.
108+
2007-02-09 (0.4.3)
109+
* Conform more to RFC4627 for JSON: This means JSON strings
110+
now always must contain exactly one object "{ ... }" or array "[ ... ]" in
111+
order to be parsed without raising an exception. The definition of what
112+
constitutes a whitespace is narrower in JSON than in Ruby ([ \t\r\n]), and
113+
there are differences in floats and integers (no octals or hexadecimals) as
114+
well.
115+
* Added aliases generate and pretty_generate of unparse and pretty_unparse.
116+
* Fixed a test case.
117+
* Catch an Iconv::InvalidEncoding exception, that seems to occur on some Sun
118+
boxes with SunOS 5.8, if iconv doesn't support utf16 conversions. This was
119+
reported by Andrew R Jackson <[email protected]>, thanks a bunch!
120+
2006-08-25 (0.4.2)
121+
* Fixed a bug in handling solidi (/-characters), that was reported by
122+
Kevin Gilpin <[email protected]>.
123+
2006-02-06 (0.4.1)
124+
* Fixed a bug related to escaping with backslashes. Thanks for the report go
125+
to Florian Munz <[email protected]>.
126+
2005-09-23 (0.4.0)
127+
* Initial Rubyforge Version

‎COPYING

+58
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
Ruby is copyrighted free software by Yukihiro Matsumoto <[email protected]>.
2+
You can redistribute it and/or modify it under either the terms of the GPL
3+
(see GPL file), or the conditions below:
4+
5+
1. You may make and give away verbatim copies of the source form of the
6+
software without restriction, provided that you duplicate all of the
7+
original copyright notices and associated disclaimers.
8+
9+
2. You may modify your copy of the software in any way, provided that
10+
you do at least ONE of the following:
11+
12+
a) place your modifications in the Public Domain or otherwise
13+
make them Freely Available, such as by posting said
14+
modifications to Usenet or an equivalent medium, or by allowing
15+
the author to include your modifications in the software.
16+
17+
b) use the modified software only within your corporation or
18+
organization.
19+
20+
c) rename any non-standard executables so the names do not conflict
21+
with standard executables, which must also be provided.
22+
23+
d) make other distribution arrangements with the author.
24+
25+
3. You may distribute the software in object code or executable
26+
form, provided that you do at least ONE of the following:
27+
28+
a) distribute the executables and library files of the software,
29+
together with instructions (in the manual page or equivalent)
30+
on where to get the original distribution.
31+
32+
b) accompany the distribution with the machine-readable source of
33+
the software.
34+
35+
c) give non-standard executables non-standard names, with
36+
instructions on where to get the original software distribution.
37+
38+
d) make other distribution arrangements with the author.
39+
40+
4. You may modify and include the part of the software into any other
41+
software (possibly commercial). But some files in the distribution
42+
are not written by the author, so that they are not under this terms.
43+
44+
They are gc.c(partly), utils.c(partly), regex.[ch], st.[ch] and some
45+
files under the ./missing directory. See each file for the copying
46+
condition.
47+
48+
5. The scripts and library files supplied as input to or produced as
49+
output from the software do not automatically fall under the
50+
copyright of the software, but belong to whomever generated them,
51+
and may be sold commercially, and may be aggregated with this
52+
software.
53+
54+
6. THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
55+
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
56+
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
57+
PURPOSE.
58+

0 commit comments

Comments
 (0)