Pike-devel August 2018

pike-devel@lists.lysator.liu.se

2 participants
4 discussions

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

wrong exit code of extract_autodoc on errors
by ceder (-) Per Cederqvist ＠ Pike (-) developers forum 13 Aug '18

13 Aug '18

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. When running "make documentation" on the current tip of the 8.1 branch, (commit 73945f040279bfe66d), you get this error message: > /home/cederp/rgit/pike/src/cpp.c:5918..5921: DocParser error: @expr{ without matching @} > > ERROR: <Invalid error container: Tools.AutoDoc.AutoDocError(SourcePosition(File: /home/cederp/rgit/pike/src/cpp.c, lines: 5918..5921), "DocParser", "@expr{ without matching @}")> The resulting ./build/linux-3.13.0-153-generic-x86_64/doc_build/src/cpp.c.xml file contains a single newline. However, the extract_autodoc command used exit code 0, so it didn't fail. (In this case, a later make command fails, but I've seen cases where the entire build succeeds -- but maybe that wasn't in the Pike tree.) The patch below is one way of making sure that extract_autodoc fails. Maybe there are better ways. diff --git a/lib/modules/Tools.pmod/Standalone.pmod/extract_autodoc.pike b/lib/modules/Tools.pmod/Standalone.pmod/extract_autodoc.pike index a3fb82645c..a346f9a132 100644 --- a/lib/modules/Tools.pmod/Standalone.pmod/extract_autodoc.pike +++ b/lib/modules/Tools.pmod/Standalone.pmod/extract_autodoc.pike @@ -717,6 +717,8 @@ string extract(string filename, string imgdest, if (!verbosity) ; werror("\nERROR: %s\n", describe_error(err)); + if (!(flags & Tools.AutoDoc.FLAG_KEEP_GOING)) + exit(1); // return 0; } And the actual documentation markup error is trivial to fix: diff --git a/src/cpp.cmod b/src/cpp.cmod index 3b98d89746..440dceb3c7 100644 --- a/src/cpp.cmod +++ b/src/cpp.cmod @@ -5018,7 +5018,7 @@ static void insert_callback_define_no_args(struct object *cpp_obj, *! it will default to @expr{"-"@}. *! *! @param charset - *! Turn on automatic character set detection if @expr{1}, otherwise + *! Turn on automatic character set detection if @expr{1@}, otherwise *! specifies the character set used by the input. *! Defaults to @expr{"ISO-10646"@}. *!

2 2

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 August 2018