Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

module can change mappings and multisets but not arrays or other types?
by Martin Bähr 08 Aug '05

08 Aug '05

hi, while playing around with modules, i observed the following: variables in modules are readonly, when accesses directly, and trying to change them from the outside gives an error. however trying to change then from the inside is either silently ignored or succeeds: int i=7; string s="foo"; mapping dict = ([ "foo":8 ]); array list = ({ 5 }); multiset mset = (< "foo" >); void set(mixed var) { // ignored: i=(int)var; s[0]=((string)var)[0]; dict += ([ "baz":var ]); list +=({ var }); list[0] = (int)var; // succeeds: dict->foo=var; dict->bar=var; mset[var] = 1; mset += (< var >); } shouldn't all of them fail and produce an error? greetings, martin.

7 12

GTK.DrawingArea won't work.
by 墳墓 07 Aug '05

07 Aug '05

I'm trying to develope my application with Pike and GTK, but when I used GTK.DrawingArea to draw a line, it doesn't work. I'm not sure if I misused GTK.DrawingArea, because I can't find example program that also use DrawingArea Error message and my code listed below, any suggestion? It says: Gdk-CRITICAL **: file gdkgc.c: line 51 (gdk_gc_new_with_values): assertion `window != NULL' failed. Gdk-CRITICAL **: file gdkgc.c: line 456 (gdk_gc_set_foreground): assertion `gc != NULL' failed. Gdk-CRITICAL **: file gdkdraw.c: line 65 (gdk_draw_line): assertion `drawable != NULL' failed. Here is my code: #!/usr/bin/pike int main () { GTK.setup_gtk(); GTK.Window MainWin = 0; GTK.Widget w = GTK.DrawingArea()->set_usize(100,100); GDK.GC gc = GDK.GC(w)->set_foreground( GDK.Color(255,0,0) ); w->draw_line ( gc , 10 , 10 , 100 , 100 ); MainWin = GTK.Window ( GTK.WINDOW_TOPLEVEL ); MainWin->set_title ( "Testing" ); MainWin->add ( w ); MainWin->show_all(); GTK.main(); return 0; }

2 2

http://pike.ida.liu.se/ down?
by Martin Bähr 05 Aug '05

05 Aug '05

hi, the webserver on http://pike.ida.liu.se/ seems to be down. any ideas what's wrong? the host is reachable, ssh is answering, although i can not log in, which i could before. that suggests that pike.ida.liu.se is pointing to a different (or freshly installed) machine. greetings, martin.

4 4

New feature: Tools.Monger
by Bill Welliver 28 Jul '05

28 Jul '05

I've placed the first version of the unbundled Monger tool up on the modules.gotpike.org website. Unbundling the monger tool is the first step toward making all Pike modules available outside the pike distribution. This first release offers significant new functionality for developer types, in that it allows a certain amount of change functionality when working with the remote module repository. In fact, this functionality was used to create the new version of Tools.Monger and upload its source using Tools.Monger.MongerDeveloper. As of right now, you'll have to create a new module using the web interface. I think that the most dangerous situations are caught, but please don't purposely try to crash the repository :) Here's an example: > object m = Tools.Monger.MongerDeveloper(); > m->set_auth("joedeveloper", "pikerulez"); (1) Result: 0 > m->add_new_version("Tools.Monger", "7.6.28", "This is the first functional unbundled release of the Monger tool.\nThis version includes developer functionality, such as version creation,\ndependency functionality, and source upload.", "GPL/LGPL/MPL"); (2) Result: 1 > m->set_dependency("Tools.Monger", "7.6.28", "Pike", "7.6.0", "7.7.999", 1); (3) Result: 1 > m->set_module_source("Tools.Monger", "7.6.28", "Tools_Monger-7.6.28.tar.gz"); (2) Result: 1 > quit To get the new release, use this command with any 7.6.6 or higher release of Pike: pike -x monger --install Tools.Monger You may need to remove your Tools.pmod/Standalone.pmod/monger.pike.o file if you get annoyed at the out of date warning messages. Obviously, this is just a first step, and so there are some things that are less than ideal, but I think it's a big step in the right direction for users and developers. As always, comments and suggestions are welcome. Bill

1 0

7.6 release
by Bill Welliver 28 Jul '05

28 Jul '05

OK, I've extracted the majority of changes from the changelog. Anyone care to look through my work to see if i've missed anything? After that, what's next in getting a new release out the door? Bill

5 4

pike terminology: parent/child, super/sub or base/derived?
by Martin Bähr 27 Jul '05

27 Jul '05

hi, what is the preferred terminology for pike documentation: parent and child class super and subclass base and derived class ? i am kinda leaning towards parent/child. greetings, martin.

3 2

Changes
by Bill Welliver 25 Jul '05

25 Jul '05

I've started going through the changelog since 7.6.24. I checked in what I have so far; please take a look to make sure your change is properly described (I'm not finished yet, so consider these preliminary). Also, I'm not sure, but it looks like there might be some missing entries for previous 7.6 releases. Can anyone confirm or deny that? Thanks, Bill

2 1

automap: [*] not supported here. bug?
by Martin Bähr 23 Jul '05

23 Jul '05

hi, can you explain why: random(allocate(3,9)[*]); or random(({9,9,9})[*]); don't work, while array foo = allocate(3,9); random(foo[*]); does? greetings, martin.

6 13

Re: Pike 7.6
by Peter Bortas ＠ Pike developers forum 23 Jul '05

23 Jul '05

>so while it would be nice to have in 7.6, It would, and I want it there, but it needs to sit in 7.7 for a while so people get a sproting chance at checking out the interface before it's cast in stone.

1 0

Binary size
by Martin Nilsson (DivX Inc.) ＠ Pike (-) developers forum 23 Jul '05

23 Jul '05

Something strange has happened with the pike 7.7 binary during the last month or so. It used to be 4.6 MB, but is now 15.4 MB when looking with ls. Using size however tells that the text segment is down 34k and the rest remains unchanged since May. What's the padding?

3 2

Jump to page:

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