Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

pike -x httpserver (was: Suggestions for a small menu-driven system?)
by Peter Bortas ＠ Pike developers forum 20 Aug '09

20 Aug '09

This discussion reminded me to check in something I've been having in my tree for a few weeks now; A simple HTTP server available as a standalone (-x) tool. The code is 90% written by Per. I just toolified it. % pike -x httpserver --version Pike httpserver 7.8.337 % pike -x httpserver --help Usage: httpserver [flags] [port] Starts a simple HTTP server on port 8080 unless another port is specified. The server will present the contents of the current directory and it's children to the world without and authentication. --version print version information and exit --help display this help and exit % pike -x httpserver Listening on 8080 The idea is taken from Python, as far as that one of my colleagues asked if Pike can do the equivalent of "python -m SimpleHTTPServer". I haven't actually checked out the python code referenced, so I don't know if -x httpserver is feature equivalent. I find it quite handy for transferring files now and then now that I have it. / Peter Bortas Previous text: >17856137 2009-08-19 22:11 /13 lines/ Brevbäraren >Recipients: Pike (-) importmöte för mailinglistan >Comment to 17855679 >Subject: Re: Suggestions for a small menu-driven system? >-------------------------------------------------------------------- >Martin Nilsson (Opera Mini - AFK!) @ Pike (-) importm?te f?r mailinglistan wrote: >>And that that webserver is good enough to be used for several commercial >>products at Opera. > >Any snippets of sample code you (or anyone else) can share for a minimal >server serving some (e.g. html and gifs) files from the filesystem? >-- >Sincerely, > Stephen R. van den Berg. >Currently unemployed programmer: >"What do you mean, I can't initialize things in an assert()?" > > > >(17856137) /Brevbäraren/-------------------------------------------- >

1 0

[typechecking] Expected int, got int|somethingelse
by Peter Bortas ＠ Pike developers forum 20 Aug '09

20 Aug '09

This program: -------8<-------------------------------------- #pragma strict_types void main() { Stdio.Stat s = file_stat("/etc/passwd"); String.int2size(s->size); } -------8<-------------------------------------- Will cause the following complaint: test-int2size.pike:5: Warning: Type mismatch in argument 1 to int2size. test-int2size.pike:5: Warning: Expected: int. test-int2size.pike:5: Warning: Got : function | string | int. which seems a bit unfair.

2 1

nettle depend in pike ebuild
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 17 Aug '09

17 Aug '09

>hey grubba, > >i am using your pike ebuild via layman. seems like nettle2.0 got the >~x86 keyword removed. as it doesnt work yet with pike, maybe you can put >a <=dev-libs/nettle-1.15 into the ebuild dependencies. It should already be there: | $ grep nettle /usr/local/portage/layman/pike/dev-lang/pike/pike-7.8.316.ebuild | DEPEND="<dev-libs/nettle-2 Try running layman -S >best > >arne

2 1

pike -x cflags, include_prefix
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 14 Aug '09

14 Aug '09

Tools.Standalone.cflags prints master()->cflags, which typically equals "-DDYNAMIC_MODULE -I" + dirname(master()->include_prefix). Tools.Standalone.module uses master()->include_prefix directly, however. Explanation? When is Tools.Standalone.cflags meant to be used? "New style" modules? Are sources relying on master()->cflags to be compiled meant to #include <pike/whatever> instead of #include <whatever>?

2 2

Fwd: Protocol.LDAP not working in 7.8?
by Peter Bortas 12 Aug '09

12 Aug '09

