Pike Meet-up 2024-Q2

Hi. At Pike Conference 2017 it was decided that we ought to hold a more informal meeting in Linköping ~ once every quarter. As the 6 month mark from the latest conference is coming up soon, it seems time to announce the second such meeting for 2024: Pike Meet-up 2024-Q2 Date:

File descriptor usage in Protocols.HTTP.Server.SSLPort

Hi Chris. > I've run into a strangeness with my TLS-based web server. It seems > that, for every incoming request, three file descriptors are used > (they all seem to be sockets), and they aren't immediately cleaned up. > > With keep-alive disabled, they CAN be disposed of, but it takes an >

Pure Pike annotations?

> (Side note: This mailing list seems very dead lately. Is the LysKOM > gateway down?) I believe that it is up. > I'm trying to make good use of annotations, but all the existing ones > are in cmod files, and I'm trying to work out how best to write them > in Pike. My goal is to have an

Re: pike docker images

> Hi. > > At Pike Conference 2017 it was decided that we ought to hold a > more informal meeting in Linköping ~ once every quarter. As the > 3 month mark from the latest conference is coming up soon, > it seems time to announce the first such meeting for 2024: > > Pike Meet-up 2024-Q1 >

Re: pike docker images

>> Place: Roxen IS AB >> S:t Larsgatan 22A > > I expect you mean Storgatan 46? Right...

Re: pike docker images

Hi. At Pike Conference 2017 it was decided that we ought to hold a more informal meeting in Linköping ~ once every quarter. As the 3 month mark from the latest conference is coming up soon, it seems time to announce the first such meeting for 2024: Pike Meet-up 2024-Q1 Date:

SHA256/SHA512 crypt_hash bug

> Hello, Hi Ricard. > I have been looking into using the SHA256/SHA512 crypt_hash > functions, and during my testing, comparing the results with other > implementations (Python's passlib, Openssl, MySQL and C), I found > that for some passwords used, the resulting hash is different that > the

gethrvtime() overflow on netbsd

> Hello all, Hi Bill. > Basically, the elapsed time is calculated as final_time - start_time as > returned by gethrvtime(), and it appears that on netbsd, there's (I'm > assuming) an overflow that causes the elapsed time to become negative. > It happens often enough that the total amount of

Pike 9.0 quirk with implicit lambda

Hi Chris. > In Pike 8 (tested on 8.1.15), the implicit lambda correctly receives > its __ARGS__, and will happily provide those as closure variables. In > Pike 9 (tested with current master, 235eb5), the inner function > somehow causes __ARGS__ to be 0 instead of an array. > > Any ideas as to

No Gz module on Debian 12

There have however been quite a few alphas released since then (ie Pike 8.0.1760 and later): 8.0.1760 8.0.1772 8.0.1784 8.0.1796 8.0.1808 8.0.1820 8.0.1832 8.0.1844 8.0.1762 8.0.1774 8.0.1786 8.0.1798 8.0.1810 8.0.1822 8.0.1834 8.0.1846 8.0.1764 8.0.1776 8.0.1788 8.0.1800

rntcl

rntcl is still used.

Pike Meet-up 2023-Q2

Hi. At Pike Conference 2017 it was decided that we ought to hold a more informal meeting in Linköping ~ once every quarter. As the 6 month mark from the latest conference is coming up soon, it seems time to announce the second such meeting for 2023: Pike Meet-up 2023-Q2 Date:

Pike Meet-up 2023-Q1

Hi. At Pike Conference 2017 it was decided that we ought to hold a more informal meeting in Linköping ~ once every quarter. As the 3 month mark from the latest conference is coming up soon, it seems time to announce the first such meeting for 2023: Pike Meet-up 2023-Q1 Date:

Segfault from Pike 8.1 - possible type check issue?

