Hi Ched,
I run nightly testsuite on a raspberry PiB,
and I did not see anything like that.
Would it be possible for you to send here a simple source file that
shows this behavior together with an explicit command line
for the compilation, to be sure of the precise options you are using:
To
On 3/05/20 10:28 pm, Michael Van Canneyt wrote:
On Sun, 3 May 2020, Noel Duffy via fpc-pascal wrote:
On Sun, 3 May 2020 09:57:46 +0200 (CEST) Michael Van Canneyt
wrote:
Yes, please open a bug report. If you attach a small console test
program that
demonstrates the bug (and subsequently th
On Wed, May 6, 2020 at 12:19 PM Noel Duffy via fpc-pascal <
fpc-pascal@lists.freepascal.org> wrote:
> So I guess the question is, is it worth the effort to make
> StrToHostAddr6 RFC4291 compliant? Is that something the FPC team would
> want, or do they just not use the sockets unit?
>
There have
Hi,
On Wed, 6 May 2020, Noel Duffy via fpc-pascal wrote:
> Testing would also have to be fairly rigorous to make sure all the
> different formats are handled correctly. I've already done some work to
> make it easy to compare StrToHostAddr6's output to that of inet_pton in
> the C library, so th
On Wed, May 6, 2020 at 8:03 AM Sven Barth via fpc-pascal
wrote:
> Not in the makefile.fpc,
That is unfortunate.
> but fpcmake allows you to pass a list of supported targets (usually -Tall is
> used to allow all targets), but you'd need to pick each one. This does mean
> however that everyone
Working on the language server it's become clear that JSON is going to be a
killer bottleneck, but that's what Microsoft decided to use. It's almost a deal
breaker just because of the sheer size of the data due to JSON's verbose plain
text formatting.
I've seen there is such thing as BSON (http