Hi, pike-devel-owner handles mailing list stuff. Forwarding to the actual developer list. -- Peter Bortas ---------- Forwarded message ---------- From: Dominik Niehus <nicke(a)uni-paderborn.de> Date: Wed, Aug 12, 2009 at 11:16 PM Subject: Protocol.LDAP not working in 7.8? To: pike-devel-owner(a)lists.lysator.liu.se Hi i have a strange problem with LDAP module in Pike 7.8.316/7.8.337 my simple test program ldap_test.pike : void main () { object ldap = Protocols.LDAP.client("ldap://127.0.0.1"); write("Ldap %O\n", ldap); ldap->bind("cn=admin,dc=test,dc=de","save",3); write("i =" + " " + "Error Strings: " + ldap ->error_string() + "\n"); ldap->set_basedn("ou=org,dc=test,dc=de"); ldap->set_scope(2); object test = ldap->search("(&(uid=test01)(objectclass=person))"); write("Search: %O\n", test); write("Error Strings: " + ldap ->error_string() + "\n"); write("count:" + test->count_entries() + "\n"); write("Result: %O\n", test->fetch(1)); } the result on Pike 7.6.86 Ldap Protocols.LDAP.client("socket", "127.0.0.1:389", 777 /* fd=9 */) i = Error Strings: Success Search: Protocols.LDAP.client("socket", "127.0.0.1:389", 777 /* fd=9 */)->result() Error Strings: Success count:1 Result: ([ /* 8 elements */ "cn": ({ /* 1 element */ "e w01" }), "dn": ({ /* 1 element */ "uid=test01,ou=student,ou=user,ou=upb,ou=asb,ou=org,dc=test,dc=de" }), "givenName": ({ /* 1 element */ "e" }), "objectClass": ({ /* 3 elements */ "person", "organizationalPerson", "inetOrgPerson" }), "sn": ({ /* 1 element */ "w01" }), "uid": ({ /* 1 element */ "test01" }), "userPassword": ({ /* 1 element */ "{crypt}66duJjhG66mss" }) ]) the result on Pike 7.8.316 is: Ldap /${PIKE_MODULE_PATH}/Protocols.pmod/LDAP.pmod/client() i = Error Strings: Success Search: /${PIKE_MODULE_PATH}/Protocols.pmod/LDAP.pmod/client()->result() Error Strings: Success count:1 Result: 0 the result on Pike 7.8.337 Ldap Protocols.LDAP.client() i = Error Strings: Success Suche: Protocols.LDAP.client()->result() Error Strings: Success count:1 Result: 0 Please help! greetings Dominik Niehus

1 0

Pike 7.8.336 alpha
by Peter Bortas ＠ Pike developers forum 10 Aug '09

10 Aug '09

An alpha for the next stable be release can be found here: https://pike.ida.liu.se/download/pub/pike/alpha/7.8.336/ I'm not aware of any issues that should make this anything but a release candidate, but there will be no Windows build today.

2 2

New /.8 Release
by Peter Bortas ＠ Pike developers forum 02 Aug '09

02 Aug '09

I was going to start preparing a new stable yesterday, but my desktop machine (more or less literally) burned up. So I decided to rebuild it and a couple of my test machines with more modern hardware instead. While I make progress on that you should a) make sure the fixes you want in are there, b) not break anything or check in anything potentially dangerous, c) update CHANGES please. I should be done with the hardware bits shortly, so with some luck there should be an alpha late Sunday evening.

2 1

state of debian packages?
by Martin Bähr 01 Aug '09

01 Aug '09

hi, i need pike 7.8 on debian lenny, and to avoid having to reinvent the package myself i would like to just rebuild what's already there. markus, could you maybe upload the current state to experimental? then anyone could simply rebuild for her/his own machine by running apt-source and pdebuild or something like that. i found the debian tree in http://svn.kibibyte.se/pike/trunk/debian/ though, and will use that for now... greetings, martin.

4 6

share_prefix
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 01 Aug '09

01 Aug '09

There's a share_prefix variable mentioned in src/Makefile.in, bin/install.pike and lib/master.pike, but they're not tied together so setting share_prefix on the "make install" command line does nothing. What's the deal with this? Where there any plans that have since been abandoned?

2 2

Nettle deends on m4
by Peter Bortas ＠ Pike developers forum 11 Jul '09

11 Jul '09

I took a look at the remaining failures to build 7.8 in Xenofarm. There are only 2 of them left: "localhost"*: Runs out of memory when exporting documentation. Not much of an issue. "tomoyo": Fails to build Nettle because apparently the libnettle bundle requires m4 to build. Now m4 isn't a very burdensome requirement, but is it supposed to be there for exorted builds? If so I'll just ask the owner of tomoyo to install it, but usually m4 tasks are taken care of when exporting a source package. * Awsome name. I must take a look at the node name generation in the client again.

4 12

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