Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

-DNOT_INSTALLED
by Mirar ＠ Pike developers forum 14 Nov '03

14 Nov '03

There's lots of red dots in pikefarm for 7.5 now. Anyone working on it? | Compiling /home/xenofarm/xenoclient/pike-7.5/orchid.mirar.org/buildtmp/Pike7.5-20031113-045850/src/post_modules/GL/top.c | /home/xenofarm/xenoclient/pike-7.5/orchid.mirar.org/buildtmp/Pike7.5-20031113-045850/build/linux-2.6.0-test9-i686/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/xenofarm/xenoclient/pike-7.5/orchid.mirar.org/buildtmp/Pike7.5-20031113-045850/build/linux-2.6.0-test9-i686/master.pike /home/xenofarm/xenoclient/pike-7.5/orchid.mirar.org/buildtmp/Pike7.5-20031113-045850/src/post_modules/GL/gen.pike < /home/xenofarm/xenoclient/pike-7.5/orchid.mirar.org/buildtmp/Pike7.5-20031113-045850/src/post_modules/GL/auto.c.in > /home/xenofarm/xenoclient/pike-7.5/orchid.mirar.org/buildtmp/Pike7.5-20031113-045850/src/post_modules/GL/auto.c | Unknown options -DNOT_INSTALLED.

3 3

Re: pike external module documentation
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 13 Nov '03

13 Nov '03

> The core modules are either built with a pike glue file, or if one > isn't provided, a two line glue file is automatically generated. /.../ Sorry, but that's not correct. You must be looking at a pike built with static modules. They get a glue file to appear in the right spot in the namespace, but dynamic ones don't need that. > True, and something that I shouldn't have let slip. It was copied from > somewhere within the pike tree, so somewhere there's a testsuite that > has behavior that might not be so good test-wise. /.../ Some of the standard modules, e.g. Gmp, do that because they are optional, so the main testsuite still works when they are disabled. But that doesn't apply to third party modules. / Martin Stjernholm, Roxen IS Previous text: >2003-11-10 23:52: >Subject: Re: pike external module documentation >-------------------------------------------------------------------- >Thanks for the feedback... I will try to get the changes you suggested >incorporated. > >> Is it possible to build the docs for the module only, without merging >> it with the system docs? > >I hadn't thought of this, but it should be possible, though right now >the build assumes the modref would be installed in the system >documentation directory pikedir/docs/modref. Again, this should be >relatively simple to accomplish. > >> What about pike only modules? Should be trivial, but it'd still be >> nice if they too are covered by the standard tools so that they can be >> handled the same way. Maybe it works to provide a standard Makefile >> for that case, so that not even autoconf is required. > >I checked some changes in about 2 weeks ago that should fix this. I've >actually been testing on a pike-only module, and it seems to work just >fine with a copy of pike from CVS. > >> Doesn't work for modules with no pike layer. Also, the check works >> better if it's a file which is very specific for the module. > >That choice of filename was really just a suggestion; I assumed that >the text following it would clarify that it would be wise to choose a >relatively unique filename (i think i wrote that; but will check.) > >> Btw, you seem to assume that there always should be a pike glue file >> like that. Is it really necessary? > >The core modules are either built with a pike glue file, or if one >isn't provided, a two line glue file is automatically generated. I was >merely following convention; whether it's a good or necessary >convention I'll leave to others. > >> It should be enough with "VPATH=@srcdir@". (A while ago I cleaned up a >> lot of vpaths like that in the module tree - seems to have been a bad >> case of cut'n'paste back to very old code.) >> > >I probably had that source file for a while, so i will fix this. > >> A bit odd example. In the testsuite for a specific module, isn't it >> better to assume it exists? If there has been some major problem so >> that the module isn't installed at all, one wouldn't expect it to >> silently pass the testsuite. > >True, and something that I shouldn't have let slip. It was copied from >somewhere within the pike tree, so somewhere there's a testsuite that >has behavior that might not be so good test-wise. I was mostly >interested in getting the framework together. I agree that I might have >picked a better set of tests, but was in a bit of a hurry when i did >it. It actually might be nice for someone with actual knowledge of the >testsuite system to put together a few paragraphs about it. > > > > / Brevbäraren >

3 8

-DNOT_INSTALLED
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 13 Nov '03

13 Nov '03

If you are able to trigg the bug; please add some debug to lib/modules/Getopt.pmod, and check where it goes wrong.

2 2

Can I get detailed documents about Pike languages design
by chen david 13 Nov '03

13 Nov '03

hi, I am a Pike user and very interested in Pike languages design. I downloaded the source code of pike-v7.4.28, but did't find any design documents, such as the theory of Pike interpreter, the architecture of Pike construction, etc. BTW, I have some experiences of simple compiler design and compiler optimization. How can I begin to understand the Pike design and furthermore do some development to it? Any suggestion or help will be highly appreciated. Thanks. Regards. David _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail

3 2

Re: module modref
by Johan Sundstr�m (f�ngar heffaklumpar) ＠ Pike (-) developers forum 12 Nov '03

12 Nov '03

