On Sat, 31 Aug 2019, Anthony Walter wrote:
Ben,
After this hurricane Dorian situation is over (I live in Cape Canaveral
Florida), I will be adding many parsers to the original test page I linked
at the top of this thread. I will be revising the numbers and charts,
adding more notes per this t
Ben,
After this hurricane Dorian situation is over (I live in Cape Canaveral
Florida), I will be adding many parsers to the original test page I linked
at the top of this thread. I will be revising the numbers and charts,
adding more notes per this thread and some more which I feel are notable,
an
On Sat, Aug 31, 2019 at 9:40 AM Anthony Walter wrote:
> > Could you include https://github.com/BeRo1985/pasjson in the comparison?
>
> Sure. I also have a few other people have requested. I will also list the
> license of each in the first table.
>
Note that I'm not sure if it's FPC-compatible,
On Sat, 31 Aug 2019, Anthony Walter wrote:
Could you include https://github.com/BeRo1985/pasjson in the comparison?
Sure. I also have a few other people have requested. I will also list the
license of each in the first table.
[snip]
For example if wanted to store object state using RTTI
> Could you include https://github.com/BeRo1985/pasjson in the comparison?
Sure. I also have a few other people have requested. I will also list the
license of each in the first table.
Regarding a huge gigabytes of JSON in a file, I know a small portion of
programmers of people might be inclined
On Fri, 30 Aug 2019, Anthony Walter via lazarus wrote:
Okay, so I turned on my Windows VM with a different version of FPC and ran
VerifyUnicodeChars with both FPJson and JsonTools. The resutls are the
same. JsonTools sees the unicode correctly, and something is wrong when
using FPJson. I don't
Okay, so I turned on my Windows VM with a different version of FPC and ran
VerifyUnicodeChars with both FPJson and JsonTools. The resutls are the
same. JsonTools sees the unicode correctly, and something is wrong when
using FPJson. I don't know what the problem is, but other people are
noticing sim
For those tracking the unicode issue, could you please verify the problem
does not present in my JsonTools library on compiler revisions and
platforms? I always get true (passed) with my library, but not with any
other library. Here is the relevant test:
function VerifyUnicodeChars: Boolean;
const
On Fri, 30 Aug 2019, Anthony Walter via lazarus wrote:
Alan, oh that's a good idea. I will do that as well as add a few more
parser libraries as requested by a few people in other non mailing lists
threads. I will also try to find out what's going on the unicode strings as
it might be a proble
On Fri, 30 Aug 2019, Anthony Walter via lazarus wrote:
With regards to duplicate key names, some libraries allow for the same key
to be parsed resulting in multiple child nodes of the same name. Others
throw an exception when parsing an object with a duplicate key name.
The correct way to han
10 matches
Mail list logo
