Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Changes coming to 7.7
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 04 Jun '07

04 Jun '07

Peter pulled together some people for sessions to bring 7.8 a little closer, some weeks ago, by forcing people to talk to one another, do some debugging, set up linux on his PS3, have kladdkaka and generally have a good time. I took some notes, and they were briefly circled for validity among participants prior to being completely forgotten. They just surfaced, again, in a spot of enlightened recollection; enjoy! Order is semi-random, some points already have been implemented since then and where things are difficult to understand, other participants can hopefully give better explanations on request. Conclusions: * Backend hack: fall back to poll if epoll does not work. * Remove varargs support (here meaning automatic "|void" decoration of all attributes -- not the trailing "<type> ... args" support). * Remove all traces of write << "foo" and similar "C++ streams" hacks. (which have not worked since Pike 0.5 or something like that anyway) * Stuff setting nonblocking mode should first check whether they could before propagating to a backend (select) or not. * GLUE initialization might be a bit lazier about setting up lights. * Locale generates deferred call_out:s -- don't, until Locale is used. * Pike 7.7 split to 7.8/7.9, feature freezing 7.8. * Mast, grubba and others commit their experiments to 7.7 first. * Others, feel welcome to mention what you're cooking, estimating when it might be checked in, for same split. * Attribute no_return. * Attribute for type checking (sprintf, werror). * Typedefs are good. * Turn on features in 7.7 by default which are intended to be deployed in pike 7.8. (This includes the new types and mapping-keypair-loop.) * Binary Hollerith encoding for sprintf/sscanf (%H, %2H, %-4H et c). * Add a structured way of reading/writing serialized data. * Add the function signatures int max(string s) and int min(string s). * For pike 8.0, add a buffer type (somewhat similar to System.Memory, but as a base type). I/O calls that presently handle string(0..255) should instead use buffer. It should further on be really easy using codecs like Locale.Charset to transition the buffer to/from strings, without much syntactic overhead, so you'd only be using the buffer directly when you're actually working on raw binary data. * The new compiler also aims for pike 8.0. * Buffer literals? {[ 17, /* ..., */ "foo", 0xBA ]} might be a syntax. * Stdio.read_file() shall take one parameter only (a file name), so that it might eventually blend in with the above for handling some additional parameter to specify an encoding. The result might look something like: buffer read_file( string filename ) string read_file( string fn, string|Locale.Charset.Decoder charset ) * We have rather many different-looking streaming interfaces in Pike; consolidating them to a common naming scheme and possibly leveraging that with features that make sense wouldn't hurt. * There are lots of include files strewn about the place at random that would benefit from some cleanups. * It should be possible to build modules separately. * Add testsuite coverage for pike -x module so breakage there does not fly below radar for extended periods of time. * grubba checks in the whitefish repository below cvsroot/projects/ * eventually: move out modules so they do not live in pike core * Math operations on NaN dump core under ix86; fix. * Add a syntax for type propagation (on the pike level); examples: - a function that returns a type mimicing its first argument - popen can now return file objects -> strict type checks explode

3 3

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

catch warnings?
by Martin Bähr 02 Jun '07

02 Jun '07

while we are on the subject of error handling, is there a way to catch warnings? in hilfe, warnings just get spewed out with broken formatting because they are not using the right write function. and generally i'd like to be able to control how warnings are handled, either for formatting, logging or elevating them to an error. greetings, martin.

2 1

string declarations and pike autodoc parsing
by Martin Bähr 02 Jun '07

02 Jun '07

while testing the documentation build i discovered that StringType was defined as string(width), however the actual implementation appears to require string(minwidth..maxwidth): > string(8) foo; Compiler Error: 1:parse error, unexpected `')'', expecting `TOK_DOT_DOT' or `TOK_DOT_DOT_DOT' Compiler Error: 1:Expected integer range. now i find references to string(width) in the documentation, which i guess should be changed, but to what? string(0..8) or string(0..255) or? greetings, martin.

3 3

Re: returning error objects anywhere?
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 01 Jun '07

01 Jun '07

> trig a specific catch somewhere, without having to implement an > entirely-fledged compatible error object. The hazards of changing phrasing.. That should read "without having to implement an entirely compatible error object", of course.

1 0

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

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