Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

optimization bug?
by Mirar ＠ Pike developers forum 09 Oct '08

09 Oct '08

> array v=({1,2,3}); > for (int i=0; i<sizeof(v); i++) v+=({17}); Ok. Why? While > int i; > for (i=0; i<sizeof(v); i++) v+=({17}); doesn't finish (as it shouldn't).

1 0

unsigned int optimizations?
by Martin Bähr 06 Oct '08

06 Oct '08

hi, i just wondered if pike does any optimization on int(0..x) i mean any case where x is below 4294967296 should fit into an unsigned int, so there would be no need to transition to bignum for these. and int(0..255) fits into a byte. does or can pike make use of that? greetings, martin.

6 19

pike 7.8 cvs browser broken?
by Martin Bähr 06 Oct '08

06 Oct '08

hi, for some reason, the cvs browser for 7.8 is missing files and directories: http://pike.ida.liu.se/development/cvs/browse.xml?dir=7.8&module=Pike listed are: bin lib man refdoc src .gitignore CHANGES Makefile README-CVS compared to the checkout which contains: ANNOUNCE bundles/ COPYING Makefile README src/ bin/ CHANGES COPYRIGHT man/ README-CVS tools/ branches COMMITTERS lib/ packaging/ refdoc/ subdirectories are missing stuff too greetings, martin.

1 0

eureka down
by Peter Bortas ＠ Pike developers forum 04 Oct '08

04 Oct '08

eureka is down and will remain so until tomorrow afternoon due to testing of the power grid that feeds the building it's in.

1 0

Re: unsigned int optimizations?
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 04 Oct '08

04 Oct '08

For example, instead of using "%4c" in sscanf format strings, you can use "%+4c" instead.

1 0

SHA-512
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 03 Oct '08

03 Oct '08

Noticed SHA-512 is missing in Pike. That's unfortunate, and I'm hoping it can be squeezed into 7.8, which means it should be added to Nettle as well. Anyone know if there are plans for that?

2 1

wierd syntax?
by Martin Bähr 29 Sep '08

29 Sep '08

is there a reason why pike allows whitespace between ( and [ for ([ ? (same for ]) and ({ }) of course) i always viewed ([ as an inseperable entity (like += or other multicharacter elements) can anyone explain this? greetings, martin.

4 5

Re: precompile on 7.8.8
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 27 Sep '08

27 Sep '08

>> That line number doesn't seem to match with either of the two >> precompile.pike files in recent Pike 7.8. Can you give an excerpt? > >Sure... it's: [...] > ret+=({ > PC.Token(sprintf("if(Pike_sp[%d%s].type != >PIKE_T_STRING || Pike_sp[%d%s].ustring -> width)", > argnum,check_argbase, > argnum,check_argbase, > upper_case(arg->basetype())),arg- > >line()) > }); Ok, that seems to correspond to line ~2211 in Pike 7.8, where it has been fixed by removing the last argument to the sprintf.

1 0

precompile on 7.8.8
by H. William Welliver III 27 Sep '08

27 Sep '08

I'm getting an error when precompiling a pmod on 7.8.8: precompile: pike /usr/local/pike/7.8.8/include/pike/precompile.pike pcap.cmod /usr/local/pike/7.8.8/include/pike/precompile.pike:2007:Too many arguments to sprintf (expected 5 arguments). /usr/local/pike/7.8.8/include/pike/precompile.pike:2007:Got : string. I noticed that the sprintf statement has a wrong number of arguments for the formatting string. Can someone who understands this take a quick look? Bill

2 1

Changelog
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 21 Sep '08

21 Sep '08

This is about what remains to be documented in the CHANGES - Describe the need for multiple backends, exemplify how to implement it and explain the different backends available. - Explain what a mixin is. - Create an example for how to use split() in Calendar objects. - Rewrite the Locale.Charset section. - Rewrite the ODBC section. - Rewrite the Parser.XML.Simple section. - Rewrite the Parser.XML.Tree section. - Rewrite the Postgres section. - Add descriptions for Pike.low_check_call() get_return_type() and get_first_arg_type(). - List the changes of Sql.mysql. - Describe how SSL client cerificates work and provide usage example. - Add description of Standards.XML.Wix - Document all changes to the Tools module. - Add an example for when ADT.List is useful. - Describe ADT.Trie. - Add description of the Kerberos module. - Add some more information on Protocols.HTTP.Server.Proxy - Add the missing changes for the Java section.

2 1

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