Re: Conference

Hello, I take it that the folks who showed interest in hosting the next conference weren't able to make things work. Is anyone else interested in holding a session this fall? Perhaps in mid-to-late september? As martin has indicated, we don't really need much space, a conference room

[OT] Re: Sprintf wrap removes space

We should grab a beer and discus this further some day :) For now: I guess I'll have to write my own wrapping function. I'm not sure i've an opinion about this sprintf stuff, since i didn't even knew it existed. However, i'd be very pleased to share a beer or two. -- Bertrand LUPART http

Re: debian package of pike (and caudium)

way to get 7.6.112 on etch (mixed system or compilation) This may be outdated: http://www.gotpike.org/PikeWiki/index.pike?page=Installing%20Pike -- Bertrand LUPART http://bertrand.gotpike.org/

[Patch] pike -x

888 -- Bertrand LUPART http://bertrand.gotpike.org/

Re: Regexp troubles

Should be a good start to narrow down the problem. -- Bertrand LUPART http://bertrand.gotpike.org/

[Bug] Regexp.PCRE(n*) multiple match endless loop (was: Re: Regexp troubles)

know which code should be fixed for now. I don't understand the documentation for exec() when it returns an array here: http://pike.ida.liu.se/generated/manual/modref/ex/predef_3A_3A/Regexp/P CRE/_pcre/exec.html -- Bertrand LUPART http://bertrand.gotpike.org/

Re: [Bug] Regexp.PCRE(n*) multiple match endless loop

SimpleRegexp()). I don't know if something like trim_whites_right() nor trim_whites_left() does exists, but feel free to watch the code of trim_whites()/trim_all_whites() and contribute a Public.String.trim_whites_[right|left]() into http://modules.gotpike.org/ :) -- Bertrand LUPART http

Re: Strong type checking

gives: 8888 strict_types.pike:9:Bad argument 1 to test. strict_types.pike:9:Expected: function(string : void) strict_types.pike:9:Got : function(int(345..345) : void | mixed) 8888 -- Bertrand LUPART http://bertrand.gotpike.org/

[Bug] Regexp() and $ (was: Re: [Bug] Regexp.PCRE(n*) multiple match endless loop)

: 8888 string bar = oofoo; Regexp(^[o]+)-replace(bar, ); (1) Result: foo 8888 While $ seems not: 8888 Regexp([o]+$)-replace(bar, ); (2) Result: f 8888 -- Bertrand LUPART http://bertrand.gotpike.org/

Re: [Bug] Regexp.PCRE(n*) multiple match endless loop

too. Thanx, -- Bertrand LUPART http://bertrand.gotpike.org/

[Bug] Parser.HTML crash

in _pthread_body () 8888 Thank you, -- Bertrand LUPART http://bertrand.gotpike.org/

Re: [Bug] Parser.HTML crash

-- Bertrand LUPART http://bertrand.gotpike.org/

Re: 7.8 alpha 2

Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum [EMAIL PROTECTED] wrote: Not MacOSX/PPC as far as I can see. I've readded my 10.4/PPC to xenofarm, but i guess this bug requires 10.5/PPC -- Bertrand LUPART http://bertrand.gotpike.org/

Re: Pike 7.8 beta

8 Then, update the list of available packages: $ sudo apt-get update Install Pike7.8 core package: $ sudo apt-get install pike7.8 Look for additional pike7.8 packages: $ sudo apt-cache search pike7.8 -- Bertrand LUPART http://bertrand.gotpike.org/

Re: Object - XML - object/Annotation

) Result: zero _typeof(t); (10) Result: zero _typeof(u); (11) Result: string _typeof(v); (12) Result: string 888 -- Bertrand LUPART 29, rue du Colisée - 75008 Paris +33 1 72 71 71 84

Pike 7.6 Debian wheezy

Hello, Does someone have (unofficial) pike7.6 packages for Debian wheezy he'd like to share? Thank you, -- Bertrand LUPART 29, rue du Colisée - 75008 Paris +33 1 72 71 71 84

Re: Pike 7.6 Debian wheezy

low level cryptographic library (development files) ——8——8——8—— Currently trying with src/post_modules/Nettle/cipher.c[mod] from 7.8.700 without patches, but i'm not really sure about what i'm doing. Thank you, -- Bertrand LUPART 29, rue du Colisée - 75008 Paris +33 1 72 71 71 84

Re: Pikefarm client

Hello,What is the correct client for participating to the pikefarm ?The one listed on the website [1] seems outdated. […][1] https://pike.lysator.liu.se/development/pikefarm/ Here’s a patch to make xenoclient 1.3 listed on the website usable out-of-the-download

Pikefarm client

Hello, What is the correct client for participating to the pikefarm ? The one listed on the website [1] seems outdated. I guess I should start with the one on GitHub ? [2] Thank you, [1] https://pike.lysator.liu.se/development/pikefarm/

Pike's Wikipedia page

Hey folks, Just made the Pike’s Wikipedia page available again (it was redirecting to MUD’s one for about a year) Already happened in the past, and the page was even proposed for deletion due to the following reasons : * Lacks significant coverage from reliable, independent sources. * This

Re: Pike testing

