Pike-devel February 2004

pike-devel@lists.lysator.liu.se

8 participants
62 discussions

Nettle
by Martin Nilsson (saturator) ＠ Pike (-) developers forum 26 Feb '04

26 Feb '04

I PUSHED THE BUTTON. Now the _Crypto module isn't used (though still built). That means that you'll need Nettle installed to use any parts of Pike that uses Crypto.

9 31

7.4.44
by Martin Nilsson (saturator) ＠ Pike (-) developers forum 26 Feb '04

26 Feb '04

Peter and I have been working hard with resolving some NT problems and have now managed to create a new NT dist with pretty much everything except GLUT. 7.4.44 source dist and windows dist are available in FTP. Release notes at http://pike.ida.liu.se/download/notes/7.4.44.xml We'll release it more publicly when we have binary dists for more platforms. Please help out with good binary dists.

3 2

Pike 7.5 - CVS installation problem
by David Gourdelier 25 Feb '04

25 Feb '04

Hello, When trying to install Pike 7.5 - CVS on FreeBSD 4.3, I got this error: %make install /home/david/Pike/7.5/src/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/david/Pike/7.5/src/master.pike -x extract_autodoc -q --srcdir=/home/david/Pike/7.5/src --imgsrc=/home/david/Pike/7.5/refdoc/src_images --builddir=doc_build/src --imgdir=doc_build/images Bad argument 1. Unknown program: foreach(0) /home/david/Pike/7.5/lib/modules/Tools.pmod/Standalone.pmod/extract_autodoc.pike:105: Tools.Standalone.extract_autodoc()->recurse("/home/david/Pike/7.5/src/doc_ build/src/doc_build/src/doc_build"+[963],"/home/david/Pike/7.5/src/doc_bui ld/src/doc_build/src/doc_build"+[977],0,({"predef::","doc_build","src","do c_build","src","doc_build","src",,,135})) /home/david/Pike/7.5/lib/modules/Tools.pmod/Standalone.pmod/extract_autodoc.pike:119: Tools.Standalone.extract_autodoc()->recurse("/home/david/Pike/7.5/src/doc_ build/src/doc_build/src/doc_build"+[954],"/home/david/Pike/7.5/src/doc_bui ld/src/doc_build/src/doc_build"+[968],0,({"predef::","doc_build","src","do c_build","src","doc_build","src",,,134})) ... After I tried to build Pike without the autodoc and I get compilation errors when using the Crypto module: > indices(Crypto); /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/cast.pike:4: Warning: Crypto.cast is deprecated. Use Crypto.CAST instead. /usr/local/pike/7.5.17/lib/7.4/modules/Crypto.pmod/module.pmod:12:Index 'crypt_md5' not present in module 'Crypto'. /usr/local/pike/7.5.17/lib/7.4/modules/Crypto.pmod/module.pmod:16:Index 'crypt_md5' not present in module 'Crypto'. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/aes.pike:4: Warning: Crypto.aes is deprecated. Use Crypto.AES instead. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/idea.pike:4: Warning: Crypto.idea is deprecated. Use Crypto.IDEA instead. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/sha.pike:4: Warning: Crypto.sha is deprecated. Use Crypto.SHA1 instead. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/hmac.pike:4: Warning: Crypto.hmac is deprecated. Use Crypto.HMAC instead. /usr/local/pike/7.5.17/lib/modules/Standards.pmod/PKCS.pmod/Signature.pmod:12:Index 'Hash' not present in module 'Crypto'. /usr/local/pike/7.5.17/lib/modules/Standards.pmod/PKCS.pmod/Signature.pmod:12:Illegal program identifier (type: int). /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/HMAC.pike:39:Error looking up 'Signature' in module 'PKCS'. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/HMAC.pike:77:Class definition failed. /usr/local/pike/7.5.17/lib/7.4/modules/Crypto.pmod/hmac.pike:6:Error looking up 'HMAC' in module 'Crypto'. /usr/local/pike/7.5.17/lib/7.4/modules/Crypto.pmod/hmac.pike:6:Illegal program pointer. /usr/local/pike/7.5.17/lib/7.4/modules/Crypto.pmod/hmac.pike:17:Class definition failed. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/hmac.pike:6:Error looking up 'hmac' in module 'Crypto'. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/hmac.pike:6:Illegal program pointer. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod.0:-: Warning: Compilation failed: Compilation failed. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/rsa.pike:4: Warning: Crypto.rsa is deprecated. Use Crypto.RSA instead. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/RSA.pike:221:Failed to index module 'Signature' with 'build_digestinfo' (module doesn't exist?) /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/RSA.pike:291:Expected constant, got something else (438) /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/RSA.pike:339:Expected constant, got something else (438) /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/RSA.pike:349:Expected constant, got something else (438) /usr/local/pike/7.5.17/lib/7.4/modules/Crypto.pmod/rsa.pike:6:Error looking up 'RSA' in module 'Crypto'. /usr/local/pike/7.5.17/lib/7.4/modules/Crypto.pmod/rsa.pike:6:Illegal program pointer. ... / David

6 9

Embedding Pike into C/C++ game
by Fredrik (Naranek) Hubinette (Real Build Master) ＠ Pike (-) developers forum 25 Feb '04

25 Feb '04

In my oppinion, pike would have to be a lot more modular to become popular in games. Basically, you would need to chop pike into pieces that can be linked individually. In my mind, those pieces would be: 1) The interpreter Capable or running pike-code, but provides only the most basic functions needed to manipulate data types. The interpreter does not provide a way to load code into memory. 2) The Compiler Capable of compiling pike-code to in-memory code 3) Object loader (could be more than one) Capable of loading pre-compiled pike code into memory. 4) Function library. (or libraries) Provides all the functions needed to make up a complete Pike. 5) Pike executable Uses all of the above libraries to run Pike programs. Apart from this, all identifiers that don't start with 'Pike' should be fixed to make Pike more embedding-friendly. / Fredrik (Naranek) Hubinette (Real Build Master) Previous text: >2004-02-23 16:54: >Subject: Embedding Pike into C/C++ game >-------------------------------------------------------------------- >I forgot some things in my original email. This is mostly geared >towards the developers of Pike, but I'm copying it to the normal >mailing list as well. > >I wanted to point out that what Kenneth is saying probably is very >true. Pike is a very nice and powerful language. Python and Lua are >indeed the most commonly used languages in games today. However they >aren't without issues - Lua especially (for example very easy to make >mistakes that you don't notice until much later). Does Pike have a >place here? I think it's possible. > >It might have a future in games if it was easily embeddable (and >behaved nicely in those cases). Of course the other big hurdle is >documentation and lack of bugs. That is as we all know a problem >that's harder than embedding to solve. > >So the question is, how does this get solved? Is there a document or >notes about issues with embedding? For now, limited to embedding a >single interpreter in a process (not worrying about multiplicity as >Perl puts it, which is a whole other layer of complexity). Has anyone >sat down and looked at this more in detail? > > / David Hedbor >

