Pike-devel September 2003

pike-devel@lists.lysator.liu.se

13 participants
60 discussions

Re: Adding PCRE to Pike
by Johan Sundstr�m, Lysator ＠ Pike developers forum 19 Sep '03

19 Sep '03

http://www.bagley.org/~doug/shootout/bench/regexmatch/?cpu / Johan Sundström, Lysator Previous text: >2003-09-19 15:30: >Subject: Re: Adding PCRE to Pike >-------------------------------------------------------------------- >where did you see that? > >greetings, martin. > > > / Brevbäraren >

3 3

Re: Adding PCRE to Pike
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 19 Sep '03

19 Sep '03

I've done a bit of testing myself. The figures one gets depend a lot on the kind of testing, but this is a fairly straightforward case when searching for a submatch that doesn't exist in a large string: Pike: 0.00017900 s Perl: 0.00074000 s Emacs 20: 0.04566600 s Emacs 21: 0.05563044 s TRE: 0.07000000 s GNU Regex: 0.16000000 s The shortcoming in Pikes Regexp is the lack of features, not the speed. / Martin Stjernholm, Roxen IS Previous text: >2003-09-19 15:30: >Subject: Re: Adding PCRE to Pike >-------------------------------------------------------------------- >where did you see that? > >greetings, martin. > > > / Brevbäraren >

2 2

Adding PCRE to Pike
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 19 Sep '03

19 Sep '03

Open question: What problems are there to add PCRE to Pike? Sure it'd be nice to have a regexp package that groks wide strings but since Regexp isn't better in that regard there's nothing to lose.

9 19

time() and optimization again
by Alexander Demenshin 19 Sep '03

19 Sep '03

Hi, Long time ago I posted a message about wrong optimization with time() (and perhaps something else). Nobody replied, and the problem is still present in recent CVS (7.4.27). So here it is again: --- snip --- Just found another bug(?) - the construction like: int ts = time() + 10; while (time() < ts) /* nothing */ ; is wrongly optimized - it doesn't work as expected, i.e. the loop is bypassed - so virtually there is no delay. When I change it to 'while ((n = time()) < ts);' or put something in body, it works. Checked against one day old CVS Pike 7.4 (7.4.17). NB: Is it related to time() only or? :) --- snip --- Also, there is a (slight) inconvenience with time() function. To retrieve current time with high precision I've to use time(2)+2.0, since only this syntax allow to retrieve time with microsecond precision. But, unfortunately, it adds 2 seconds to the result. Sure, extra float op is nothing (almost), but at least inconvenient and misleading. Would it be a good idea to add an extra option (say, negative argument) to return current time as float without using base (which is the case when argument is > 1)? And last about time() :) When Pike is compiled with default float size, its float result is absolutely unrealiable (even wrong) - because of very limited precision (just try: time() - (int)(time(2)+2), the difference will impress you). Yes, I know that there is gethrtime() etc., but I can't use it (directly) with call_out(), for instance (and gethrtime() involves MPI, which is quite slow comparing to floats, even double precision floats). Regards, /Al

9 32

float type weirdness
by Alexander Demenshin 19 Sep '03

19 Sep '03

Hi, I was surprised that float type is somewhat "special", like here: float x = 0.0; // OK, I can live with the fact that I just can't assign "0" :) // However, it would be convenient to make an exception for this // special case (zero) if (!x) something(); // Will be never called, since x is _always_ true // while it is (numerically) is zero (7.4.20) Is this intentional? According to the tutorial: "When Pike encounters an if statement, it first calculates the value of the expression. Pike then checks if this value is true or false. The value zero (0) is considered to be false, and everything else is true." It is not mantioned that "zero" has to be integer zero, and everywhere else (C, Perl etc) float zero is false. Regards, /Al

10 58

ONLY 1 MORE WEEK!!!!!! to the Pike Conference 2003
by Martin Baehr 18 Sep '03

18 Sep '03

