Re: Optimised map

On Wed, Apr 6, 2016 at 8:12 AM, Martin Karlgren wrote: > Having realised the benefits of functional programming, I’ve been quite > annoyed by the rumour of how expensive function calls are in Pike. I decided > to look into f_map and could see how much seemingly unnecessary work

Re: Pike 8.0.222 release candidate

On Wed, Apr 6, 2016 at 7:37 AM, Peter Bortas wrote: > No final release today. The disk in my virtual Windows machine broke. > Fixing that took up time that should have been used for testing, so > you will only get some completely untested builds. I've spun this up in a couple

Re: Pike 8.0.222 release candidate

On Wed, Apr 6, 2016 at 9:50 AM, Peter Bortas @ Pike developers forum <10...@lyskom.lysator.liu.se> wrote: >>I can't recommend this to my users while it ships GTK 2.12.11 :( Is >>there anything I can do to help out there? > > Well. GTK+ used to be available as an all-in-one package for Windows >

Segfault in colortable.c

I've been digging into a segfault that was preventing 'make doc' from operating correctly, and pinned it down to this code: src/modules/Image/colortable.c:2010 - rnd->u.refs++; + ++*rnd->u.refs; and corresponding decrementing of the refcount. The count appears to be a

Re: Segfault in colortable.c

On Fri, Mar 25, 2016 at 10:55 PM, Martin Nilsson (Coppermist) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se> wrote: > Probably correct. We really should have all the image operations > performed in the image testasuite as well... Okay, pushed to 8.1 then. Thanks. ChrisA

Tracking down corruption after exception in GTK signal handler

int main() { GTK2.setup_gtk(); object btn=GTK2.Button("Raise an exception"); object win=GTK2.Window(0)->add(btn)->show_all(); win->signal_connect("destroy",lambda() {exit(0);}); btn->signal_connect("clicked",lambda() {error("Baboom!\n");}); return -1; } Run this, click

Re: Tracking down corruption after exception in GTK signal handler

