Pike-devel

pike-devel@lists.lysator.liu.se

3 participants
3048 discussions

Overlapping ranges
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 19 Feb '03

19 Feb '03

Pike v7.5 release 3 running Hilfe v3.5 (Incremental Pike Frontend) > array_sscanf("hej", "%[\x6dd\x70f\x780]"); Overlapping ranges in sscanf not supported. HilfeInput:1: HilfeInput()->___HilfeWrapper() > Sorry? Where is the range, and what is it overlapping with? If I remove either of the three characters from the set, the code works...

1 0

String.Bootstring
by Martin Nilsson (�skblod) ＠ Pike (-) developers forum 18 Feb '03

18 Feb '03

What is a Bootstring? Both the testsuite and the documentation appears to be somewhat lacking in describing this class.

3 3

Sql.[Ss]ql
by rjb ＠ Pike developers forum 18 Feb '03

18 Feb '03

OK, I know that by current conventions, the class's name should be Sql.Sql. Still, Sql.sql used to resolve to the same program in 7.2, and probably -- up to some point -- in 7.3... but no more. That is, Sql.sql returns zero.

2 1

Extending autodocs (2nd try)
by Xavier Beaudouin 18 Feb '03

18 Feb '03

Hello, As maintainer of Caudium, I'd like to use pike autodocs for : - caudium modules - tags - containers - entities I'd like to know if current pike autodocs can be extended to handle such extensions, if yes is there any examples / plugins or some docs (except as usual "use the source luke") to handle that. Note this part is really a *wanted* feature for others projects like sTeam, and maybe this should be "a plus" for Roxen as well. Sincerly, /Xavier -- Xavier Beaudouin - Unix System Administrator & Projects Leader. Please visit http://caudium.net/, home of Caudium & Camas projects O ascii ribbon campaign against html email |\ and Microsoft attachments

5 6

unnecessary tpike
by David Hedbor ＠ Pike developers forum 18 Feb '03

18 Feb '03

So, I'm compiling with icc. Problem is that with icc, linking is slow when you have IPO enabled since it performs multi-file optimizations. Pike will ALWAYS create a tpike binary even though there is a working Pike installed (so that step is unnecessary). It adds a significant time to the compilation (several minutes I'd guess). How about, if possible, use the system-installed Pike to run the generation of peep.c etc, skipping the redundant 'tpike' step. I can understand why there's been no optimizations done here since in general it doesn't take a whole lot of time.

5 11

setsid
by Peter Bortas ＠ Pike developers forum 16 Feb '03

16 Feb '03

I have a sudden urge to remove the only expect script on my systems. To do that I have to be able to set passwords with Solaris passwd. I've tried this once before, and failed. Short version of the expect script: ----8<------------------------------------- spawn /usr/bin/passwd -r nis $uname expect { -re assword: { send "$password\n" } } expect { -re assword: { send "$password\n" } } expect { eof { wait } } ----8<------------------------------------- In pike that should be something like this: ----8<------------------------------------- #!/usr/bin/env pike array(Stdio.File) make_ptypair() { Stdio.File pf = Stdio.File(), tf = Stdio.File(); foreach(get_dir("/dev/"), string pty_name) if(pty_name[..2]=="pty" && pf->open("/dev/"+pty_name, "rw")) { if(tf->open("/dev/t"+pty_name[1..], "rw")) return ({ pf, tf }); pf->close(); } return 0; } int main() { string luser = "victim"; array(Stdio.File) f = make_ptypair(); if(!f) { werror("No PTYs available.\n"); return 1; } object p = Process.create_process( ({ "/usr/bin/passwd", luser }), ([ "setsid":f[1] ]) ); f[1]->close(); f[0]->write("bogus\n"); f[0]->write("bogus\n"); return p->wait(); } ----8<------------------------------------- But no, that still gives the password question on the command line: [root] ./setsid.pike New password: Any ideas?

6 20

pike poster design?
by Martin Baehr 16 Feb '03

16 Feb '03

hi, sTeam will be present at the CeBit in germany next month. since it is a pike application i would like to use the opportunity and also advertize pike itself. unfortunately i don't have any design skills. is there any one among this group who might help us out with designing a poster that can be used at various events, such as the CeBit, linux expos/conferences, the pike conference or others? (only a digital rendition would be needed, as we have printing facilities at the university) having such a poster would help the pike project a great deal greetings, martin.

3 3

SDL on NT
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 14 Feb '03

14 Feb '03

post_modules/SDL/configure.in in 7.4 contains this oddity: if test x"$pike_cv_sys_os" = xWindows_NT ; then enable_sdltest=no fi It causes builds to fail completely on NT systems that doesn't have SDL installed (e.g. http://pike.ida.liu.se/development/pikefarm/ result.xml?id=123_15&pike=7_4). If the SDL test doesn't work for some reason, isn't it better to give --disable-sdltest on the specific systems where it's known to be installed?

2 2

Protocols.HTTP.Session
by Mirar ＠ Pike developers forum 14 Feb '03

14 Feb '03

I started to write a Protocols.HTTP.Session class. The goal is an interface to keep cookies throughout a session, and in the future to reuse keep-alive connections, as well as adding better methods for async operations. It can also follow redirects automatically. Example (the Elfwood initial page redirects to the main page if a cookie is set, and it is the first time): | > object s=Protocols.HTTP.Session(); s->get_url("http://elfwood.lysator.liu.se/"); s->get_url("http://elfwood.lysator.liu.se/"); | (1) Result: Request("http://elfwood.lysator.liu.se/" - connected - 361 bytes recieved) | (2) Result: Request("http://elfwood.lysator.liu.se/elfwood.html" - connected - 343 bytes recieved) (Sidenote: What's the autodoc keyword for known bugs? Am I right in guessing it was @known_bugs?)

2 2

Re: Weird problem with Image.SVG in Pike 7.4/7.5
by David Hedbor ＠ Pike developers forum 13 Feb '03

13 Feb '03

Again, gdb/strace output would be good. That way there would be a way to see where it actually dies. By the way, an unrelated suggestion - how about adding support for the 'backtrace()' system call on platforms where it's available? It can be used to, on crashes (or demand) craate a stack trace such as this: Stack dump: { /lib/i686/libpthread.so.0 [0x4003710c] /lib/i686/libc.so.6 [0x401684c8] majesty(Read__17CYLinuxFileSystemiPvUl+0x1d) [0x8268bc1] majesty(Unserialize__11CYLibHeaderi+0x2b) [0x8200b8b] majesty(__11CYLibHeaderi+0x2e) [0x82017d6] majesty(AddLibrary__12CYLibManagerRC8CYString+0x14e) [0x820469e] majesty(AddStaticCAMs__Fv+0x6b) [0x830f0e7] majesty(main+0x5bf) [0x81dcbfb] /lib/i686/libc.so.6(__libc_start_main+0xa2) [0x401573e2] majesty(XMapRaised+0x31) [0x81368b1] } It's very specific to Linux (afaik) but can prove very useful when trying to debug someone elses problem (i.e it's more information than you would have received otherwise). / David Hedbor Previous text: >2003-02-12 22:31: >Subject: Re: Weird problem with Image.SVG in Pike 7.4/7.5 >-------------------------------------------------------------------- >I have just confirmed the suspicion - code compiled with gcc 2.95 and full >optimization works fine. So, now to see what gets overoptimized with gcc 3.2 >-O2 > >marek > > > / Brevbäraren >

4 7

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