Call for Participation and Contributions Pike Conference 2003 - Sep 25-27 Pike In Distributed Knowledge Environments http://pike.ida.liu.se/conferences/2003/ The Pike conference is next week! Have you registered yet? If it isn't to much trouble please take a few minutes to fill out the registrationform, so that we can prepare adequately. http://www.open-steam.org/conferences/pike2003/ http://www.open-steam.org/conferences/pike2003/registration Conference Information: ----------------------- The conference is being held on the 25th to the 27th of september. There is an extension to the 29th for Caudium specific topics. The conference is held at Paderborn University in Germany and with attendees coming from as far as Australia and New Zealand it is set to be a good one! After you have registered, you will be able update your registration details right up until the day of the event. If you have any further questions you may post them on the board inside the conference area after logging in. There will also be a FAQ available on the website in the next few days. Submissions: ------------ Please note that the date for submissions of talks, presentations or workshops has been changed and is now around the 18th of september. Pike: ----- This years conference is titled "Pike in Distributed Knowledge Environments" and we invite Pike programmers all over the world to meet in Paderborn, to discuss and present how Pike is used, what development has been done and what direction that development should take in the future. Caudium: -------- The Caudium extension is the first worldwide meeting of Caudium developers and users, and we invite all of you who wish to be involved in a brief catch-up with what has happened so far in the project, and help choose direction for the future of the project. Any participants of the Pike conference are welcome to join. Cost: ----- This years conference is being kindly sponsored by Paderborn University, however there is a cost to organising these events and a small, as yet undecided fee will be charged to all entrants. Rest assured that we will endeavour to keep it as low as possible. Updates and further information will be available at http://pike.ida.liu.se/conferences/2003/ and http://www.open-steam.org/conferences/pike2003/ Thanks for your time and see you in Paderborn! for the conference team (www.open-steam.org), martin. -- the signature below is unrelated to the announcement -- Pike Conference 2003 - Sep 25-27 - http://pike.ida.liu.se/conferences/2003/ -- interested in doing pike programming, sTeam/caudium/pike/roxen training, sTeam/caudium/roxen and/or unix system administration anywhere in the world. -- pike programmer working in europe open-steam.org unix system- bahai.or.at iaeste.(tuwien.ac|or).at administrator (stuts|black.linux-m68k).org is.(schon.org|root.at) Martin Bähr http://www.iaeste.or.at/~mbaehr/

1 0

Pike 7.4.28
by Martin Nilsson (saturator) ＠ Pike (-) developers forum 18 Sep '03

18 Sep '03

Ok, we have a new Pike release at ftp://pike.ida.liu.se/pub/pike/all/7.4.28/ Contributions in the form of conmpiled binaries (make bin_export) is appreciated (save the config.info file). Regarding gentoo, there is no bc dependency anymore.

5 8

Pike 7.5/7.6 roadmap?
by Alexander Demenshin 18 Sep '03

18 Sep '03

Hi, Is there any roadmap for 7.5/7.6? What is new, long term plans, current feauters etc? Current status (in regard to stability and useabulity)? May be something like overview (changelogs are good but not for overview)... Regards, /Al

2 1

7.4
by Martin Nilsson (saturator) ＠ Pike (-) developers forum 15 Sep '03

15 Sep '03

Is there anything else left to do before making a source package? Marcus, does your latest fixes warrent for a CHANGES entry?

2 2

Catching segfault
by David Gourdelier 15 Sep '03

15 Sep '03

Hello list, I have a segfault with a Pike that happens rarely on a busy Camas server. To get a backtrace and fill a bug report I've tried to run it into gdb however I didn't get any segfault for now and I can't run it into gdb for a long time since it is a production server (I saw this error only one time on the development server, too few traffic). Maybe it's not even possible to have a segfault inside gdb because of a strange side effects (maybe the segfault occurs only on a fast process or something). So I'd like to know if it would be possible to catch SIGSEGV in Pike and output a backtrace so that: . You might get more bug reports. . It would be possible to track problems when it's not possible to run inside a debugger or that the error don't happen in this case. Thank you for your reply. -- David Gourdelier

2 6

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 September 2003