Or, better still, cook your own refdoc/structure file, to only list documentation entities you have and want in the result? That file was at least intended to be pluggable and to make it easier to do lots of different views of the refdocs. / Johan Sundström (fångar heffaklumpar) Previous text: >2003-11-12 01:54: >Subject: Re: module modref >-------------------------------------------------------------------- >ah, ok. I'll try ignoring the return on that step then. thanks! > >On Tuesday, November 11, 2003, at 07:30 PM, Martin Nilsson (saturator) >@ Pike (-) developers forum wrote: > >> I think that failure is nothing more than a warning. It is anyway >> caused >> by the <insert-move entity="_Roxen"/> and the likes in the xml files in >> refdoc/structure. >> >> / Martin Nilsson (saturator) >> >> Previous text: >>> 2003-11-12 00:44: >>> Subject: module modref >>> -------------------------------------------------------------------- >>> I'm working on creating a module only modref, but am running into the >>> following problem: >>> >>> I've created the autodoc.xml containing only the markup for my module. >>> Then I run the following command: >>> >>> pike -x assemble_autodoc >>> /usr/local/pike/7.5.12/doc//src/structure/modref.xml \ >>> plib/autodoc.xml >plib/modref.xml >>> >>> And get the following output: >>> >>> Parsing structure file >>> "/usr/local/pike/7.5.12/doc//src/structure/modref.xml". >>> Executing reference expansion and queueing node insertions. >>> Parsing autodoc file "plib/autodoc.xml". >>> Executing node insertions. >>> Failed to move predef::._Roxen >>> Failed to move predef::.__builtin >>> >>> Can anyone with more knowledge of the autodoc system help me out with >>> this >>> one? It looks like there must be some references to these "modules" >>> but i >>> don't know how to remove those dependencies. >>> >>> Any thoughts? >>> >>> Bill >>> >>> >>> >>> / Brevbäraren >>> > > > > / Brevbäraren >

1 0

module modref
by Bill Welliver 11 Nov '03

11 Nov '03

I'm working on creating a module only modref, but am running into the following problem: I've created the autodoc.xml containing only the markup for my module. Then I run the following command: pike -x assemble_autodoc /usr/local/pike/7.5.12/doc//src/structure/modref.xml \ plib/autodoc.xml >plib/modref.xml And get the following output: Parsing structure file "/usr/local/pike/7.5.12/doc//src/structure/modref.xml". Executing reference expansion and queueing node insertions. Parsing autodoc file "plib/autodoc.xml". Executing node insertions. Failed to move predef::._Roxen Failed to move predef::.__builtin Can anyone with more knowledge of the autodoc system help me out with this one? It looks like there must be some references to these "modules" but i don't know how to remove those dependencies. Any thoughts? Bill

2 1

pike external module documentation
by Bill Welliver 11 Nov '03

11 Nov '03

I've started the first draft of a document describing how to build modules outside of the pike source tree. Keeping in mind it's only about 45 minutes old, please take a look at it and let me know if there are any corrections or additions to it at this point. I've not gotten into any of the goodies about the module repository, but that will come soon enough. I think the only requriements that should happen from that standpoint would be a recommendation that a constant __version should be placed in the class of the module, and that the module distribution directory be saved as FullModuleName-ver. https://steam.iaeste.at/home/Pike%20Community/tutorials/External%20Modules/ Note that there is both a HTML version and a StarWriter version. If anyone wants to make changes, at this point, please make them to the SW version (or just send me your updates). As always, comments, suggestions and donations of time from technical writing enthusiasts are welcome! Bill

2 2

Problem with MIME module
by David Gourdelier 10 Nov '03

10 Nov '03

Hello, I am using the MIME module of Pike 7.2 and I think it is broken when the mail contains the Content-Transfer-Encoding header. Indeed the RFC says the header is of type: encoding := "Content-Transfer-Encoding" ":" mechanism mechanism := "7bit" / "8bit" / "binary" / "quoted-printable" / "base64" / ietf-token / x-token But in the Pike code of MIME.pmod we have: if (headers["content-transfer-encoding"]) { array(string) arr=tokenize(headers["content-transfer-encoding"]); if (sizeof(arr)!=1 || !stringp(arr[0])) throw (({ "invalid Content-Transfer-Encoding in message\n", backtrace() })); transfer_encoding = lower_case(arr[0]); } And MIME.tokenize for a valid value such as Content-Transfer-Encoding: 8bit returns: Result: ({ /* 3 elements */ "Content-Transfer-Encoding", 58, "8bit" }) So in the Pike code the size of arr is neither 1 unless no encoding is specified (sizeof(arr)!=1 in the code). I think the offending code must be replaced by: if(!stringp(arr[2])) throw... string transfer_encoding = lower_case(arr[2] || ""); multiset possible_values = (< "7bit", "8bit", "binary", "quoted-printable", "base64" >); if(!possible_values[transfer_encoding]) throw... Can I change it this way ? PS: It seems to break especially with some Lotus Notes servers. / David Gourdelier

4 4

A note on .so files in 7.5
by Johan Sundstr�m (f�ngar heffaklumpar) ＠ Pike (-) developers forum 08 Nov '03

08 Nov '03

It seems .so files since recently (?) *need* to have a .pmod file that inherits them. A heads-up about such changes here is never wrong; it's not trivial to track down bugs related to such sudden incompatibility.

2 2

Nettle cipher.pmod
by Niels M�ller (igelkottsr�ddare) ＠ Pike (-) developers forum 08 Nov '03

08 Nov '03

I've made a slight reorganization of cipher.cmod: : Use a custom struct pike_cipher to keep track of information about : ciphers, instead of Nettle's primitive struct nettle_cipher. : : The only significant difference is that the pike version uses : set_key-functions that deal with invalid or weak keys, and throws pike : errors. : : The check_key_size method is gone, but that's the only user-visible : change. To test if a key is valid, just try to use it, and catch the : error. It passes the testsuite, but I haven't done any testing beyond that.

1 0

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