Pike-devel November 2018

pike-devel@lists.lysator.liu.se

4 participants
10 discussions

Re: Playing music using pike and SDL.
by Martin Nilsson (lvl 60) ＠ Pike (-) developers forum 13 Mar '26

13 Mar '26

Were you not able to get any C code to play through SDL either? Does your SDL library have a mixer compiled in it (I think it is optional)?

5 4

managing comport settings in linux
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 13 Mar '26

13 Mar '26

Not a good idea; the design philosophy of Pike is that Pike-level code should never be able to cause memory corruption at C-level. With ioctls there's no way to know what data a specific ioctl wants without reading the documentation for that specific ioctl for that specific OS. ioctls and fcntls are a way for device handlers to hook in APIs that aren't standard across all filedescriptors. / Henrik Grubbström (Lysator) Previous text: >2004-08-17 13:32: >Subject: managing comport settings in linux >-------------------------------------------------------------------- >What would be nice, is a way to define ioctl methods in >Pike. Perhaps something like > >object i = Stdio.IOCTL(4242 /* request_id */ ); >i->add_int_parameter(); >i->add_string_parameter(); >i->set_return_type(STRING); > >string ret = i(fd, 1, "somestring"); > > >That ought to be possible, or..? > > / Marcus Agehall (PacketFront) >

3 2

full MySQL 4.x support. or pike roadmap
by thomas.gusenleitner＠com-bet.com ＠ Pike developers forum 01 Mar '26

01 Mar '26

HI to all! mysql 4.x support works only with a mysql CFLAGS=-DUSE_OLD_FUNCTIONS is this correct ? are there plans to make a full 4.x support ? bye, thomas

4 4

Pike Meet-up 2018-Q1
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 20 Oct '21

20 Oct '21

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 conference is coming up soon, it seems time to announce the first such meeting for 2018: Pike Meet-up 2018-Q1 Date: 2018-02-03 (Sat) Time: 10:00 - afternoon/evening Place: Roxen IS AB S:t Larsgatan 22A Linköping Welcome! /grubba

2 13

Operator assignment and strict_types
by Marc Simpson 07 Jul '20

07 Jul '20

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 of foo's restricted int domain: int(3..3) foo = 3; foo++; // no warning foo += 1; // no warning foo = foo + 1; // warning from strict_types Similarly, operator assignment on aggregates fails to elicit a warning: array(int) a = ({}); multiset(int) b = (<>); mapping(int:int) c = ([]); // no warnings a += ({ "hey" }); b += (< "hey" >); c += ([ "hey": "there" ]); // warnings from strict_types a = a + ({ "hey" }); b = b + (< "hey" >); c = c + ([ "hey": "there" ]); I'm guessing this is because the checks provided by the F_ASSIGN/F_ASSIGN_SELF case (las.c) only apply to direct assignment; op= and friends are presumably not instrumented for strict_types in the same manner. Have there been any discussions around addressing this inconsistency? Thanks, Marc

3 3

Remixml, javascript module
by Stephen R. van den Berg 25 Feb '20

25 Feb '20

This might be of interest to the Pike and/or Roxen community: https://www.npmjs.com/package/remixml I just launched it. Using it in a Single-Page-Application website. Any critical feedback is welcome (I'm currently the only user, so changes in the API are easy and still allowed). >From the description: Remixml is an XML/HTML macro language/template engine. The language and primitives used blend in completely with standard XML/HTML syntax and therefore integrate smoothly with existing XML/HTML syntax colouring editors. Requirements It runs inside any webbrowser environment (starting at IE11 and up). For historical reference: Remixml was originally inspired by RXML, the Roxen webserver macro language. -- Stephen.

1 1

Thread.ResourceCount: Fixed mutex handling.
by Stephen R. van den Berg 08 Dec '18

08 Dec '18

commit d168eb73a23756642bdc80451ba206a345471f6a Author: Henrik Grubbström (Grubba) <grubba(a)grubba.org> Date: Sun Aug 5 11:21:52 2018 +0200 Thread.ResourceCount: Fixed mutex handling. I'm not saying that this is not correct, I just want to make sure I understand the change. Can anyone elaborate on as to why this change is necessary/desirable? -- Stephen.

2 4

line number storage and included files
by H. William Welliver III 26 Nov '18

26 Nov '18

Hi all, 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 comparing line numbers that come from the file I’m interested in. The initial file marker entry appears correctly, however, when the file changes, a new marker entry doesn’t seem to be inserted in the array. I see that the line numbers jump correctly, but there is no other indication that the source of the lines has changed. Is this intentional, or am I missing something? Here’s an example tracing through a program with a file included within a function definition. cnt: 127 <— beginning of program new file file: /Users/hww3/bpt.pike cnt: 0 line: 0 0x0 cnt: 36 line: 2 0x24 cnt: -127 line: 4 0xcd cnt: 54 line: 5 0x103 cnt: -127 line: 8 0x1ab cnt: -127 line: 9 0x23e cnt: 34 line: 10 0x260 cnt: 116 line: 12 0x2d4 cnt: -127 line: 14 0x37d cnt: 69 line: 15 0x3c2 cnt: -127 line: 16 0x467 cnt: -127 line: 18 0x52c cnt: -127 line: 19 0x5ff cnt: 76 line: 1 0x64b <— included file, line number jumps to 1, but no marker cnt: 114 line: 2 0x6bd cnt: 80 line: 21 0x70d <— back to original file, but also no marker cnt: -127 line: 22 0x7a6

4 10

Should atexit really store a weak reference?
by ceder (-) Per Cederqvist ＠ Pike (-) developers forum 23 Nov '18

23 Nov '18

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; This means that if you pass a lambda to atexit() and don't hold any other references to the lambda, it may be garbage collected. This is not documented, and I belive it is bad. At the very least, it is not what I expected. Here is a sample program. Note that is doesn't print "atexit lambda 0.200 running" unless you remove the gc call. --- cut here --- #!/usr/bin/env pike void do_exit() { werror("do_exit function running\n"); exit(0); } void setup_lambda(float x) { atexit(lambda() { werror("atexit lambda %f running\n", x); } ); } int main() { call_out(setup_lambda, 0.2, 0.2); call_out(gc, 0.4); call_out(setup_lambda, 0.6, 0.6); call_out(do_exit, 0.8); return -1; }

2 1

Pike sites downtime tomorrow, Saturday Nov 17
by Peter Bortas 16 Nov '18

16 Nov '18

All Pike sites will go down while the machines are moved a few racks over. The downtime will be somewhere between 09:00 and 18:00 and is estimated to last less than 60min. This is done together with a lot of other machines, so a more exact timeline is not possible. Regards, -- Peter Bortas

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel November 2018