Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

pikefarm and code librarian no longer seeing updates from cvs?
by Martin Bähr 08 Apr '08

08 Apr '08

hi, code librarian and pikefarm are not picking up any changes from cvs since this morning. any ideas what could be the issue? greetings, martin.

4 5

Re: [Patch] pike -x
by bertrand.lupart＠linkeo.com 29 Mar '08

29 Mar '08

> I can't say much intelligent about this patch, but it looks like an > improvement. Since noone else has shown any interest I've committed it > to 7.7 so it doesn't get lost in time. Thanks! Thank you. -- Bertrand LUPART http://bertrand.gotpike.org/

1 0

[Patch] pike -x
by bertrand.lupart＠linkeo.com 28 Mar '08

28 Mar '08

Hello, Here's a patch for having a more clear error message and abort if the specs file isn't present at the expected location when running "pike -x monger --install" for example. The current error is actually a user-unfriendly backtrace. Maybe the check for this file could be moved elsewhere, since before checking for the specs file, monger select the good version of the software to install and downloads it. ----8<----8<----8<----8<---- --- Tools.pmod/Standalone.pmod/module.pike.ori 2008-03-18 15:32:11.000000000 +0100 +++ Tools.pmod/Standalone.pmod/module.pike 2008-03-18 15:50:42.000000000 +0100 @@ -194,6 +194,14 @@ int main(int argc, array(string) argv) { + string specspath=include_path+"/specs"; + + if(!Stdio.is_file(specspath)) + { + werror("Missing specs file at %s\n",specspath); + return 1; + } + run_pike = master()->_pike_file_name; #ifdef NOT_INSTALLED run_pike += " -DNOT_INSTALLED"; @@ -205,7 +213,7 @@ run_pike += " -m"+master()->_master_file_name; putenv("RUNPIKE", run_pike); - load_specs(include_path+"/specs"); + load_specs(specspath); foreach(Getopt.find_all_options(argv,aggregate( ({"autoconf",Getopt.NO_ARG,({"--autoconf"}) }), ---->8---->8---->8---->8---- -- Bertrand LUPART http://bertrand.gotpike.org/

2 1

Compiler/interpreter feature request
by cschalkwijk 27 Mar '08

27 Mar '08

I don't know if it's already available (if so: I'd like to know) but I'd like to receive warnings about unused variables/objects/methods in Pike. Is this possible? Next to that: is there any progress with the Pike Eclipse plugin? (What was the url again?) Greetings, Coen __________________________________________________________ Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken. The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system. __________________________________________________________

3 2

libffi and java-static elements
by H. William Welliver III 25 Mar '08

25 Mar '08

Did I understand correctly that libffi will be a bundle in Pike 7.8? If so, that makes it easier for me to include the Objective-C module directly in Pike. Also, I vaguely recall some additions to 7.7 that seemed to suggest java-static elements were coming at some point, too. Did I misunderstand that? If I didn't what is the current status? Right now, the Objective-C makes (inappropriate) use of function constants to make "class" methods appear in classes. Bill

3 3

Re: libffi and java-static elements
by Peter Bortas ＠ Pike developers forum 25 Mar '08

25 Mar '08

There was some checkins to support it, but nothing besides that yet.

1 0

Difference in execution speed
by cschalkwijk 25 Mar '08

25 Mar '08

I was wondering, which is faster (in Pike) or are they eventually the same? if(search(someArray, someElt) < 0){;} or if(search(someArray, someElt) == -1){;} If one is faster, why? Greetings, Coen __________________________________________________________ Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken. The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system. __________________________________________________________

6 10

rot13
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 24 Mar '08

24 Mar '08

Appearently Crypto.Substitution()->set_rot_key(13)->encrypt(x) was too difficult to find so eMBee added String.rot13(), though 17 times slower. I obviously has an opinion as Crypto co-author, but I think it is reasonable to have ROT13 in the Crypto module instead of String.

3 3

Filenames in the Pike CVS repository are now valid UTF-8
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 19 Mar '08

19 Mar '08

FYI: I doubt that anyone will notice (or care :-)), but I've just renamed the few files in Pike that contained 8-bit characters, so that they may be stored on filesystems that enforce UTF-8 encoding (eg HFS or ZFS). The only files affected were the (deleted) file src/modules/image/doc/säljstöd.html in Pike 0.5, 0.6, 7.0, 7.2 and 7.4, and the external pike-module µpgp/µpgp.pike.

3 3

Git 101 revised for pikers
by Stephen R. van den Berg 18 Mar '08

18 Mar '08

A.S. After toying with git some more, I revised the recommended instructions to follow the mirror(s) apt-get install git-core git clone git://git.cuci.nl/pike cd pike git gc git branch -r # List available active remote branches # dead branches are available as # tags (like: 7.5 or ulpc.old) git checkout -f origin/7.7 git branch -f master # This creates your own development # branch called "master" # tracking official version 7.7 git checkout -f master git log master git log origin/7.7 git log origin/7.6 git log origin/7.4 Now edit around, and commit changes using: git commit -a -m "Some useful one-line-description" and repeat as often as needed (of course). In order to update the mirror from upstream (my repository, where you cloned from), simply run: git fetch every once in a while. After doing so, perform: git rebase origin/7.7 to actually move forward your own "master"-branch changes so they are automatically merged and (re)based onto the latest (official) updates from 7.7 Pushing back the changes into the official release involves using CVS (externally from git) still. The native git mechanisms cannot be used for that until the official repository is also changed to git. The nice thing about git is that merges from the developmentbranch back into older stable branches are seemless and fully annotated. These advantages however, cannot be used until git is used natively. In theory, the merges could be retro-fitted into the branches, but there currently is no automated way of doing that to the existing tree (it can be done manually, git allows all kinds of "afterward fixing"). ------------------------------------- For Roxen/Caudium/Chilimoon, try the above with: git clone git://git.cuci.nl/roxen git branch -r Then pick either: origin/5.0 # for Roxen development branch origin/caudium # for Caudium development branch origin/chilimoon # for Chilimoon development branch -- Sincerely, srb(a)cuci.nl Stephen R. van den Berg (AKA BuGless). "Good moaning!"

5 7

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