On Thu, Mar 3, 2016 at 12:45 PM, Lance Dillon wrote: > However: > > > int main() > { > GTK2.setup_gtk(); > object btn=GTK2.Button("Raise an exception"); > object win=GTK2.Window(0)->add(btn)->show_all(); > win->signal_connect("destroy",lambda()

Re: Tracking down corruption after exception in GTK signal handler

On Thu, Mar 3, 2016 at 12:50 PM, Lance Dillon wrote: > Sorry, that was all wrong. That is callback_args, which is a required > parameter. > > > get_all_args("signal_connect",args,"%s%*%*.%s%d",_before); > > assign_svalue_no_free(>cb,tmp1); >

Re: Tracking down corruption after exception in GTK signal handler

On Thu, Mar 3, 2016 at 7:13 PM, Arne Goedeke wrote: > Try running that test with valgrind, it should tell you more reliably > what the issue is. You will either have to compile pike --with-valgrind > or use --smc-check=all so that valgrind is able to deal with the > generated

Re: Tracking down corruption after exception in GTK signal handler

On Thu, Mar 3, 2016 at 8:53 PM, Arne Goedeke wrote: > Try compiling --without-machine-code and --with-valgrind, this will get > rid of most of the false positives. Thanks - that gets rid of most of the noise. This seems to be what's happening: $ sudo apt-get install

Re: Tracking down corruption after exception in GTK signal handler

On Thu, Mar 3, 2016 at 11:00 PM, Peter Bortas @ Pike developers forum <10...@lyskom.lysator.liu.se> wrote: > Try compileing Pike with -fsanitize=address, there's a fairly good > chance that would catch exactly when things start going wrong of we > are talking about any kind of over/under-flow. >

Fixing compilation with --enable-werror

Currently, 8.1 trunk doesn't build with CONFIGUREARGS=--enable-werror on GCC 5.3.1, due to a couple of small issues. I've pushed fixes to the rosuav/enable-werror branch; can someone please try this on a different system, different compiler, etc, to see if it breaks anything? The three changes

Re: Revamping the Pike site

On Fri, Apr 22, 2016 at 2:30 AM, Pontus Östlund wrote: > The big problem with user contributions in docs is that the quality > varies from "good enough to turn appalling docs into something you can > actually use" to "flat-out wrong and horrendously misleading". Is > someone

Re: Revamping the Pike site

On Fri, Apr 22, 2016 at 2:46 AM, Pontus Östlund wrote: > We’ll the way I’m implementing it is you’ll have to authenticate via some of > the larger web networks like Github, Twitter, Google, Instagram e t c. That > would take care of bot created spam. > > My take on stuff like

Re: Revamping the Pike site

On Fri, Apr 29, 2016 at 6:57 PM, Pontus Östlund <pon...@roxen.com> wrote: > > 28 apr. 2016 kl. 16:56 skrev Chris Angelico <ros...@gmail.com>: > > On Fri, Apr 29, 2016 at 12:53 AM, Pontus Östlund <pon...@roxen.com> wrote: > > The reason is probably tha

Re: Revamping the Pike site

On Fri, Apr 29, 2016 at 12:26 AM, Chris Angelico <ros...@gmail.com> wrote: > Also: After messing with the docos, I'm having trouble forcing my > browser to refresh - neither F5 nor Ctrl-F5 shows the newly-documented > module under Protocols. Using porn mode (incognito/secure >

Re: Revamping the Pike site

On Fri, Apr 29, 2016 at 12:26 AM, Chris Angelico <ros...@gmail.com> wrote: > On Tue, Apr 19, 2016 at 4:02 AM, Pontus Östlund <pon...@roxen.com> wrote: >> Module refdoc: >> http://poppa.github.io/pikedoc/ > > Just run into a strangeness in the new docs. It appe

Re: Revamping the Pike site

On Tue, Apr 19, 2016 at 4:02 AM, Pontus Östlund wrote: > Module refdoc: > http://poppa.github.io/pikedoc/ Just run into a strangeness in the new docs. It appears that a module that consists of a pmod directory without a module.pmod inside it doesn't get documented. (I don't

Stdio.File()->pipe() and PROP_IPC

What exactly does PROP_IPC (fd_INTERPROCESSABLE in the source) permit? Consider this usage: object stdout = Stdio.File(); Process.create_process(cmd, (["stdout": stdout->pipe()]); Is this at risk of failing, where stdout->pipe(Stdio.PROP_IPC) would succeed? I can't find anything that indicates

Re: Pike 8.0.222 release candidate

On Wed, Apr 6, 2016 at 10:25 AM, Peter Bortas @ Pike developers forum <10...@lyskom.lysator.liu.se> wrote: > Well, the build machine is an XP. I don't mind dropping anything > before 7. But that means a whole new build environment. Not happening > this week. Fair enough. I'd guess that GTK

Re: Revamping the Pike site

On Fri, Apr 29, 2016 at 12:53 AM, Pontus Östlund wrote: > The reason is probably that the navigation is cached (per page) in a > ”sessionStorage” once it’s been generated. Now, the sessionStorage you would > think would run out of scope once you restart the browser but that

SSL.File()->nonblocking_mode is protected

I'm messing around with SSL.File in a threaded server, and have run into a strange difficulty. The object defaults to nonblocking mode, which is fine; but how do I set it to blocking mode? Here's my current code: //sock is a straight Stdio.File initially string handshake = sock->read(9, 1); if

Re: CHANGES for next release

On Fri, May 6, 2016 at 9:29 AM, Lance Dillon wrote: > Hmm, probably a typo, documentation says composited-changed for both gtk2 > and 3. Looks like it may have existed since 2.10. I think it probably > hasn't been tested. There are a lot of signals that would be hard to

Re: Pike 8.0.240 release candidate

On Tue, May 10, 2016 at 6:26 AM, Peter Bortas wrote: > I did an effort to get a Windows 10 environment up this weekend, but > it's not done. So here is a release candidate together with an old > classically compiled Windows version. If no one finds anything bad > (where bad is

Re: Revamping the Pike site

On Tue, Apr 19, 2016 at 4:02 AM, Pontus Östlund wrote: > Module refdoc: > http://poppa.github.io/pikedoc/ > > So feel free to comment and give feedback. This is the same refdoc layout that's being built from current trunk Pike, right? I've been using it for a while now; for the

Re: Notes from the impromptu developer meetup 2016-07-07

On Fri, Jul 22, 2016 at 12:41 AM, Peter Bortas wrote: > Consider this a Windows problem and call up the 3 Windows users by phone. Hah. Actually, I've been pushing more people onto Pike who aren't developers, and unfortunately there are a number of trickinesses to working on

Re: Notes from the impromptu developer meetup 2016-07-07

On Fri, Jul 22, 2016 at 1:05 AM, Martin Bähr wrote: > Excerpts from Chris Angelico's message of 2016-07-22 00:46:18 +1000: >> Hah. Actually, I've been pushing more people onto Pike who aren't >> developers, and unfortunately there are a number of trickinesses to >> working on

String.trim[_all_whites]

The switch from trim_all_whites to trim broke clean builds on systems where the installed Pike doesn't have trim. The blocker is src/modules/_Charset/make_jisx0213_tables_h.pike, but after fixing that, there are still lots of module precompilation failures, eg: Compiling modules/Gmp/mpz_glue.c

Proposal: Create Stdio.Port from systemd-provided socket

Branch: rosuav/systemd-sockets Currently, you can create a Stdio.Port("stdin") as a means of accepting a socket handed to you as FD 0. However, there's no way to accept a socket given as any other FD, making it impossible to use this for systemd's sockets. Example: $ cat

Re: Proposal: Create Stdio.Port from systemd-provided socket

On Sun, Feb 12, 2017 at 8:36 AM, Arne Goedeke wrote: > I had a look at your branch. My feeling is that this would be better > placed into a seperate module. Maybe there will be more things that > might be useful when interacting with systemd? Maybe; if so, Stdio.Port would

Re: Proposal: Create Stdio.Port from systemd-provided socket

On Sun, Feb 12, 2017 at 9:54 AM, Arne Goedeke wrote: > I was reading the diff wrong, sorry about that. How about > Stdio.Port()->listen_fd()? *facepalm* That would be what I was looking for originally. How did I not see it? Thanks Arne. So the question is... why

Re: Proposal: Create Stdio.Port from systemd-provided socket

On Sun, Feb 12, 2017 at 6:40 PM, Mirar @ Pike developers forum <10...@lyskom.lysator.liu.se> wrote: > I'm guessing that the original was "stdin", then someone had the same > problem you had and expanded the API without breaking backwards. Entirely possible. I've deleted the branch for this

Re: Compile error in 8.1

On Thu, Sep 15, 2016 at 8:36 AM, Chris Angelico <ros...@gmail.com> wrote: > On Thu, Sep 15, 2016 at 8:34 AM, Pontus Östlund <pon...@roxen.com> wrote: >> Does anyone know how to solve this? >> >> make[2]: *** No rule to make target >> '/home/poppa/src/

Re: Compile error in 8.1

On Thu, Sep 15, 2016 at 8:34 AM, Pontus Östlund wrote: > Does anyone know how to solve this? > > make[2]: *** No rule to make target > '/home/poppa/src/pike-git/devel/src/hashtable.h', needed by 'cpp.o'. Stop. > Makefile:149: recipe for target '_make_in_builddir' failed >

Re: Lambdas, captured variables

On Thu, Oct 27, 2016 at 7:12 AM, Martin Karlgren <ma...@roxen.com> wrote: >> 26 okt. 2016 kl. 21:23 skrev Chris Angelico <ros...@gmail.com>: >> >>> On Thu, Oct 27, 2016 at 6:08 AM, Martin Karlgren <ma...@roxen.com> wrote: >>> A possible worka

Re: Lambdas, captured variables

On Thu, Oct 27, 2016 at 6:08 AM, Martin Karlgren wrote: > A possible workaround is to cut the reference to the “foo” frame: > > function f = lambda(string var1, string var2) >{ > return lambda(string arg) > { >

MIME.Message and RFC 2047 encodings

Currently, Pike's MIME.Message parser doesn't handle non-ASCII headers with specified encodings: > MIME.Message("Hello, world!", (["Subject": "Hello, \U0001F310"])); (10) Result: Message(([ ])) > (string)_; (11) Result: "Subject: Hello, \U0001f310\r\n" "Content-Length: 13\r\n"

Re: MIME.Message and RFC 2047 encodings

On Sun, Oct 30, 2016 at 9:17 PM, Chris Angelico <ros...@gmail.com> wrote: > On Sun, Oct 30, 2016 at 4:17 AM, Martin Karlgren <ma...@roxen.com> wrote: >> Adding charset decoding to MIME.Message sounds good to me, perhaps with a >> flag to enable it on decoding? >&

Re: MIME.Message and RFC 2047 encodings

On Sun, Oct 30, 2016 at 4:17 AM, Martin Karlgren wrote: > Adding charset decoding to MIME.Message sounds good to me, perhaps with a > flag to enable it on decoding? > (A compat problem I can think of is that applications may assume that decoded > data is 8bit strings and fail

Re: Bad function identifier on 8.1

On Wed, Nov 9, 2016 at 2:01 AM, Stephen R. van den Berg wrote: > While trying to use Pike 8.1, I consistently get the following on stderr > whenever I run pike: > > /usr/local/pike/8.1.6/lib/modules/Crypto.pmod/Random.pmod.o:-: Warning: > Decode failed: Error while decoding >

Re: Proposal: Checked subprocess calls

On Mon, Nov 7, 2016 at 7:15 AM, Peter Bortas wrote: > Chris: What you have seem generally useful, but it lies in a namespace > that will get a bit busy if we implement all the special cases as we > think of them. I have similar function not checked in that would > confuse users

Re: Pike 8.0.352 release candidate

On Tue, Nov 8, 2016 at 11:24 PM, Peter Bortas wrote: > > https://pike.lysator.liu.se/pub/pike/beta/8.0.352/Pike-v8.0.352-win32-oldlibs.msi What will it take to produce a Pike with new libraries (notably GTK2)? I tried to build it at one point, and failed badly :( ChrisA

Re: Added permessage-deflate support to WebSocket

On Wed, Oct 19, 2016 at 11:20 PM, Arne Goedeke wrote: > On 10/18/16 11:46, Stephen R. van den Berg wrote: >> Arne Goedeke wrote: >>> * permessage-deflate is activated by default. i don't believe that >>> this is a good choice. >> >> The default is what should help most users.

Re: Proposal: Checked subprocess calls

On Sat, Oct 15, 2016 at 8:12 PM, Stephen R. van den Berg <s...@cuci.nl> wrote: > Chris Angelico wrote: >>Two features added to the Process module. Firstly, a simple wrapper >>Process.check_run that calls Process.run and throws an error if the >>exit code isn't 0; >

Re: MIME.Message and RFC 2047 encodings

On Wed, Nov 23, 2016 at 1:35 PM, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se> wrote: > IÃ'm sorry, but your code is incorrect, and it cannot be done > correctly either. As I explained, the encoding rules depend on the > grammar of the

Re: Clean-room Engine.IO implementation committed to git 8.0/8.1

On Wed, Nov 23, 2016 at 10:00 PM, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se> wrote: > If there are no character values >127, then the encoding step is a > no-op, so skipping it buys you nothing except making your code harder > to read. I

Re: Clean-room Engine.IO implementation committed to git 8.0/8.1

On Wed, Nov 23, 2016 at 11:10 PM, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se> wrote: >>I agree, but using string(8bit) to mean "binary data" is something >>that's 100% backward compatible. > > It would not be backwards compatible, since that

Re: Clean-room Engine.IO implementation committed to git 8.0/8.1

On Thu, Nov 24, 2016 at 12:20 AM, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se> wrote: >>\U12345678 possibly should be an error, as it's not valid Unicode. > > It's valid Pike. Pike supports the full ISO/IEC 10646 31-bit range, > plus an

Re: Clean-room Engine.IO implementation committed to git 8.0/8.1

On Wed, Nov 23, 2016 at 10:30 PM, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se> wrote: > I think you are conflagrating range with interpretation. Both a > Latin1 string and an UTF-8 encoded one are 8-bit strings (with a 0-255 > range). What

Re: Clean-room Engine.IO implementation committed to git 8.0/8.1

On Thu, Nov 24, 2016 at 12:40 AM, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se> wrote: >>In Python, it's done with a prefix - u"asdf" is a Unicode string, and >>b"asdf" is a byte string. > > Since nominally strings are Unicode (with the

Protocols.SMTP.ClientHelper()->rfc2822date_time()

What exactly is this function, and how does it differ from Calendar.Time.format_smtp()? The docs for the latter state that it's "as seen in Date: headers in mails", which seems to be the same purpose. They appear to give the same output. Should the ClientHelper function have a docs reference to

Re: MIME.Message and RFC 2047 encodings

On Sun, Oct 30, 2016 at 11:04 PM, Chris Angelico <ros...@gmail.com> wrote: > I've pushed a change to 8.1 that ought to be 100% backward compatible. > If there's a problem, I can revert it, but there shouldn't be. (Just > in case, it's not in 8.0.) The two notable feat

Code review request: branch rosuav/gtk2-drag-drop

I'm aware that GTK2 is a bit of a dark and dusty corner in Pike, with few devs understanding everything that goes on in there. Nonetheless, I'm hoping someone can eyeball my code, at least from a general Pike dev point of view. Are there pitfalls that I haven't noticed? Things that I've done

Re: Lambdas, captured variables

On Mon, Oct 31, 2016 at 8:53 AM, Martin Karlgren wrote: > Btw: is 8.1 officially on C99 now? I’ve rarely seen line comments or inline > variable declarations in commits, but maybe it’s just old habit. :-) ) I'd like to know this too, actually. The code I'm currently working on

Re: Code review request: branch rosuav/gtk2-drag-drop

Marcus Comstedt on LysKOM: > IIUC the target is supposed to be a MIME-type, which means that > non-ASCII is simply not allowed. So you could check the min and max > of the string to make sure it only contains ASCII and no control > characters (such as NUL). Huh. Didn't know that; the docs I was

Re: MIME.Message and RFC 2047 encodings

On Mon, Oct 31, 2016 at 7:46 PM, Martin Karlgren wrote: >> New proposal: MIME.decode_words_text_remapped is the single most >> obvious way to decode a Subject header (among others), but that's >> really not obvious from the docs. Can we somehow make that more >> discoverable? I

Re: Code review request: branch rosuav/gtk2-drag-drop

Responding to Martin Nilsson's post on LysKOM (if I respond directly there, I'll have no record at my end): > From a very quick look: _decode_targets in gtkwidget.pre doesn't check > that the sub-array size is 3 before indexing it. And checking that > ITEM(cur)[0].u.string->size_shift is 0 is

Re: Proposal: Checked subprocess calls

On Sun, Oct 16, 2016 at 8:12 PM, Stephen R. van den Berg wrote: > Well, ok, fair enough. But then, try to improve on the interface and > preferably make it work like this: > (unless there already is an easy Pike-API for this, I'm not intimately > familiar with the Process-group) >

C99, dynamic arrays, and branch rosuav/gtk2-drag-drop

I've noticed a number of commits going through that remove C99isms for the sake of Windows builds. Does that imply that the code must be exclusively C89, or are there some C99isms that are acceptable? The only one left now is a dynamic array: GtkTargetEntry drag_targets[targ->size]; Will this

Re: C99, dynamic arrays, and branch rosuav/gtk2-drag-drop

On Tue, Dec 13, 2016 at 10:40 AM, Peter Bortas @ Pike developers forum <10...@lyskom.lysator.liu.se> wrote: > I'd be OK with disabling GTK on Windows in 8.1 for now if the > alternative is uglifying your entire codebase. Grubba might need it > for something though, so don't commit anything to

Re: C99, dynamic arrays, and branch rosuav/gtk2-drag-drop

On Tue, Dec 13, 2016 at 10:25 AM, Peter Bortas @ Pike developers forum <10...@lyskom.lysator.liu.se> wrote: > I don't know the details, grubba is the one that has been trying to > get 8.1 to build on the existing VC9 Windows build machines. So > anything that doesn't break VC9 is probably fine.

Re: C99, dynamic arrays, and branch rosuav/gtk2-drag-drop

On Tue, Dec 13, 2016 at 10:47 AM, Chris Angelico <ros...@gmail.com> wrote: > The change will be pushed (to rosuav/gtk2-drag-drop) as soon > as I figure out why Pike is segfaulting, which seems to be unrelated. Found it. The GTK build script includes this (massively cut down): //bui

Re: C99, dynamic arrays, and branch rosuav/gtk2-drag-drop

On Tue, Dec 13, 2016 at 9:58 PM, Arne Goedeke <e...@laramies.com> wrote: > On 12/13/16 00:33, Chris Angelico wrote: > >> I'm having trouble finding authoritative information on what VC9 >> supports (MS don't seem to carry much information on their older >> compiler

Re: GTK/GDK on OSX

On Sat, Mar 18, 2017 at 3:55 AM, H William Wellliver III wrote: > Thanks for taking a stab at it, Chris. I will have a look this weekend... > just got a fresh OSX VM running so I can test things out pretty easily. > > Getting a build attempt on Windows is possible but may

Re: GTK/GDK on OSX

On Thu, Mar 23, 2017 at 8:06 AM, H William Wellliver III wrote: > Looks like there are some X11isms in the source code as well (such as use of > GDK_DISPLAY() on non-NT systems) that will need to be dealt with. I may take > a look at them at some point if no one else gets to

Conditional inclusion of inotify_config.h?

Branch: rosuav/inotify-config Currently, inotify.cmod won't go looking for inotify_config.h unless HAVE_INOTIFY_CONFIG_H is defined. This doesn't seem to match the way other autoheader files get included, and it results in System.Inotify not being available even on systems that support inotify.

Re: Bad function identifier on 8.1

On Wed, May 24, 2017 at 8:32 PM, Stephen R. van den Berg <s...@cuci.nl> wrote: > Chris Angelico wrote: >>The simplest workaround is to delete the .o file in question after you >>install. I still haven't managed to track down exactly what the >>problem is, or make a minim

Re: GDK/GTK on OSX

On Wed, May 24, 2017 at 7:37 AM, H. William Welliver III wrote: > I’ve been quietly working on this for a few weeks now, and have got the > various permutations working on OS X. Basically, there are 2 paths for GTK > on OS X (now called macOS): X11, which is the classic

Proposed improvements to Hilfe

Branch: rosuav/hilfe-improvements Two smallish improvements to Hilfe. One is suppressing "quit" and "exit", per the TODO at the top; fairly simple but I'd like someone else's eyeballing to make sure it's going about things the right way. The other is the addition of a new help() built-in

Possible issue with elliptic curve crypto?

I'm far from any sort of crypto expert, but this looks a bit odd. SSL.File() is bombing out when trying to work with ECDHE ciphers. Using this Pike script: object ssl; void readcb(mixed id, string data) {exit(0, "Readable\n%s\n", data);} int x=1; void writecb() {if (x) ssl->write("asdf\n"); x=0;

Re: "old" mails on the list

On Thu, Nov 23, 2017 at 9:02 AM, Peter Bortas wrote: > Hello list subscribers, > > I finally took over responsibility for the LysKOM exporter, and ran it > through the backlog. Which means you just got a bunch of new mails > that have a send date of today but might have been

Re: Proposed improvements to Hilfe

On Thu, Nov 23, 2017 at 8:44 AM, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se> wrote: >>The other is the addition of a new help() built-in function, which >>gives human-readable information about whatever object it's given. >>Currently it

Re: Proposed improvements to Hilfe

On Thu, Nov 23, 2017 at 8:44 AM, Henrik Grubbström (Lysator) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se> wrote: >>Branch: rosuav/hilfe-improvements >> >>Two smallish improvements to Hilfe. One is suppressing "quit" and >>"exit", per the TODO at the top; fairly simple but I'd like

Re: Conditional inclusion of inotify_config.h?

On Thu, Nov 23, 2017 at 7:58 AM, Martin Nilsson (Coppermist) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se> wrote: > The change look good. I've no idea when you posted this, but I only just saw it. So I've merged that branch in now. The lyskom => mailing list gateway must have been

Re: Calendar does not seem to use mktime()/localtime()/gmtime()

On Fri, Dec 15, 2017 at 12:41 AM, Peter Bortas @ Pike developers forum <10...@lyskom.lysator.liu.se> wrote: > While true, for actual Pike installations 64bit dominate. The number > of Pike mobile applications are quite low. By "quite low" do you actually mean zero, or is there actually such a

Re: JSON5

On Sun, Dec 24, 2017 at 10:58 AM, Martin Nilsson (Coppermist) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se> wrote: >>Having taken a quick cursory look at the new JSON5 module, I think it >>would make sense to have a distinct decoder for JSON5, but have common >>code for the encoder.

Re: GTK/GDK on OSX

On Thu, Mar 23, 2017 at 12:51 AM, Chris Angelico <ros...@gmail.com> wrote: > On Sat, Mar 18, 2017 at 3:55 AM, H William Wellliver III > <will...@welliver.org> wrote: >> Thanks for taking a stab at it, Chris. I will have a look this weekend... >> just got a fresh OSX V

Re: Protocols.DNS.server anyone used it in a DNS server?

On Thu, Feb 8, 2018 at 12:04 PM, Stephen R. van den Berg wrote: > Has anyone ever used Protocols.DNS.server in an application > (to implement a mini-DNS server)? > Is the code available? Yep! Here's one that shares your /etc/hosts.

GTK2.Object()->destroy() checking for no args?

I doubt anyone will know the answer to this, as it's in 12+ year old code in the GTK2 module, but the destroy method (now renamed to _destruct) was explicitly checking that it received exactly zero args before calling gtk_object_destroy. Any idea why? Is there a situation in which destroy() might

Re: GTK2.Object()->destroy() checking for no args?

On Fri, Dec 22, 2017 at 9:49 PM, Stephen R. van den Berg <s...@cuci.nl> wrote: > Chris Angelico wrote: >>before calling gtk_object_destroy. Any idea why? Is there a situation >>in which destroy() might have been called with arguments, such that it >>shouldn't actually

Re: GTK2.Object()->destroy() checking for no args?

On Sat, Dec 23, 2017 at 12:42 AM, Henrik Grubbström (Lysator) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se> wrote: > Note that AFAIK destruct() in some GTK2 classes is a public function > (and thus part of the API). Do you mean destroy? It got renamed in the big _destruct rename, and

Re: GTK2.Object()->destroy() checking for no args?

On Sat, Dec 23, 2017 at 2:11 AM, Henrik Grubbström (Lysator) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se> wrote: >>On Sat, Dec 23, 2017 at 12:42 AM, Henrik Grubbström (Lysator) @ Pike >>(-) developers forum <10...@lyskom.lysator.liu.se> wrote: >>> Note that AFAIK destruct() in some

Interaction between automap and argument splicing segfaults

Test case: int score_image(string image, int r, int g, int b) {return 42;} array(int) getpixel() {return ({1, 2, 3});} int main(int argc, array(string) argv) { if (argc < 2) exit(0, "All good! Try again with -DBOOM for a segfault.\n"); array images = ({"foo", "bar", "quux"}); for

Re: Interaction between automap and argument splicing segfaults

On Thu, Apr 4, 2019 at 11:11 PM Henrik Grubbström (Lysator) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se> wrote: > > > 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

Re: Shuffler.Shuffler, does anyone use it?

On Thu, Jun 13, 2019 at 9:38 PM Stephen R. van den Berg wrote: > > I though Roxen might be using it, but maybe I remember it wrong. > Anyone else? > > I ask because I'm changing Protocols.HTTP.Server.Request to use the > Shuffler, and I'm close to done, but it appears that in the process I have >

Re: Comments/thoughts requested: Generators and async functions in Pike

On Sun, Aug 11, 2019 at 8:37 AM Stephen R. van den Berg wrote: > > Chris Angelico wrote: > >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 o

Re: Comments/thoughts requested: Generators and async functions in Pike

On Tue, Aug 27, 2019 at 3:26 AM Henrik Grubbström (Lysator) @ Pike (-) developers forum <10...@lyskom.lysator.liu.se> wrote: > > > 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

Re: Use of ::_destruct() in arbitrary objects

On Tue, Aug 27, 2019 at 3:18 AM Stephen R. van den Berg wrote: > > Chris Angelico wrote: > >In digging into a problem with Protocols.HTTP.Promise, I came across > > ># define PROMISE_DESTRUCTOR \ > > protected void _destruct() { \ > &

Re: Comments/thoughts requested: Generators and async functions in Pike

On Tue, Aug 27, 2019 at 7:51 PM Stephen R. van den Berg wrote: > > Chris Angelico wrote: > >string show_channel_info(string name) { > >int id = continue return get_channel_id(name); > ... > >return name + " is offline."; > > >The intermediate

SSL cert for pike.lysator.liu.se has expired

Going to https://pike.lysator.liu.se/ shows a big warning about the certificate having expired. Who's in charge of this? ChrisA

Re: SSL cert for pike.lysator.liu.se has expired

On Fri, Aug 23, 2019 at 11:59 PM Peter Bortas @ Pike developers forum <10...@lyskom.lysator.liu.se> wrote: > > I guess that's me. Fixed. Thanks! I was doing some Pike coding on live-stream today and one of my viewers mentioned it. Appreciate the quick fix! ChisA

Use of ::_destruct() in arbitrary objects

In digging into a problem with Protocols.HTTP.Promise, I came across an issue with inheritance and destructors. #ifdef HTTP_PROMISE_DESTRUCT_DEBUG # define PROMISE_DESTRUCTOR \ protected void _destruct() { \ werror("%O()._destruct()\n", object_program(this)); \ }

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 generators and

Re: Image.PNG unable to find Gz

On Wed, Jan 1, 2020 at 12:38 AM Tobias S. Josefowitz @ Pike developers forum <10...@lyskom.lysator.liu.se> wrote: > > >As of commit 1c31950, the Image.PNG module fails unless Gz has already > >been loaded. The PIKE_MODULE_IMPORT lines fail, and the module chooses > >to export nothing. > > > >Is

Image.PNG unable to find Gz

As of commit 1c31950, the Image.PNG module fails unless Gz has already been loaded. The PIKE_MODULE_IMPORT lines fail, and the module chooses to export nothing. rosuav@sikorsky:~/pike$ pike -e 'write("%d\n", sizeof(indices(Image.PNG)));' 0 But if the Gz module gets tagged first, it works:

Re: RFC: Attributes in Markdown text

On Wed, Apr 8, 2020 at 1:04 AM H William Welliver wrote: > > Hi Chris- > > I haven’t looked at your branch (yet). Given that there are a number of > popular extensions to Markdown, perhaps rather than having a number of > different classes, we could have a flag that enables the various

RFC: Attributes in Markdown text

See branch: rosuav/markdown-attribute-syntax There's a not-very-well-known syntax supported by some Markdown parsers (including GitHub Flavored Markdown) that allows HTML attributes to be attached to a paragraph of text: Text goes here blah blah blah {: someattr=value otherattr=otherval} This

Re: RFC: Attributes in Markdown text

On Wed, Apr 8, 2020 at 1:12 AM Chris Angelico wrote: > With the proposed enhancement, it's governed by the flag "attributes" > - set it to 1 to get the new functionality (otherwise an attribute > block will be seen as just another paragraph of text). If there's > actually

Re: SQLite query segfaults

On Wed, Apr 29, 2020 at 5:13 AM Marc Simpson wrote: > > 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 > >

Re: SQLite query segfaults

On Wed, Apr 29, 2020 at 5:25 AM Marc Simpson wrote: > > 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 i

<    1   2   3   >