4 4

XMLRPC patch for 7.2
by David Gourdelier 25 Feb '04

25 Feb '04

Hello, I have a patch for Pike 7.2 XMLRPC. The spec at http://www.xml-rpc.org/ says the <value> element can contain <string>, <array> and so on but can also contain a PCDATA by itself ("If no type is indicated, the type is string."). This wasn't set in XMLRPC.pmod and this is used by some client like XML-RPC Apache project one. Here is the patch: on Feb 23 16:38:40 2004 @@ -137,7 +137,7 @@ <!ELEMENT params (param*)> <!ELEMENT param (value)> - <!ELEMENT value (boolean|i4|int|double|string|base64| + <!ELEMENT value (#PCDATA|boolean|i4|int|double|string|base64| array|struct|dateTime.iso8601)> <!ELEMENT boolean (#PCDATA)> @@ -231,6 +231,8 @@ // seems to assume localtime). return Calendar.parse("%dT%h:%m:%s", data*"") || magic_zero; + // the spec says that the default is string inside value + default: return data*""; } error("Unknown element %O.\n", name); case "error": / David

3 5

configure
by Martin Nilsson (saturator) ＠ Pike (-) developers forum 25 Feb '04

25 Feb '04

How can I tell configure that I want to use the ar/as/gcc/ld/nm/etc binaries from /foo/bar instead of the system-ones?

2 1

PIKE
by Mirar ＠ Pike developers forum 24 Feb '04

24 Feb '04

How do I get Pike to use another pike then /usr/local/bin/pike? Setting PIKE, USE_PIKE or --with-pike doesn't seem to help. config.info reports: | pike............ /usr/local/bin/pike-7.5 but: | precompile: /usr/local/bin/pike /home/mirar/pike/bin/precompile.pike /home/mirar/pike/src/modules/Gmp/mpq.cmod (method=QQQQQ) | /home/mirar/pike/bin/precompile.pike:2121:Indexing on illegal type. | Pike: Failed to compile script: | Compilation failed. | | Failed to find a Pike executable that could run /home/mirar/pike/bin/precompile.pike.

3 7

Bad number of identifiers in inherit: 2 != 3
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 24 Feb '04

24 Feb '04

After the recent changes to Parser.RCS, I see a warning /usr/local/pike/7.5.19/lib/modules/Parser.pmod/_parser.pmod.o:-: Warning: Decode failed: Error while decoding program(/usr/local/pike/7.5.19/lib/modules/Parser.pmod/_parser.pmod): Bad number of identifiers in inherit: 2 != 3 I don't quite know what to do with. Things appear to work nevertheless but what is it a symptom of? Parser.pmod seems to do some interesting three-level inheritance, due to the weird one-pmod-per-.so-file scheme which might be a clue, I suppose. Is that setup (a .pmod that just inherits some ____parser or similar) somehow superior to the old style setup where .so files could be modules right away?

2 1

Starting new pike processes from the testsuite
by Niels M�ller (ny flexiblare br�stkorg) ＠ Pike (-) developers forum 24 Feb '04

24 Feb '04

What's the recommended way of starting separate processes (which are Pike programs) from the testsuite? I want to make a test case for the SSL code, by starting a https process using the SSL.pmod/https.pike program (which I'm not sure it really belongs in the module tree) or some similar code, and then use the client code in the url/http modules to connect to it.

9 35

Embedding Pike into C/C++ game
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 24 Feb '04

24 Feb '04

Another restriction would be no multiplicity, i.e. only one pike interpreter per process. / Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) Previous text: >2004-02-23 16:51: >Subject: Embedding Pike into C/C++ game >-------------------------------------------------------------------- >I think the biggest problem is that no one is making a list of the >actual problems that should be solved. To me it (since I know so little >about the backend, memory management etc) it feels like it shouldn't be >that hard to add pike_init and pike_exit that does what main does and >then begin to call Pike code (possibly with a set of restrictions like >no threads and no call_outs). > > / Martin Nilsson (saturator) >

4 5

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 February 2004