> float thing_sum(array(string) things) { > return `+(@(array(float))things) + 1.0; > } I can't reproduce the issue with a current Pike 8.1, but there have been lots of fixes to the type checker the last few months. /grubba

Pike Meet-up 2022-Q3

Hi. At Pike Conference 2017 it was decided that we ought to hold a more informal meeting in Linköping ~ once every quarter. As the 33 month mark from the latest conference is coming up soon, it seems time to announce the second such meeting for 2022: Pike Meet-up 2022-Q3 Date:

Pike Meet-up 2022-Q2

Hi. At Pike Conference 2017 it was decided that we ought to hold a more informal meeting in Linköping ~ once every quarter. As the 36 month mark from the latest conference is coming up soon, it seems time to announce the first such meeting for 2022: Pike Meet-up 2022-Q2 Date:

Pike 8.0.1738 ready to release

> But please fix the permissions on the directory so that it is possible > to upload additional platforms: > > rin:/space/ftp/pub/pike/all/8.0.1738% ls -ld . > drwxr-sr-x 2 1044 pike 10 Feb 20 23:11 . > rin:/space/ftp/pub/pike/all/8.0.1738% > > (should be writable for pike group)

Pike 8.0 beta 8.0.1738

> Hello all- Hi Bill. > I’ve prepared a new 8.0 beta release and have uploaded it to: > > http://pike.lysator.liu.se/pub/pike/beta/8.0.1738/Pike-v8.0.1738.tar.gz There's now a corresponding ebuild for Gentoo in the Pike overlay. > Thanks in advance! Thanks for making the effort!

Bug in ccm glue?

It has its own implementation of CCM.

Bug in ccm glue?

Thanks, fixed in Pike 8.0 and master.

compile of pike under chroot failing

> hi Hi. > i'm currently building rpms of pike 8.0 for fedora35 and have troubles to > "install" the binaries. > > my setup: mock (chroot environment for building rpms). inside of that > environment there are several steps, mainly extract source-files, > prepare, compile, install and collect

Pike Meet-up 2021-Q4

Hi. At Pike Conference 2017 it was decided that we ought to hold a more informal meeting in Linköping ~ once every quarter. As the 24 month mark from the latest conference is coming up soon, it seems time to announce the first such meeting for 2021: Pike Meet-up 2021-Q4 Date:

What are the consequences of adding a subtype?

> Currently functions have two subtypes: normal ones (0) and builtin > functions (USHRT_MAX). What would be the implications of adding two > more? Not quite correct; normal ones are 0..USHRT_MAX-1 and builtin functions are USHRT_MAX. The subtype is used to select the function entry in the

Recursive Pike_error calls

> Any suggestions on how I can find out in this coredump where the > original exception was? (i.e. which pike file and linenumber point > at the spot where we tried to access the variable in the destructed object). You didn't get a backtrace from debug_va_fatal()? As far as I can see, the

Did someone already try to ask someone at Lysator?

Hi Stephen! > Did someone already try to ask someone at Lysator to push the power button? The power button wasn't the problem... The problem was due to the zpool version being bumped to a version not supported by the version of GRUB on the bootdisks (Illumos bug 12780). That the hardware

Possible over-optimization with 'continue return'

> Playing around with generators, and have come across a strange oddity. > This code works fine: [...] > But remove any of the 'if' guards, and the function terminates prematurely. > > continue int gen(int x) > { > if (x == 1) continue return 1; > continue return 2; > if (x == 1) continue

Pike 8.0.1116 (release)

> Great work Bill! > > > Please feel free to upload binaries; > > I'd love to, but it looks like the /space/ftp/pub/pike/all/8.0.1116/ > directory is not writable to the pike group? (Maybe check your > umask?) Better now?

8.0.1116 tarball

> All- Hi Bill; merry X-mas. > I've discovered that the source tarball contains a handful of extraneous > files: a pair of droppings from patch as well as a pair of temporary > files my text editor seems to have made (but which I can't find outside > the archive). There's nothing of any note

Pike 8.0.1116 (release)

Hi Bill, Merry X-mas! > I ve cut a new version of Pike 8.0 that includes the missing change > log entry as well as a minor fix that hopefully fixes a compile > error in the latest version of macOS. The builds all look good so > I m going to declare this an official stable release. Please feel >

Pike 8.0.1116 (release)

8.0 test suite failures: Critbit on illumos

Hi Bill. > I m running builds of 8.0 to make sure we don t have any major test > failures, and I ve run into a few problems so far. I ll put them in > separate emails so they are more manageable. If anyone can offer any > assistance, that would be most appreciated. I can supply any info > needed,

Thinking about annotations

Bill writes: > I’ve been away from the keyboard for a few months and am slowly > getting back to work and I thought I’d celebrate by taking a closer > look at the new annotation support that Grubba has put together. My > plan is to have a “chapter” of material for a future edition of the

Pikefarm hang

Hi. For Pikefarm participants information: Pikefarm build 5559 of Pike master seems to hang spending 100% CPU during the testsuite, and may need to be killed by hand. Sorry for the inconvenience. /grubba

Re: Segmentation fault cause

> Tobias S. Josefowitz @ Pike developers forum wrote: > >>I can now confirm that I've been running three hours with io->this = 0 at > >>destruct, and there have not been any coredumps yet. Seems promising. > > Four hours now, no coredump. Statistically relatively strong evidence. > > >I'm

Operator assignment and strict_types

> Hi folks, Hi Marc. It took some time, but... > It looks like operator assignment (op=), increment and decrement > statements aren't subjected to the same typechecks as their more > explicit equivalents. Correct. > For example, neither the post-increment nor += statements below warn > with

an automap bug

> Reproduces both on pike 8 from apt repository and pike compiled on master: > $ ./pike -v > Pike v8.1 release 13 Copyright © 1994-2018 Linköping University > Pike comes with ABSOLUTELY NO WARRANTY; This is free software and you are > welcome to redistribute it under certain conditions; read the

Re: Segmentation fault cause

>I think I found it. > >commit be8d0c60fcd3bb8615740d55ba300460c9062679 (HEAD -> master) >Author: Stephen R. van den Berg >Date: Mon Jul 6 00:13:44 2020 +0200 > >Stdio.Buffer: Put null in a freed io->output.u.object. > > src/modules/_Stdio/buffer.cmod | 4 +++- > 1 file changed, 3

Re: Segmentation fault cause

>This was when compiled with -g -O2 and no RTL_DEBUG. >I have a coredump factory now. > >[New LWP 9071] >[New LWP 9048] >[New LWP 5670] >[Thread debugging using libthread_db enabled] >Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". >Core was generated by

Pike-bot

Hi The githelper instance on pike-git.lysator.liu.se has been extended to know about the gitlab issue tracker at git.lysator.liu.se. It can set and remove some labels on issues, and also close issues. The policies are relatively straight forward: * The Stalled label is always cleared. *

Re: Crypto.Password and Blowfish

> Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote: > >> Has anyone attempted to add support for Blowfish encryption to > >> Crypto.Password? > >> I have some $2y$... prefixed passwords (interfacing with the PHP > >> password_verify()) w

Crypto.Password and Blowfish

> Has anyone attempted to add support for Blowfish encryption to > Crypto.Password? > I have some $2y$... prefixed passwords (interfacing with the PHP > password_verify()) which I need to verify. I've looked into it briefly. As I recall, you need access to some low-level functions that AFAIK

Issue tracker

Hi again. > At the 2020-Q1 meet-up we decided to use the GitLab issue tracker > at https://git.lysator.liu.se/pikelang/pike/ for Pike. > > Issue numbers were reserved as follows: > > * 1 - 7999 Bugzilla bugs ([Bug ]). > * 8000 - YouTrack issues ([PIKE-]). > *

Issue tracker

Hi. At the 2020-Q1 meet-up we decided to use the GitLab issue tracker at https://git.lysator.liu.se/pikelang/pike/ for Pike. Issue numbers were reserved as follows: * 1 - 7999Bugzilla bugs ([Bug ]). * 8000 - YouTrack issues ([PIKE-]). * 1 -

Pike Meet-up 2020-Q1

Hi. At Pike Conference 2017 it was decided that we ought to hold a more informal meeting in Linköping ~ once every quarter. As the three month mark from the latest conference is coming up soon, it seems time to announce the first such meeting for 2020: Pike Meet-up 2020-Q1 Date:

Re: Immediate call_out takes 2ms

> 8.0.702 on macOS 10.14.6 : > > Pike bertrand$ for i in `seq 10`; do ./test_callout.pike; done > took 0.006 ms > took 0.007 ms > took 0.006 ms > took 0.006 ms > took 0.006 ms > took 0.006 ms > took 0.006 ms > took 0.005 ms > took 0.006 ms > took 0.006 ms The default backend in MacOS X uses

Immediate call_out takes 2ms

Fixed in Pike 8.0 and master.

Immediate call_out takes 2ms

>> Hi. >> In Pike 7.8 calling call_out takes 0.002 ms. In Ubuntu's Pike v8.0 >>release 498 and in Opera's v8.0 release 610 it takes 2ms. Test program: > >Seems to be a relative direct consequence of >7e8de5246b3012b055756293f2332494216646fd. /me scratches head. It seems there are

Crypto.MAC segmentation fault?

> FYI: > > $ pike > Pike v8.1 release 13 running Hilfe v3.5 (Incremental Pike Frontend) > > object x = Crypto.MAC()->State("secretp"); > Segmentation fault > > It might be abuse of the API (I was trying to find an incantation to > create a secret to be used for JWT generation), but a segfault

Comments/thoughts requested: Generators and async functions in Pike

> Pike now (8.1) has a decent promise/future subsystem. It's always had > great handling of multiple asynchronous operations (GUI, socket, time > delay, etc) with the convenience of just returning -1 from main. > Interested in people's opinions on whether it would be of value to > introduce

Pike Meet-up 2019-Q3

A reminder about the Pike Meet-up 2019-Q3 on Sunday. > At Pike Conference 2017 it was decided that we ought to hold a > more informal meeting in Linköping ~ once every quarter. As the > nine month mark from the latest conference is coming up soon, > it seems time to announce the third such

Pike Meet-up 2019-Q3

>Hi. [...] > Pike Meet-up 2019-Q3 > Date: 2018-08-04 (Sun) Oops, should be 2019-08-04. /grubba

Pike Meet-up 2019-Q3

Hi. At Pike Conference 2017 it was decided that we ought to hold a more informal meeting in Linköping ~ once every quarter. As the nine month mark from the latest conference is coming up soon, it seems time to announce the third such meeting for 2019: Pike Meet-up 2019-Q3 Date:

Example how to use Protocols.HTTP2 ?

> Does anyone have any sample code that demonstrates how to use > Protocols.HTTP2 ? That module is work in (stalled) progress. /grubba

Re: set_read_callback()

> Stephen R. van den Berg wrote: > >The freeing of the C-struct needs to be delayed until all references to > >the callback function are gone (which probably implies that I need to > >turn the struct over to the garbage collector, which implies that it > >needs to be an svalue, I presume). If

Re: SEGFAULT in Pike 8.1

Stephen R. van den Berg wrote: > >Henrik Grubbström (Lysator) @ Pike (-) developers forum wrote: > >>Now please fix the testsuite falures caused by the Stdio.FakePipe changes. > > >I'll run through them. > > Fixed. There are still some failures that are triggered: | Doing tests in

Re: SEGFAULT in Pike 8.1

> >Looks like something has set Pike_compiler->new_program to NULL. > > >New attempt at fixing committed. > > $ pike -e "foo::bar = 1;" > -:2:No inherit or surrounding class foo. > Compilation failed. > > Cheers! Great. Now please fix the testsuite falures caused by the Stdio.FakePipe changes.

Re: SEGFAULT in Pike 8.1

> Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote: > >Thanks. Potentially fixed. > > Sorry, whack-a-mole, I guess. The bug shifted, maybe it's more obvious now > (you check for inh > 0, does that even work for pointers? Maybe that > should be inh != 0 in

Re: SEGFAULT in Pike 8.1

Stephen R. van den Berg wrote: >Program received signal SIGSEGV, Segmentation fault. >0x5561c6b5 in find_inherited_identifier (inherit_state=0x557e7140, >inherit_depth=0, inh=1, ident=0x5590a308) >at /var/src/roxen/81pike/src/program.c:2304 >2304 return

Re: SEGFAULT in Pike 8.1

Stephen R. van den Berg wrote: > >>Please provide a full example. > > Shortest example so far: > > $ pike -e "foo::bar = 1;" > -:2:No inherit or surrounding class foo. > Segmentation fault I can't reproduce the crash: | $ ./pike -e "foo::bar = 1;" | -:2:No inherit or surrounding class foo. |

SEGFAULT in Pike 8.1

> When I run the following in Pike 8.1, it SEGFAULTs: > > foo::bar = 1; > > Gets me: > p.pike:4:No inherit or surrounding class foo. > Segmentation fault Please provide a full example. /grubba

Scope runtime bug in Pike 8.0 and 8.1

> This gives a runtime error which seems incorrect to me. > Flipping the #if causes it to run flawlessly. > Is this a problem in Pike, or are my expectations too high? This is expected (and correct) behavior, the `->() operator performs "external" indexing. In this case you may want to use the

SSL decoding error regression in Pike 8.1 (works in Pike 8.0)

> The test program below shows an I/O error for Pike 8.1, and it shows [...] Seems to be due to an incompatibility in the implementation of Curve25519. Try disabling Curve25519 for now (by eg disable it in the mapping ECC_CURVES in SSL.pmod/Constants.pmod). /grubba

Pike Meet-up 2019-Q2

Hi. A reminder about Pike Meet-up 2019-Q2 tomorrow. > Pike Meet-up 2019-Q2 > Date: 2018-05-04 (Sat) > Time: 10:00 - afternoon/evening > Place: Roxen IS AB > S:t Larsgatan 22A > Linköping /grubba

Re: Pike Meet-up 2019-Q2

> If moving the meeting to May 11th turns out to be impossible, would it be > ok if I dropped by the Roxen office between 13th and 17th afternoon to ask > some questions regarding the debugger? Sure. I'll be at the Roxen office the 13th, 15th and 17th. /grubba

Re: Pike Meet-up 2019-Q2

>Any chance it might be moved to 11th May? Sure, I don't have any problem with either date. What do others say? >śr., 17 kwi 2019 o 11:53 Henrik Grubbström (Lysator) @ Pike (-) developers >forum <10...@lyskom.lysator.liu.se> napisał(a): > >> Hi. >> >> At Pike Conference 2017 it was decided

Pike Meet-up 2019-Q2

Hi. At Pike Conference 2017 it was decided that we ought to hold a more informal meeting in Linköping ~ once every quarter. As the six month mark from the latest conference is coming up soon, it seems time to announce the second such meeting for 2019: Pike Meet-up 2019-Q2 Date:

Interaction between automap and argument splicing segfaults

> The crash is on this line: [...] > If pike is built with PIKE_DEBUG, you get this fatal instead: [...] > So the crash is in the compiler proper, not in the execution of the > program. Thanks for the report, test case and investigation. Fixed the code generator in Pike 8.0 and master.

Debugger, Debug Adapter Protocol, Annotations

> Hey Grubba! Hi. > Thanks for a great and fruitful meetup. I've learned a lot of things there. > I'm also really glad that we move the debugger development on. Wouldn't > have done it without you. [...] > Also,would you be able to share the local variable lookup feature so I can > move on with

Re: Debugger, Debug Adapter Protocol, Annotations

Hi Mateusz. >Regarding the annotations - I seem to have lost my notes from the meetup, >and have some questions: >I've managed to play around the @Implements annotation and it seems to work >alright. > >Can you remind me what does the @constant annotation do? @constant is a "fake" annotation

Pike Meet-up 2019-Q1

Hi. At Pike Conference 2017 it was decided that we ought to hold a more informal meeting in Linköping ~ once every quarter. As the three month mark from the latest conference is coming up soon, it seems time to announce the first such meeting for 2019: Pike Meet-up 2019-Q1 Date:

Re: QuickType support

Hi. >I came to the point where I spent so much time on providing Pike support >for QuickType, that I'd probably manage to manually write DAP and LSP pmods >by now. So I've decided to stop there and deliver it as-is. Despite the >generated code's likely poor performance, it's been thoroughly

Re: debugger, status and suggestions sought

Hi. >I think having both LSP > and DAP > implementations for >Pike would be awsome, but I feel that this discussion is getting further >away from it's main point. We've been talking about

Re: line number storage and included files

Better now?

Should atexit really store a weak reference?

>The atexit() function internally stores the exit handlers in >"atexit_functions" (see src/signal_handler.c). For some reason I >don't understand, f_atexit() includes this line: > > atexit_functions->flags |= ARRAY_WEAK_FLAG; Hmm... Yes, that's probably not a good idea. >This means that if you

Re: line number storage and included files

>Hi Grubba… > > I’m using 8.1 freshly compiled from master. The results of cpp() > look good, but when I throw an error the file name is incorrect (it > shows the line number of the included file, but the filename of the > file that contains the #include directive.) > > Example (note the file

line number storage and included files

> Hi all, Hi Bill. > I’ve been looking at the linenumbers element in struct program as a > means of getting offsets for a given line number. Since a program > can be made up of multiple files through includes, I need to make > sure that when I look through the entries, that I’m only

Pike conference 2018

>Hi, Hi Tobi. >we invite you to this year's Pike developer conference on the weekend >of the 3rd and 4th of November 2018. > >Opera Software will host the conference in its offices in Linköping. And following tradition, Roxen invites to afternoon fika on the preceeding day (November 2nd). This

wrong exit code of extract_autodoc on errors

>I think extract_autodoc should exit with a non-0 exitcode whenever it >produces an error message. Right now, it doesn't, which can cause >documentation markup errors to go unnoticed. [...] >The patch below is one way of making sure that extract_autodoc fails. >Maybe there are better ways. >

Pike Meet-up 2018-Q3

Hi. At Pike Conference 2017 it was decided that we ought to hold a more informal meeting in Linköping ~ once every quarter. As the nine month mark from the conference is coming up soon, it seems time to announce the third such meeting for 2018: Pike Meet-up 2018-Q3 Date:

Re: calling methods

> Could I trouble you for some insight into your GI branch code? > I was looking at > >static void signal_func_wrapper(struct signal_data *d, gpointer go, guint >n_params, >    const GValue *param_values, GValue >*return_value) { >    struct signal_wrapper_context

pike -x module

>There may be an error in this?  Not sure, but in my code, I'm getting an >error.  I removed @ from the beginning the shell code in Makefile so that I >can see the output: >if test "xgi.o" != "x" ; then \ >  /usr/local/pike/8.0.610/include/pike/install_module module.so

calling methods

> Which brings up a question:  is it possible to add a method to a > class that has already started and ended (using start_new_program() > and end_program()). > And how could I write the frontend pike code to intercept > GTK3.Window and have it call GTK3.method_missing.  I was looking at > the

interesting terminfo error

Hi Lance. >I encountered this error on a system that had it's term type set to >xterm-256color: >$ TERM=xterm-256color pike >Terminfo: unparsable terminfo file "/usr/share/terminfo/x/xterm-256color" >/usr/local/pike/8.0.498/lib/modules/Stdio.pmod/Terminfo.pmod:406: [...] > >$ file

Pike Meet-up 2018-Q2

Hi again. A reminder about tomorrow: > Pike Meet-up 2018-Q2 > Date: 2018-05-19 (Sat) > Time: 10:00 - afternoon/evening > Place: Roxen IS AB > S:t Larsgatan 22A > Linköping /grubba

Compile problem on illumos for 8.0.608

>There seems to be one, possibly two compile problems on illumos >(ex-opensolaris). I just verified that 8.0.498 compiles without error, however >a fresh download of 8.0.608 fails with this error: > > Making dynamic: post_modules/Shuffler >There's no master to handle the error. Dumping it

Re: Pike 8.0.528 release candidate

>> I can make another build this week. Can you do the Mac build Bill? > >I have a few more NT-related fixes I'd like to get in. My fixes are in. /grubba

pike build msql error with 8.0 git

>So trying to build pike 8.0 from git, and got an error about Msql: > >=== configuring in Msql >(/home/riffraff/src/pike/8.0/pike/build/linux-4.16.6-302.fc28.x86_64-x86_64/modules/Msql) >configure: running /bin/bash -norc >/home/riffraff/src/pike/8.0/pike/src/modules/Msql/configure

Re: Pike 8.0.528 release candidate

> I can make another build this week. Can you do the Mac build Bill? I have a few more NT-related fixes I'd like to get in. /grubba

Pike Meet-up 2018-Q2

Hi. At Pike Conference 2017 it was decided that we ought to hold a more informal meeting in Linköping ~ once every quarter. As the six month mark from the conference has passed, it seems time to announce the second such meeting for 2018: Pike Meet-up 2018-Q2 Date: 2018-05-19

Re: Filesystem.Monitor race condition

> I guess what I was looking for was an answer to whether or not it is > a design feature to be able to create monitors on folders that don't > exist. I was planning to ensure that new monitors have valid stat > objects on creation. That way, if the directory is gone by the time > the monitor

Type warnings on 8.0?

>The problem is probably that State uses the parent pointer >(and thus isn't constant if indexed from an object(_HMAC)). >In this case it is indexed from the class, which renders a >constant, but the value is invalid for cloning the class, >so it is hidden from indexing in the runtime. However

Type warnings on 8.0?

>lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:446: Warning: Not a valid >object type. >lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:446: Warning: Expected: >function(void | mixed ... : object) | object | program. >lib/modules/__builtin.pmod/Nettle.pmod/Hash.pike:446: Warning: Got :

cp is different from rm/mv

Also note that the cp() hook lambda probably doesn't work as the author intended, as it will reinstall the predef every time it is used.

Re: Doc fixes and @namespace removal

>Stephen R. van den Berg wrote: >>Could someone please take a look at: > >>I kicked out some @namespace and @endnamespace directives that autodoc >>complained about. I'm unsure if simply removing them had the desired effect. > >Ah, well, yes, Grubba, you restored them, but, then the problem

strlen

>https://pike.lysator.liu.se/generated/manual/modref/ex/predef_3A_3A/strlen.html >says that strlen is deprecated and that we are supposed to use sizeof >instead. At the same time, I see new Pike code beeing committed that >use strlen (282a8a93 by Grubba 2018-01-04, a5c5c7cd by Bill >2017-12-22,

strange error on cross-compiled pike 8

>I cross compiled pike 8.0.498 on an amd64/linux system for use on an >armv5tejl/linux system, and I m getting a strange error when starting it up: > >-:1: Type mismatch for callback function `[]=: >-:1: Expected: scope(0,function(zero, (0=zero) : 0)). >-:1: Got : function(int(128..-129),

//

Windows?

Protocols.HTTP.Server.SSLPort()->create([...], void|int share)

> I'm trying to figure out what the "void|int share" argument of > Protocols.HTTP.Server.SSLPort()->create() really does. The > documentation is less than helpful: > > > Parameter share > > > > If true, the connection will be shared if possible. See > > Stdio.Port.bind for more information > >

Re: New pike.vim (Re: Newlines in strings)

> Stephen R. van den Berg wrote: [...] > Incidentally the docs for Autodoc seem to be incomplete; it fails to > document @global ? It's probably intentional; from Tools.AutoDoc.DocParser: parseError("The @global keyword is obsolete. " "Use @belongs predef::

Port fixes to mktime() and System.TM() from 8.1 to 8.0?

>As a by-product of creating the Val.Timestamp (et al) types, I encountered >numerous bugs and uncertainties in mktime() and System.TM() with regard >to timezone handling/abuse. > >AFAICS, all these bugs have now been dealt with and fixed in 8.1. >Any objections if I port these fixes from 8.1 to

  1   2   3   4   5   >