Pike-devel

pike-devel@lists.lysator.liu.se

2 participants
3046 discussions

Start a nNew thread

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

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

21 Sep '08

I changed the type of `<< in file_functions.h to tAttr("deprecated", tFunc(tMixed,FILE_OBJ)) which didn't have any visible effect when doing file<<"string". However, if I add the following to the File class i module.pmod object `<<(mixed in) { return ::`<<(in); } I'll get the warning /home/nilsson/Pike/7.8/lib/modules/Stdio.pmod/module.pmod:804: Warning: Calling a deprecated value. /home/nilsson/Pike/7.8/lib/modules/Stdio.pmod/module.pmod:804: Warning: Using deprecated object(implements _static_modules.files()->Fd_ref) value. Is this hiding a bug or a misfeature?

1 0

pike-svn.lysator.liu.se
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 13 Sep '08

13 Sep '08

This is an announcement that a Subversion repository for Pike is now available on eureka under the following two URLs: http://pike-svn.lysator.liu.se/ - read-only access https://pike-svn.lysator.liu.se/ - commit access To use the https address, you need a client certificate. I've written instructions on <http://mc.pp.se/svncert.xhtml> how to make and use one. (CSR:s can be sent to me.) If it turns out that this is inconvenient, we can change to basic auth with name and password instead. Please note that while it's perfectly allright to commit for test purposes, anything committed to the repository at this time _will_ be lost when I make the next conversion run, so don't commit anything "real". :-) Feedback on server setup or problems with the repository itself is welcome.

4 7

Error decoding XMLRPC call
by cschalkwijk 12 Sep '08

12 Sep '08

Hello, I receive the following error when decoding an XMLRPC call. Error decoding XMLRPC call: All data must be inside tags (location 24904: "/"...) I'd like to know if the location is the character position of the error causing xml/text/whatever and, if it is, if I should take anything into account while finding that position (e.g. tab to space conversions). I seem to get the location number with a file of 24230 characters. Greetings, Coen __________________________________________________________ Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken. The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system. __________________________________________________________

2 1

Git repository
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 12 Sep '08

12 Sep '08

I'm trying to fully understand the history as presented by git. One of the things I can't work out is this: Take a look at src/pike_memory.c on the 7.8 branch in gitk. For the last few commits it says 7.7 and 7.8 branches only, which is what I expect. But at the commit "Added DMALLOC_USE_HASHBASE mode" it suddenly claims 7.4 and 7.6 too, and that that commit precedes both tags v7.4.512 and v7.7.40. Why is that? I can't see this commit or any descendant on the 7.4 branch. All commits after that one are also claimed to be on essentially all branches. This is something I see in general all over the repository. If the history of several branches is viewed at once then this makes it difficult to see on which branch(es) a commit is really made.

7 34

Jump to page:

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