Hello, >> As a side note, maybe the brew Pike formula could be enhanced to >> provide mktestsuite in the PATH ? > > I'm not sure what the best solution is for this; "mktestsuite" is kind of a > generic name. Maybe we could add an option to test_pike to generate the > testsuite? Getting back

Re: Pike testing

Yeah, it maybe wasn’t engineered this way, but we end up with a shell script hidden in the source tree, depending on m4 you wouldn’t run at runtime. A system subtle enough to run tests against the Pike binary you just compiled instead of the installed one. A marvel for a Pike core hacker :)

Pike testing

Hello, I’m a bit lost in the incomplete (and maybe outdated) documentation about testing in the Pike manual [1] Is this intended to do unit testing ? Is "pike -x test_pike" different kind of a beast ? Does someone use this for testing its own code and would like to share an example? Thank

Re: Pike testing

provide mktestsuite in the PATH ? If some kind of interest, here’s an example of a CI that will run the testsuite for a Pike module against latest Pike 7.8 and 8.0 Docker images upon a push on the GitHub repo : https://github.com/bertrand-lupart/pike-public-standards-csv/blob/master/.github/workflows/test-module.yml

Re: pike docker images

Hello, > Nice. The script does not work for me though: > > mikan:~/docker-pike% env DRYRUN=1 ./build-push.sh docker/8.0.1116 > building docker/8.0.1116 > [+] Building 0.0s (0/0) > error: multiple platforms feature is currently not supported for docker > driver. Please switch to a different

Re: pike docker images

> Btw, pike packages are indeed available for Debian/riscv64: > https://packages.debian.org/sid/pike8.0-core Yeah, just figured that, along with ppc64 and other oddities :) Thanx

Re: pike docker images

>> Looks like your local install is missing the buildx Docker plugin. It’s >> used by the script to build multi-arch container images. >> >> https://docs.docker.com/build/buildx/ > > Well, the documentation you pointed to says > > | Docker Buildx is included in Docker Desktop for Windows,

Re: pike docker images

Debian is offering ppc64le and riscv64 base container images, but not ppc64 : https://hub.docker.com/_/debian I thought ppc64le would fit any 64 bit POWER machine ? Anyhow, I used Debian packages as convenience to get fast results. Many other solutions could

Re: pike docker images

>> No luck with linux/ppc64 yet, need to have a closer look. > > I got buildx running, and AFAICT this seems to be an omission in the > moby/buildkit image that buildx is using. > > ppc64 is missing in the lists here: > > https://github.com/moby/buildkit/blob/master/util/archutil/Dockerfile >

Re: pike docker images

x on a linux/ppc64 machine ? https://github.com/bertrand-lupart/docker-pike/blob/993c96cf0a93719f9ed919af96ad900d99c498ac/docker/8.0.1116-ppc64/Dockerfile <https://github.com/bertrand-lupart/docker-pike/blob/993c96cf0a93719f9ed919af96ad900d99c498ac/docker/8.0.1116-ppc64/Dockerfile>

Re: pike docker images

Hello folks, > On 4 Aug 2022, at 20:41, H William Welliver wrote: > > A quick update: > > I’ve created a new docker organization called “pikelang”, to match the GitHub > organization. I’ve also put a request in to have it made an “OSS” > organization, which I hope will be approved and which

Re: pike docker images

> You can use use base containers I built if you want: > > https://hub.docker.com/r/zeldin/debian/tags > > They are built using debuerreotype, so they should be identical to > Debian built ones. There's also another guy making base containers > for ppc64 and some other arches (including

Re: pike docker images

Hello, > Ok, I think I have figured this out now. You don't need to modify > buildx itself, but if your docker host is not ppc64 you need to run > this command line first: > > docker run --rm --privileged aptman/qus -s -- -p ppc64 > > Then you can make linux/ppc64 images with buildx (tested

Re: Revamping the Pike site

us stuff i'm working on, but that's obviously not a good format for sharing sample code: https://github.com/bertrand-lupart/pike-sample-code -- Bertrand LUPART 29, rue du Colisée - 75008 Paris +33 1 72 71 71 84

Re: Revamping the Pike site

ule (well I’m alread y > halfway there!) we can use and have more control over the data. "Edit on GitHub" links are appearing on websites. Having fragments of refdoc pages in a git repo is an interesting concept, which would solve license, moderation and export issues. Just a tho

Re: Revamping the Pike site

going to vet all posts and make sure they're on the better > side of the scale? Indeed. I guess moderators (i'm volunteering) would be happy to fix those. Actually, the main drawback is not to have sample Pike code at all, rather than having some sub-optimal one. -- Bertrand LUPART

Re: Revamping the Pike site

e refdoc. That's double-edged sword, but that's the main drawback programmers i'd want to code in Pike opposed me. PHP user contributed notes for example could look sometimes lousy, but they give real-word examples to figure how to use modules. Sometimes, the refdoc look somewhat too much abstract to newcomers. Greetings, -- Bertrand LUPART

Re: Immediate call_out takes 2ms

Hello, > 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: […] > Is there a fix in younger version of Pike? 8.0.702 on macOS 10.14.6 : Pike bertrand$ for i in `seq 10`; do