Pike-devel

pike-devel@lists.lysator.liu.se

2 participants
3046 discussions

ADT.Set does not support ^; & operator fails in hilfe
by Martin Bähr 10 Oct '11

10 Oct '11

> ADT.Set AAS = ADT.Set(({ "John", "Serena", "Bob", "Mary", "Serena", "Bob" })); > ADT.Set BAS = ADT.Set(({ "Jim", "Mary", "John", "Jim", "Bob", "Mary" })); > AAS^BAS; Operator not in object. Unknown program: `^(ADT.Set({ /* 4 elements */ "Bob", "Serena", "John", "Mary" }),ADT.Set({ /* 4 elements */ "Bob", "John", "Mary", "Jim" })) HilfeInput:1: HilfeInput()->___HilfeWrapper() the error below only appears in hilfe: > AAS&BAS; Compiler Error: 1: Undefined identifier AAS. Compiler Error: 1: Undefined identifier BAS. Compiler Error: 1: Too few arguments to `& (got 0). Compiler Error: 1: Expected: array | mapping | multiset | object | program | string | type(mixed) | int | mixed. Compiler Error: 1: Function type: Compiler Error: 1: Got : scope(0,function((0=mixed) : 0) | function((0=program | type(mixed)) : 0) | function((0=string) : 0) | function((0=multiset) : 0) | function((0=mapping) : 0) | function((0=array) : 0) | function((0=int) : 0) | function(mixed, object, mixed ... : mixed) | function(object, mixed, mixed ... : mixed) | !function(!mapping ... : mixed) & function(array | multiset | (4=mapping) ... : 4) | !function(!(program | type(mixed)) ... : mixed) & function((1=program | type(mixed)), (2=program | type(mixed)) ... : 1 | 2) | !function(!string ... : mixed) & function((1=string), (2=string) ... : 1 | 2) | !function(!multiset ... : mixed) & function((1=multiset), (2=multiset) ... : 1 | 2) | !function(!mapping ... : mixed) & function((1=mapping), (2=mapping) ... : 1 | 2) | !function(!array ... : mixed) & function((1=array), (2=array) ... : 1 | 2) | !function(!int ... : mixed) & function((1=int), (2=int) ... : 1 | 2)). greetings, martin.

1 0

Re: Possible bug walking a GTK2.TreeModel in 7.9
by Lance Dillon 22 Sep '11

22 Sep '11

----- Original Message ---- > From: larcky <pclar7(a)yahoo.co.uk> > To: pike(a)roxen.com > Sent: Thu, September 22, 2011 3:17:33 AM > Subject: Possible bug walking a GTK2.TreeModel in 7.9 > > Hi > This works fine in Pike 7.8 but 7.9 crashes with a Segmentation Fault. I > think the problem's with GTK2.TreeModel->iter_next(). I can get the first > row OK but then the iterator becomes invalid. > Thanks, larcky > I believe I see the problem. In 7.9, in gtktreemodel.pre, function iter_next, it was changed to push the iter onto the stack, to return it. This way you can possibly do things like iter2=tm->iter_next(iter). The problem is that iter gets modified in place by gtk_tree_model_iter_next(), so it is there, then it gets pushed onto the stack also. So the same GtkTreeIter is present twice, once in the original object, and another on the stack. When the one on the stack doesn't get assigned to anything, it gets free'd by gtk, so the original iter gets free'd also. Then when you try to use it again, possibly the memory is fine and hasn't been overwritten yet, but when it tries to free it again, it gets the double free. 7.9 needs to be changed to either copy the iter, or to not return it. Does anybody have a preference? I don't think the copy would be the right thing to do, because it would usually consist of a copy and a free anyway, because you won't probably won't use the old one once you have the next one. I don't think there is any way to do it otherwise because gtk_tree_model_iter_next() replaces the iter, it doesn't return the next one as a new iter, leaving the old one alone.

1 1

Re: Val.true and Val.false [Was: XMLRPC] (from pike@roxen.com)
by Lance Dillon 11 Sep '11

11 Sep '11

Patch for boolean support for Protocols.XMLRPC --- module.pmod.orig 2011-08-31 16:02:19.838058384 -0400 +++ module.pmod 2011-09-07 10:17:21.848427570 -0400 @@ -15,12 +15,15 @@ //! Pike @expr{mapping@} is translated to XML-RPC @tt{<struct>@}. //! Pike @expr{array@} is translated to XML-RPC @tt{<array>@}. //! Pike @[Calendar] object is translated to XML-RPC @tt{<dateTime.iso8601@}. +//! Pike @expr{Val.false@} and @expr{Val.true@} is translated to +//! XML-RPC @tt{<boolean>@}. //! //! Translation rules for conversions from XML-RPC datatypes to Pike //! datatypes: //! -//! XML-RPC @tt{<i4>@}, @tt{<int>@} and @tt{<boolean>@} are -//! translated to Pike @expr{int@}. +//! XML-RPC @tt{<i4>@} and @tt{<int>@} are translated to Pike @expr{int@}. +//! XML-RPC @tt{<boolean>} is translated to Pike @expr{Val.true@} and +//! @expr{Val.false@}. //! XML-RPC @tt{<string>@} and @tt{<base64>@} are translated to //! Pike @expr{string@}. //! XML_RPC @tt{<double>@} is translated to Pike @expr{float@}. @@ -225,8 +228,9 @@ return sizeof(data)?data[0]:""; case "i4": case "int": - case "boolean": return (int)(data*"") || magic_zero; + case "boolean": + return ((int)(data*""))?Val.true:Val.false; case "double": return (float)(data*""); case "string": @@ -274,7 +278,7 @@ ({ "&", "<", ">", """, "'", "" })); } -protected string encode(int|float|string|mapping|array value) +protected string encode(int|float|string|mapping|array|object value) { string r = "<value>"; if(intp(value)) @@ -303,6 +307,8 @@ else if (objectp (value) && value->format_iso_short) r += "<dateTime.iso8601>" + value->format_iso_short() + "</dateTime.iso8601>"; + else if (objectp(value) && (value->is_val_true || value->is_val_false)) + r += sprintf("<boolean>%d</boolean>",(int)value); else error("Cannot encode %O.\n", value); return r+"</value>\n";

