Pike-devel

pike-devel@lists.lysator.liu.se

3 participants
3048 discussions

Start a nNew thread

dumpmaster
by Martin Nilsson (lambda) ＠ Pike (-) developers forum 06 Jun '03

06 Jun '03

Why is the program that dumps the master so bare bones?

2 1

configure problem with Freebsd
by David Gourdelier 03 Jun '03

03 Jun '03

Hi, I am having problems with Pike 7.4 on Freebsd 4.7. The problem is that it sources /etc/make.conf but make.conf is not really sourceable (at least on my system). It contains things like BDECFLAGS= -W -Wall or CPUTYPE=i386 and source /etc/make.conf reports errors in this case (morever i don't remember modifying make.conf). Another thing is: /configure --disable-make.conf configure: error: make.conf: invalid feature name -- David Gourdelier

3 3

New encoder
by Martin Nilsson (lambda) ＠ Pike (-) developers forum 03 Jun '03

03 Jun '03

It appears that the new encoder hangs most systems running "make verify" during precompilation of the test pike. That is bad, since there is no watchdog running during the installation phase.

3 4

Re: Pike Cookbook
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 01 Jun '03

01 Jun '03

In case this wasn't 100% clear from the original post, I meant include the actual stat() call in the solution as well. It doesn't make it much longer, just much better. :-)

1 0

Pike Cookbook
by Martin Nilsson (har bott i google) ＠ Pike (-) developers forum 01 Jun '03

01 Jun '03

Johan Sundström and I are about to make some attempts to make a Pike Cookbook. Regardless if we have the strength to make it all the way into a book or not, I think this is a good project to spend some time on. While we can get some ideas what this cookbook should contain by looking at e.g. the Perl and Python cookbooks, much of what is in them deals with how to solve problems that are inherit in the langauges themselves. As a consequence we would like to know what problems you have with Pike and how you solve them (if you have). Johan and I will set up some sort of database or repository and collect the responses as well as inserting our own stuff. We will probably aim at getting the same basic layout as in the present cookbooks in the database, e.g.: ----------------------8<-------------------- Title: Hello World Contributor: Martin Nilsson Problem: Make a program that prints Hello World! and exits. Solution: int main() { write("Hello World!\n"); } Discussion: The above code is probably the smallest possible program, counting tokens, that solves the problem. Without unessecary white spaces this is 36 characters. A more "proper" solution would however be: int main(int argc, array(string) args, array(strings) env) { write("Hello World!\n"); return 0; } Here all the passed arguments are received in fairly typed variables, which you don't have to do. I say fairly typed, because there is always at least one argument passed to the program, the path of the program itself, so argc could be declared as int(1..). After the interesting code has been executed 0 is returned, as result code of the program. There is an implicit return 0; at the end of every function, which we relied on in the first code. Since the return value is always 0, the main function could be declared to return int(0..0). Since the Pike master only feeds positive return values from main into an exit call, return 0; can be replaced with exit(0);. While this doesn't really matter here it does matter if we chose another aproach for this program all together. When Pike executes a script it first loads the file and compiles it into a program. Then it instansiate an object from the program and call its main function. Thus we can put our code in the object constructor and when finished exit Pike, so it doesn't find out that the main function is missing. void create() { write("Hello World!\n"); exit(0); } ----------------------8<-------------------- So please give us your thoughts, problems and solutions, either here or as private messages.

8 26

'-g' is forbidden in paths...
by David Hedbor ＠ Pike developers forum 01 Jun '03

01 Jun '03

This brilliant code: CFLAGS="`echo $(CFLAGS) | sed -e 's/-g//g' -e 's/-W[^ ]*//g'`" \ In the GL and GTK Makefile.in's don't do what you'd want them to do when your directory is named, for example: /mnt/disk3/src/pike/7.4/build/linux-2.4.20-gaming-r3-i686 What are the reasons for the forced removal of -g and other stuff anyway?

3 3

Codec
by Martin Nilsson (lambda) ＠ Pike (-) developers forum 31 May '03

31 May '03

In the new Codec, isn't it better to prefix strings with "\1", "\2" etc instead of "s", "p" etc, to ensure no interference with resolving e.g. q->p->r? Also, should we make the module dumper a Standalone Tool (i.e. NOT making it standalone but part of Pike), so that one can do "pike -x dump my_module.pmod"? Another idea is that "pike -x dump" redumps all module directories.

2 3

dumping modules
by rjb ＠ Pike developers forum 30 May '03

30 May '03

I tried running dumpmodule.pike on some of my .pmod's, with the result: -rw-r--r-- 1 rjb rjb 55029 May 21 11:23 PiXPull.pmod -rw-r--r-- 1 rjb rjb 82157 May 28 11:43 PiXPull.pmod.o -rw-r--r-- 1 rjb rjb 18221 May 21 11:23 PiXTree.pmod -rw-r--r-- 1 rjb rjb 102525 May 28 11:43 PiXTree.pmod.o Note the funny sizes: the module with much less code gets a significantly larger bytecode dump. Taking a closer look, I concluded that the bytecode for PiXPull.pmod was for some reason getting pulled into PiXTree.pmod.o. Indeed, running `strings' on PiXTree.pmod.o, I found all the string literals used in PiXPull.pmod. In fact, PiXTree.pmod contains the statement `import .PiXPull;', but it's not clear to me whether this should have the above effect. NB modifying PiXTree.pmod to reference .PiXPull.Parser etc. explicitly (instead of using the import) has little effect on the dump. (This is with Pike v7.4 release 21)

2 1

make problems on OpenBSD
by Ian D (spellisteligist) ＠ Pike (-) developers forum 29 May '03

29 May '03

This seems familiar in a way: (GNU Make 3.80, OpenBSD-current, Pike-7.4.20) [ian@bleep Pike-v7.4.20]$ gmake install "Makefile", line 336: Need an operator No closing parenthesis in archive specification "Makefile", line 337: Error in archive specification: "\|void\|constant\|class\)\>)*\|\<\" No closing parenthesis in archive specification "Makefile", line 337: Error in archive specification: "\t]\{1,\}\" "Makefile", line 337: Need an operator sh: syntax error: `(' unexpected "Makefile", line 340: warning: "\|->=?\|<[<=]\|==\|>[=>]\|\[\]=?\|()\|[%-!^&+*<>|~\/]\)\)[ \t]*(/\4/' -r '/" returned non-zero status Fatal errors encountered -- cannot continue gmake: *** [install] Error 1 [ian@bleep Pike-v7.4.20]$

4 3

bug report?
by Ian D (spellisteligist) ＠ Pike (-) developers forum 29 May '03

29 May '03

I couldn't find how to bug report on pike.ida: On OpenBSD > 3.2 (tested on -current), the compiler complains following: /usr/include/malloc.h:4: warning: #warning "<malloc.h> is obsolete, use <stdlib.h>" (same as freebsd, i gather)

2 1

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