Pike-devel May 2007

pike-devel@lists.lysator.liu.se

2 participants
11 discussions

Process.run
by Peter Bortas (nu med mindre Opera) ＠ Pike (-) developers forum 15 Jul '08

15 Jul '08

I just checked in a Process.run() in 7.7: http://pike.ida.liu.se/development/cvs/diff.xml?module=Pike&file=7.7/lib/mo… The rational for that is that I was once again reminded by a user this week that getting Process.create_process() or Process.Process right without some corner case blocking is hard. It's not obvious that if you bind pipes to booth stderr and stdout you have to take in to account that OS buffers are not limetless. Process.run() is a thin wrapper around Process.Process that collects stdout, stderr and exitcode and return them in a mapping. This could potentially result in huge strings, but will do what most users want and even already do when they call create_process() with both pipes bound. Something like this should be in 7.8, but I'm open to suggestions for other things that might be usefull to return in the mapping or for changing member names.

5 7

Snapshot tarballs and packaging/debian
by Magnus Holmgren, FR Ryd (Nu med m�l och syfte) ＠ Pike (-) developers forum 03 Oct '07

03 Oct '07

I have a few questions relating to pike in Debian (as you may know, the previous maintainer has retired from Debian and orphaned his packages). I've figured out that one can get a fresh tarball from http://pike.ida.liu.se/generated/pikefarm/packages/7.6/latest. What's the difference between that and checking out from CVS and running "make source" (which is what I suspect Marek has done), if any? Is there any archive of such tarballs except for the official releases? How did the packaging/debian subdirectory originally come to be? Do you synchronize with the Debian package yourself or has Marek been sending you patches? I see that export.pike adds new records to packaging/debian/changelog. AFAICT, export.pike --tag first increments the build number (to an even number, typically), then tags, then increment the build number again, so that an even build number represents a known state of the source, whereas an odd build number can include any number of commits inbetween.

17 129

error: `LIBS' was not set in the previous run
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 30 Jul '07

30 Jul '07

Has anyone else seen this problem? When building current 7.7 from scratch, it bombs out during the configuration of CommonLog: configure: loading cache ../.././config.cache configure: error: `LIBS' was not set in the previous run configure: error: changes in the environment can compromise the build In config.cache there is the following: ac_cv_env_LIBS_set= ac_cv_env_LIBS_value= (these are the only ac_env/ac_cv_env entries). Maybe this is related to the line LIBS= in PIKE_RETAIN_VARIABLES somehow? Interestingly enough, the problem does not occur on my PS3, which also has ac_cv_env_LIBS_set= ac_cv_env_LIBS_value= in config.cache...

3 8

returning error objects anywhere?
by Martin Bähr 02 Jun '07

02 Jun '07

hi, is there any reason to not convert all errors that are being thrown anywhere in pike 7.7 to error objects? if not, then i'd prefer to stomp on any that i come accross rather than keep using tests on the error type. greetings, martin.

8 27

Calendar compilation problem
by Martin Bähr 30 May '07

30 May '07

hi, i just objserved the following obscure error: if i run Calendar; before doing anything else with the Calendar module, then the module is now missing now(); i guess this has to do with the way the Calendar module is built, and i wonder how this could be prevented other than "don't do this" greetings, martin.

6 28

Re: Calendar compilation problem
by Mirar ＠ Pike developers forum 28 May '07

28 May '07

This looks like it could be guilty: void fill_cache() ... map(indices(module), safe_index); from master.pike.in.

2 2

New 7.6 beta this weekend
by Peter Bortas ＠ Pike developers forum 28 May '07

28 May '07

The netgods willing I'll release another 7.6 beta this weekend, please do anything drastic like rewriting the garbage collector the next few days.

2 2

issues with [<x..<y]
by Martin Bähr 25 May '07

25 May '07

hi, i'd like to discuss the implementation of [<x..<y]. i do not agree with the current way of addressing the last element as "<0". this is counter-intuitive. i think it makes more sense to have "-x" and "<x" to mean the same, so [..<2] means what most people think [..-2] should mean. consider the explanation: [-x] counts from the end. 0 has no negative value, so -1 is the last element. however in a range -x is always reduced to 0. to count from the end in a range use <x. now if "-x" and "<x" would mean the same, you could just end there. as it is now you have to add an extra paragraph to explain the difference. changing this would as a bonus also make this compatible with lpc (at least as implemented in ldmud) i noticed this while ago, but only now managed to get pike 7.7 built on my machine after i came up with the idea of using pikefarm to always have an up-to-date binary without having to build one myself everytime. greetings, martin.

3 2

Calendar.TimeRange->format_http()
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 06 May '07

06 May '07

> 2007-05-05 12:05:41 UTC by mbaehr > > * Pike/7.7/lib/modules/Calendar.pmod/YMD.pike (+3/-5) > > don't hardcode month and day names here changes format_http() from using constant English strings to using Calendar's language bound day and month names. I don't contest that that format could be useful for some purposes, but shouldn't it use a different method name then? RFC 2616 states that a HTTP-date is: HTTP-date = rfc1123-date | rfc850-date | asctime-date rfc1123-date = wkday "," SP date1 SP time SP "GMT" rfc850-date = weekday "," SP date2 SP time SP "GMT" asctime-date = wkday SP date3 SP time SP 4DIGIT date1 = 2DIGIT SP month SP 4DIGIT ; day month year (e.g., 02 Jun 1982) date2 = 2DIGIT "-" month "-" 2DIGIT ; day-month-year (e.g., 02-Jun-82) date3 = month SP ( 2DIGIT | ( SP 1DIGIT )) ; month day (e.g., Jun 2) time = 2DIGIT ":" 2DIGIT ":" 2DIGIT ; 00:00:00 - 23:59:59 wkday = "Mon" | "Tue" | "Wed" | "Thu" | "Fri" | "Sat" | "Sun" weekday = "Monday" | "Tuesday" | "Wednesday" | "Thursday" | "Friday" | "Saturday" | "Sunday" month = "Jan" | "Feb" | "Mar" | "Apr" | "May" | "Jun" | "Jul" | "Aug" | "Sep" | "Oct" | "Nov" | "Dec" Examples of Calendar's less known features (swedish and roman latin): > Calendar.set_language("swedish")->Day()->week_day_shortname() "sön" > > Calendar.set_language("roman")->Day()->month_shortname(); "Mai" I'm not sure if the Calendar module tries to do any environment sniffing of its own to pick up a suitable language, but it's been known to be a bit over-customizable by .h files, so I'd be wary of changes like these.

3 6

Attributed types
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 02 May '07

02 May '07

As you all probably know, I've been tinkering with the type system in Pike 7.7 for a while now, and I've now reached the point of implementing attributed types. The question once again is "which syntax do you prefer?": GCC-style: void __attribute(noreturn) error(string msg); string werror(string __attribute(sprintf_format) fmt, mixed __attribute(sprintf_args) args); or (analogous with other pike types): __attribute(noreturn, void) throw(mixed); string werror(__attribute(sprintf_format, string) fmt, __attribute(sprintf_args, mixed) args);

4 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 May 2007