Thanks!
/M
On Thu, Apr 22, 2021 at 2:23 PM Martin Nilsson (Coppermist) @ Pike (-)
developers forum <10...@lyskom.lysator.liu.se> wrote:
> I've fixed that. Looks like the behaviour of adding an array to 0 is
> no longer working.
>
Hi folks,
With recent Pikes, I get the following SSL/TLS error on multiple platforms:
> Protocols.HTTP.get_url;
[warnings*]
> Protocols.HTTP.get_url("https://example.com;);
Bad argument 0 to `+(). Expected array.
Unknown program: `+(0,({"chambersignr...@chambersign.org"}))
Reproduced with the current HEAD of master on both macOS and Linux. For
example,
$ pike -e 'Protocols.HTTP.get_url'
produces an error log very similar to Stephen's, ending:
bld/pike/8.1.13/lib/modules/Standards.pmod/URI.pike:653:Illegal program
identifier: 0.
Thanks!
On Tue, Jul 7, 2020 at 5:00 AM Henrik Grubbström (Lysator) @ Pike (-)
developers forum <10...@lyskom.lysator.liu.se> wrote:
>
> > Hi folks,
>
> Hi Marc.
>
> It took some time, but...
>
> > It looks like operator assignment (op=), increment and decrement
> > statements aren't subjected to
On Thu, May 28, 2020 at 8:48 AM Marcus Comstedt (ACROSS) (Hail
Ilpalazzo!) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se>
wrote:
>
> >Also, GL is deprecated as of 10.14,
>
> Hm? They can't seriously expect people to use Vulcan or some crap
> like that, can they?
"Metal", apparently:
On Wed, Apr 29, 2020 at 2:03 PM Marc Simpson wrote:
>
> Hi all,
>
> FYI, it looks like master no longer builds on macOS due to the MTU
> additions in [44f12ac]:
Fixed in [5ba8545]; thanks Grubba.
Hi all,
FYI, it looks like master no longer builds on macOS due to the MTU
additions in [44f12ac]:
.../src/modules/_Stdio/file.c:5526:16: error: use of undeclared
identifier 'IP_MTU'
int option = IP_MTU;
.../src/modules/_Stdio/file.c:5541:14: error: use of undeclared
identifier 'IPV6_MTU'
On Tue, Apr 28, 2020 at 12:20 PM Chris Angelico wrote:
>
> On Wed, Apr 29, 2020 at 5:13 AM Marc Simpson wrote:
> > [...]
> >
> > It seems that I can reliably segfault recent Pike 8.1 installs when
> > using sprintf-style SQLite queries: [...]
>
> Reproduced
Hi folks,
It seems that I can reliably segfault recent Pike 8.1 installs when
using sprintf-style SQLite queries:
$ echo '
create table demo(a, b);
insert into demo(a, b) values(1, "abc")' | sqlite3 demo.db
$ pike
Pike v8.1 release 13 running Hilfe v3.5 [...]
>
Bumping the following message from 2018; just built the latest HEAD
and this still seems to be an issue (assuming it's considered a bug).
Best,
Marc
On Mon, Mar 26, 2018 at 5:36 PM Marc Simpson wrote:
>
> Hi folks,
>
> It looks like operator assignment (op=), increment a
Bumping this—I believe the behaviour is unchanged in HEAD.
On Wed, Mar 28, 2018 at 5:30 PM Martin Nilsson (Coppermist) @ Pike (-)
developers forum <10...@lyskom.lysator.liu.se> wrote:
> Looks like a bug to me. I think these should all give the same
> warnings.
>
Hi folks,
It looks like operator assignment (op=), increment and decrement
statements aren't subjected to the same typechecks as their more
explicit equivalents.
For example, neither the post-increment nor += statements below warn
with strict_types enabled, even though they assign values outside
12 matches
Mail list logo
