Pike-devel May 2007

pike-devel@lists.lysator.liu.se

2 participants
14 discussions

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

%H
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 01 May '07

01 May '07

Should sprintf("%0H",s) be the same as sprintf("%H",s) or should it be an error?

1 0

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