Pike-devel

pike-devel@lists.lysator.liu.se

1 participants
3045 discussions

Start a nNew thread

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

www.ohloh.net contributor list
by Stephen R. van den Berg 12 Mar '08

12 Mar '08

For a tiny bit of Pike promotion, and to show that the community is thriving, it might be a good show of hands to put actual accounts behind the contributor list of pike at the following page: http://www.ohloh.net/projects/7336/contributors Also, feel free to update the data on Pike there (or even Roxen/Caudium). The data they're using is the live git mirror I put up for the Pike repository (it tracks bleeding edge pike (7.7), at the moment). -- Sincerely, srb(a)cuci.nl Stephen R. van den Berg (AKA BuGless). "Good moaning!"

4 5

Re: www.ohloh.net contributor list
by H. William Welliver III 12 Mar '08

12 Mar '08

That appears to be the case; It says that caudium has a large percentage of Java code, and that Fins is written predominantly in JavaScript (which it isn't). The counts seem to be based on file extension, so perhaps we should rename all of our code with .php?? :) I find some of the metrics interesting, but there are a lot of flaws behind automated analysis. I wouldn't say that the site is solely designed to permit poaching of developers; but I've always been skeptical of the whole "social networking" thing, so I'm not sure I see the real benefits to putting a lot of effort into it. Bill > Are you sure? I find it hard to believe that 79% of the Roxen code > is written in XML... > > According to a quick wc -l, a fresh Roxen consists of the following: > > C 605 > css 172 > h 1111 > HTML 1987 > Java 4358 > js 1497 > Perl 478 > Pike 166017 > sh 2016 > VBS 78 > XML 49140 > > My guess is that it has just ignored the pike and pmod files.

1 0

Re: follow up: segfault
by Peter Bortas ＠ Pike developers forum 10 Mar '08

10 Mar '08

It's a tentative fix, so 7.7: http://pike.ida.liu.se/development/cvs/diff.xml?module=Pike&file=7.7/src/in…

2 3

Java configure
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 05 Mar '08

05 Mar '08

Pike 7.6 detects that I have Java (-lzip -ljava -ljvm ), but 7.7 doesn't.

2 3

Fully tracked git repositories of Pike/Roxen/Chilimoon/Caudium
by Stephen R. van den Berg 25 Feb '08

25 Feb '08

I've setup 2 permanent and live git-mirrors: one for Pike (called pike) and one for Roxen/Chilimoon/Caudium (called roxen). I.e. they are both synced with the CVS versions at 06:00 every day. For Pike: git-clone git://git.cuci.nl/pike For Roxen/Chilimoon/Caudium: git-clone git://git.cuci.nl/roxen Use "git-branch -r" to view all the tracked branches. E.g. "git-log origin/7.6" to view the complete history of the pike 7.6 tree. As for Pike, I reconnected the source tree beyond what was done in the SVN dump earlier. I.e. all Pike branches now share a common origin and ancestry at Wed Aug 9 10:21:42 1995, the first checkin of ulpc.old. The repositories are clean and complete, and could be used as an instant master if anyone would like to abandon the CVS repositories. Any suggestions as to possible incorrectness of the repositories are welcome. I'm quite proficient with git and reconnecting history at the moment, so any amendments shouldn't take long. Some interesting trivia perhaps: the whole source repository, including all history of all Pike versions is about 36MB in size, and for all Roxen revisions the full-history source repository is about 24MB in size, Caudium adds another 13MB. Incidentally, in trying to sync the old Roxen versions, I got an error in Roxen 1.3, the file /cvs/Roxen/1.3/server/nfonts/32/bell_gothic/bn,v seems to contain a bogus revision number: "unexpected '\x0' reading revision number in RCS file" So that branch is not synced beyond the main developmentline. In order to fix this, either that file needs to be fixed, or deleted (temporarily?) or I'd need a personal copy of the RCS files of 1.3; can any of those options be arranged (mast/grubba?)? P.S. It is, of course, possible to create a "roxen" git without either Roxen or Caudium; but since it (at best) saves you 24MB or 13MB in space, it's not really a big problem. If one should insist, removing the offending tags from the repository, then repacking it, will shrink the size. P.P.S. If anyone wonders why the original git archive is smaller than what you find on your own disk after cloning my versions, that's because you didn't try running "git-repack -d -a -f --window=100" yet. -- Sincerely, srb(a)cuci.nl Stephen R. van den Berg (AKA BuGless). "Good moaning!"

2 3

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