Use Collection instead of List

[GoogleCodeExporter]

If you change

JSONValue:150, 151, 205 and 206 to java.util.Collection instead of 
java.util.List
and
JSONArray:32 and 72 (method definitions) to Collection instead of List

it'll work with other types of collections (such as Set) too!

Original issue reported on code.google.com by teh.e...@gmail.com on 20 May 2010 at 7:55

[GoogleCodeExporter]

Original comment by fangyid...@gmail.com on 20 May 2010 at 11:56

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Use Itrable instead of Collection in same lines.

Original comment by dmitry.s...@gmail.com on 24 May 2010 at 8:43

[GoogleCodeExporter]

I don't think that would be a good idea. If you look at the type hierarchy of 
Iterable, there are several other 
Iterable objects/interfaces, which are not for the purpose of holding a list 
(which is what we want here). It would 
suggest that json-simple is capable of handling any type of iterable object, 
while it only makes sense putting a 
collection in it.
Narrowing it down to List is too narrowed, to Iterable is too wide.

Original comment by teh.e...@gmail.com on 24 May 2010 at 8:50

[GoogleCodeExporter]

Yes I agree with teh's point.

Original comment by fangyid...@gmail.com on 24 May 2010 at 10:04

[GoogleCodeExporter]

Hi,

   I reported your issue on my github JSON-SIMPLE tree[1] to keep track of your request.

Bye
Piero
[1]https://github.com/ottuzzi/JSON-SIMPLE/issues/4

Original comment by ottu...@gmail.com on 24 Aug 2011 at 2:02

[GoogleCodeExporter]

>Narrowing it down to List is too narrowed, to Iterable is too wide.
So what is the reason List is not replaced with Collection as it was originally 
proposed?

I'd like to serialize Set without hassle.

Original comment by ats...@gmail.com on 26 Feb 2013 at 3:25

[GoogleCodeExporter]

Done in r210.

Original comment by jon.cham...@gmail.com on 10 Aug 2013 at 1:45

• Changed state: Fixed