Pike-devel May 2008

pike-devel@lists.lysator.liu.se

10 participants
55 discussions

7.8 blockers
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 21 May '08

21 May '08

As for Roxen, my intention is to turn off 7.4 compat mode as soon as it works in that mode. Then I expect to be hit full force by all the new stringency.

1 0

7.8 blockers
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 21 May '08

21 May '08

That's a very nice addition, but it has a problem: As I'm working my way through Roxen to get it to compile with 7.7 in 7.4 compat mode, I'm adding regression tests to the testsuite where this and other new errors are causing previously working pike code to not compile anymore. I think that every new error added to the compiler needs a compat check so that it's turned off in old code. It seems to me that the lack of such compat checks is systematic.

1 0

7.8 blockers
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 21 May '08

21 May '08

How about this then? No ordering issues here: Pike v7.7 release 47 running Hilfe v3.5 (Incremental Pike Frontend) > [string x] = array_sscanf("17", "%d"); (1) Result: ({ /* 1 element */ 17 }) >

1 0

7.8 blockers
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 21 May '08

21 May '08

Yes. It doesn't seem like hilfe recognizes the multiple assignment syntax, so it doesn't make any magic transformations. Pike v7.7 release 47 running Hilfe v3.5 (Incremental Pike Frontend) > [int x]=({3}); (1) Result: ({ /* 1 element */ 3 }) > dump wrapper Last compiled wrapper: 001: mapping(string:mixed) ___hilfe = ___Hilfe->variables; 002: # 1 003: mixed ___HilfeWrapper() { return [int x]=({3}); ; } 004: > int x=3; > dump wrapper Last compiled wrapper: 001: mapping(string:mixed) ___hilfe = ___Hilfe->variables; 002: # 1 003: int x=3; 004: mixed ___HilfeWrapper() { return x; } 005: >

2 1

7.8 blockers
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 21 May '08

21 May '08

Then this ought to give a compilation error, no? Pike v7.7 release 47 running Hilfe v3.5 (Incremental Pike Frontend) > [string x, int y] = array_sscanf("47 11", "%d %s"); (1) Result: ({ /* 2 elements */ 47, "11" }) >

1 0

7.8 blockers
by Peter Bortas ＠ Pike developers forum 17 May '08

17 May '08

Me, grubba an Nilsson enumerated the major 7.8 blockers yesterday. They are as far as we could determine: [ ] not done [/] tentatively fixed [X] fixed Owner Issue [ ] grubba Deprecated type should print warnings. [ ] grubba Implement #pragma to turn off deprecated warnings. [ ] zino Known crash on Windows. [ ] mast/zino New Windows build environment. [ ] per/marcus Performance regression --with-assembler. (per and marcus weren't present so item assigned without consent... per says memprotect() is responsible as far as -x benchmark goes.) [ ] nilsson Running the test suite should not produce warnings. [ ] zino/mast Building external modules should work. [ ] nilsson Write ChangeLog. [ ] Deprecated type should be extracted to documentation. [ ] Documentation should transform from XML to HTML (broken) [ ] nilsson Arg module should be fixed or removed. Non-blockers: [ ] jhs Build (SVG) graph from the -x benchmark results Pikefarm delivers to track development. If you think you could help with any of the items please do. Especially the items that have no one assigned to them yet.

11 70

7.8 blockers
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 17 May '08

17 May '08

language.yacc is now capable of passing a flags parameter along to o_sscanf().

2 2

Calendar timezones
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 17 May '08

17 May '08

The following code breaks in 7.7, claiming that the timezone name gotten from Calendar.TZnames.zones doesn't exist: int main() { foreach (Calendar.TZnames.zones; string r1; array(string) r2s) foreach (r2s, string r2) { werror (r1 + "/" + r2 + "\n"); Calendar.ISO.Second()->set_timezone (r1 + "/" + r2); } } That's a bug, right?

4 6

Calendar timezones
by Mirar ＠ Pike developers forum 17 May '08

17 May '08

...but why doesn't it work?

4 9

Calendar timezones
by Mirar ＠ Pike developers forum 17 May '08

17 May '08

Note that I still think Per's solution was better.

1 0

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 2008