3 16

Re: Val.true and Val.false [Was: XMLRPC] (from pike@roxen.com)
by Lance Dillon 10 Sep '11

10 Sep '11

Okay I'll take care of that this afternoon. Sent from Yahoo! Mail on Android

1 0

pikefarm
by Lance Dillon 09 Sep '11

09 Sep '11

It looks like pikefarm isn't valid anymore. I went to this page: http://pike.ida.liu.se/development/pikefarm/7.8.xml, and it looks like the latest build was on 2010-10-01 16:15:54 (1197). Is it still being used, or is there a different url to go to?

1 0

Re: Val.true and Val.false [Was: XMLRPC]
by Lance Dillon 07 Sep '11

07 Sep '11

> > > Looks ok, but could you please update the docs accordingly as well? > > > > Getting (optional) boolean support when decoding would be nice from a > > feature and symmetry perspective, but that's not a requirement imo. > > > > > In order to backport Val.pmod to 7.8.526, I had to remove Null, because >it > > > references Builtin.Null, which doesn't exist. > > > > Right. That shouldn't be a problem in this case. > > > That last patch was for 7.8.526 with Val.pmod backported (meaning, minus Val.Null) to add boolean support to Protocols.XMLRPC using Val.

1 0

Mapping mixup
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 06 Sep '11

06 Sep '11

We've seen this nasty little issue. The following code class C { mapping options = ([1:1]); void create() { werror("%O\n\n", options); } } void main() { C c = C(); c->options[3] = 3; C cc = C(); } will result in nilsson@riaa:~$ pike --dumpversion 7.9.5 nilsson@riaa:~$ uname -a Linux riaa 2.6.38-10-generic #46-Ubuntu SMP Tue Jun 28 15:07:17 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux nilsson@riaa:~$ pike test.pike ([ /* 1 element */ 1: 1 ]) ([ /* 2 elements */ 1: 1, 3: 3 ]) thought it works fine on nilsson@khora:~$ pike --dumpversion 7.9.5 nilsson@khora:~$ uname -a Linux khora 2.6.32-28-generic #55-Ubuntu SMP Mon Jan 10 21:21:01 UTC 2011 i686 GNU/Linux nilsson@khora:~$ pike test.pike ([ /* 1 element */ 1: 1 ]) ([ /* 1 element */ 1: 1 ])

3 12

Re: Calendar.Month / Calendar.Hour
by Marc Dirix 23 Aug '11

23 Aug '11

On 04/12/2011 11:05 AM, Mirar @ Pike developers forum wrote: > That's an old bug that I thought would be fixed by now. Pike optimizes > the + call and calls `+ with more than one argument. The Calendar > module ignores all other arguments than the first. > > (I think it's that one anyway.) Ok, then I have to wait for the new debian package (still on 7.8.352)

8 12

7.8 segfault
by Bill Welliver 28 Jun '11

28 Jun '11

I've migrated a fairly complex application that was running fine under Pike 7.6 and am getting a number of different situations that cause segfaults. I'm not able to completely rule out the possibility that there's a non-core pike c-module that may be to blame, but the module code has been running well and without any problems of this sort for a number of years. The GDB backtraces look like this: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -145934672 (LWP 2582)] 0x081276e5 in low_object_index_no_free (to=0xffaaad58, o=0x88bfa78, f=67) at /root/Pike-v7.8.352/src/object.c:1252 1252 add_ref(to->u.dummy=dummy); (gdb) bt #0 0x081276e5 in low_object_index_no_free (to=0xffaaad58, o=0x88bfa78, f=67) at /root/Pike-v7.8.352/src/object.c:1252 #1 0x08133599 in index_no_free (to=0xffaaad58, what=0xf720f260, ind=0xffaaad60) at /root/Pike-v7.8.352/src/operators.c:87 #2 0x08076d57 in opcode_F_STRING_INDEX (arg1=702) at /home/zino/hack-local/Pike/7.8-distmaker/src/interpret_functions.h:1854 #3 0xf61c8a04 in ?? () #4 0x000002be in ?? () #5 0xf7610160 in __after_morecore_hook () from /lib/libc.so.6 #6 0xffaaad88 in ?? () #7 0x08a03870 in ?? () #8 0x00000000 in ?? () Any suggestions? This is 7.8.352 on an intel atom (64-bit debian). Best, Bill

2 1

possible sscanf misfeatures
by H. William Welliver III 22 Jun '11

22 Jun '11

I don't recall if anyone else has reported the following problems with sscanf() or not. I'm using 7.8.352 and having the following problems: 1. The + and - modifiers to %c don't seem to work in combination, even though it seems reasonable that one might want to decode a signed value in big endian order. Separately they work fine. 2. The - modifier does not work with %F. I'm currently using a workaround of reading in the bytes as an array, reversing them and then feeding them back into sscanf(). Bill

5 16

Jump to page:

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