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
On Fri, Aug 30, 2019 at 5:16 AM Michael Van Canneyt
wrote:
> The shootout benchmarks for example are dismally coded for FPC with as a
> result that they perform badly.
>
Not all of them! At least, not anymore:
https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/binarytrees.h
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
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 problem with the compiler.
Michael,
I am on Linux as well, but I
I'd recommend that you also list what license each is licensed under, as
that can be an extremely large deciding factor in whether or not a given
implementation can even be considered.
Alan
On Fri, Aug 30, 2019 at 1:19 AM Anthony Walter wrote:
> I've posted a new page that tests the speed and c
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
On Fri, 30 Aug 2019, Anthony Walter wrote:
I've posted a new page that tests the speed and correctness of several
pascal based JSON parsers.
https://www.getlazarus.org/json/tests/
In full disclosure I am the author of the new open source JsonTools
library, and even though my parser seems to
>
> D'Oh.
>
Thanks. The links were swapped and now have been fixed. Nice find.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Hello,
Le 30/08/2019 à 10:18, Anthony Walter a écrit :
I've posted a new page that tests the speed and correctness of several
pascal based JSON parsers.
https://www.getlazarus.org/json/tests/
it seems you made a typo in your html,
JsonTools points to https://sourceforge.net/projects/lkjson/
I've posted a new page that tests the speed and correctness of several
pascal based JSON parsers.
https://www.getlazarus.org/json/tests/
In full disclosure I am the author of the new open source JsonTools
library, and even though my parser seems to a big improvement over the
other alternatives, m
12 matches
Mail list logo
