Pike-devel

pike-devel@lists.lysator.liu.se

1 participants
3045 discussions

Start a nNew thread

7.8 blockers
by Mirar ＠ Pike developers forum 03 May '08

03 May '08

...hm, I thought I had a newer Pike. Doesn't trigger with 7.7.39, is it fixed?

2 2

inherit resolving problem
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 03 May '08

03 May '08

If I create a module X.pmod with the contents class Y { class X { } } and then tries to run the following program class Z { inherit X.Y; } void main() { } I will get the error that 'Index Y not present in module "X".' Doing other things with X.Y is however possible, like declaring a variable "X.Y foo;" in the Z class or making the statement werror("%O\n", indices(X.Y)); in main().

3 6

Re: MySQL or Pike?
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 24 Apr '08

24 Apr '08

>It is MySQL 5.0: >http://dev.mysql.com/doc/refman/5.0/en/myodbc-configuration-connection-para… This page seems to be about some ODBC connector, which I'm sure you are not using? >Oh, I forgot to mention that I'm NOT EVEN USING the mapping :). The >error/strange behaviour purely results from creating the mapping: > >................catch { >........................mapping(string:int) tst_opt = >(["connect_options":2]); >........................dbconn = Sql.Sql( QUERY(db_string)); >................}; > >I didn't get to the part of actually using the mapping yet. > >Strange, strange, strange... Well, yes, that _is_ weird. :-)

1 0

MySQL or Pike?
by cschalkwijk 24 Apr '08

24 Apr '08

When using MySQL 5.0 with Pike 7.4 I get an error message (only) when a called stored procedure has an empty resultset. Calling the stored procedure with a MySQL management application does not result in any problems. I get the following message: PROCEDURE {X} can't return a result set in the given context Now, is this Pike or MySQL? If it's Pike, what am I doing wrong? If it's MySQL, well, any suggestions? 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 3

Getopt mark II
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 19 Apr '08

19 Apr '08

(or rather Getopt mark III, since I've already rewritten the current one, although no functionality was changed then) I've been working a bit on a new Argument parser, and would like some input. In reality there will be two different way of using the argument parser, which really doesn't share any code but is convenient to do at the same time. The first one is a "I just want to get this over with" kind of interface: void main(int num, array argv) { mapping args = Arg.parse(argv); argv = args[Arg.REST]; } The output will contain ([ "foo":1 ]) if the argument is --foo and ([ "foo":"bar" ]) if the argument is --foo=bar. There is no fancy stuff to handle default values (just or it with another mapping) or options that may or may not have values (e.g. -bar=foo will produce ([ "b":1, "a":1, "r":"foo" ]) and --foo x --bar will just produce ([ "foo":1 ]) and then stop processing the line). The other mode is the (supposedly) easy yet powerful mode that you would use for more mature applications. class Parser { inherit Arg.Options; Arg verbose = NoArg("-v")|NoArg("--verbose")|Env("VERBOSE"); Arg level = HasArg("-l")|HasArg("--level"); } void main(int n, array argv) { Parser p = Parser(argv); // Index magic. Some like it, some not so much. if( p->verbose ) werror("Level %s\n", p->level); } Which is extended in class Parser { // The name for now. inherit Arg.OptionsSupreme; Arg verbose = NoArg("-v")|NoArg("--verbose")|Env("VERBOSE"); // These are used in the automatically generated --help response. string help_pre = "This program is like awesum."; string verbose_help = "Increases the verbosity of the program."; // Called when/if verbose is set to a value. void verbose_cb(string arg) { werror("Verbosity is on.\n"); } } Does this match the long list of requirements that I've heard from others?

5 17

questions about new stuff in 7.8
by Martin B�hr 19 Apr '08

19 Apr '08

hi, i am just looking through the CHANGES file to find out what all the new stuff is and try it out. - the getter-setter example fails with: getset.pike:4:Illegal ` identifier. getset.pike:4:parse error, unexpected `TOK_IDENTIFIER', expecting `error' or `'('' getset.pike:7:parse error, unexpected `TOK_RETURN' getset.pike:10:Illegal ` identifier. getset.pike:10:parse error, unexpected `TOK_IDENTIFIER', expecting `error' or `'('' getset.pike:13:parse error, unexpected `'='' getset.pike:14:parse error, unexpected `'}'' getset.pike:14:Missing ';'. getset.pike:20:parse error, unexpected `'}'' getset.pike:20:Missing ';'. getset.pike:26:parse error, unexpected `';'', expecting `')'' getset.pike:26:Missing ')'. getset.pike:27:Missing ';'. getset.pike:29:Missing '}'. getset.pike:29:Unexpected end of file. it looks almost like it is not working at all. (i am using the pikefarm build to test this) is there a switch that needs to be turned to activate this? - does portable bytecode affect the performance? did the dumped bytecode contain architecture specific optimizations before? or were those always generated at runtime? in other words, where does the machinecode generation come in? - what is the missing example in ADT.Struct supposed to demonstrate? - what do all these FIXME: Rewrite comments mean? rewrite the code or rewrite the CHANGES entry? greetings, martin.

4 4

Need prototype of a function at runtime
by PeterPan 17 Apr '08

17 Apr '08

I tried to use _typeof() to get the type of a function, but I found if a lambda function modified a var in the environ, the type "function" would be returned instead of "function(<arg type list>:<result type>)". for example: # cat lambda.pike void t(function f) { write("%O\n",_typeof(f)); } void main() { int k; t(lambda(int ig){}); t(lambda(int ig){k++;}); } # pike lambda.pike function(int : zero) function With second lambda function ,_typeof() just return "function", but for the first lambda it returned "function(int : zero)". The prototype of the two lambda function is SAME, then my question is "how can I get the prototype at runtime?"

1 0

Re: [Bug] Regexp.PCRE("n*") multiple match endless loop
by bertrand.lupart＠linkeo.com 16 Apr '08

16 Apr '08

Mirar @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Aha! > > Well, it seems like those two are depending on the end of the previous > hit a little too much. This gives a more appropriate behaviour: > > /home/mirar/.zshenv:21: HISTCHARS can only contain ASCII characters > Index: module.pmod.in > =================================================================== > RCS file: /pike/data/cvsroot/Pike/7.7/src/modules/_Regexp_PCRE/module.pmod.in,v > retrieving revision 1.8 > diff -u -r1.8 module.pmod.in > --- module.pmod.in 19 Feb 2004 13:53:38 -0000 1.8 > +++ module.pmod.in 16 Apr 2008 13:11:53 -0000 > @@ -133,7 +133,7 @@ > if (stringp(with)) res->add(with); > else res->add(with(subject[v[0]..v[1]-1])); > > - i=v[1]; > + if (i!=v[1]) i=v[1]; else res->add(subject[i..i++]); > } > > res->add(subject[i..]); > @@ -203,7 +203,7 @@ > if (intp(v) && !handle_exec_error([int]v)) > return this; > callback(split_subject(subject,v),v); > - i=v[1]; > + if (i!=v[1]) i=v[1]; else i++; > } > } Wonderful. ----8<----8<----8<----8<---- > string foo = "foobar"; > Regexp.PCRE("o+")->replace(foo,""); (1) Result: "fbar" > Regexp.PCRE("o*")->replace(foo,""); (2) Result: "fbar" > Regexp.PCRE("^o*")->replace(foo,""); (3) Result: "foobar" > Regexp.PCRE("o*$")->replace(foo,""); (4) Result: "foobar" > Regexp.PCRE("o+")->matchall(foo, lambda(mixed s){ werror("%O\n",s); } ); ({ /* 1 element */ "oo" }) (5) Result: Regexp.PCRE.StudiedWidestring("o+") > Regexp.PCRE("o*")->matchall(foo, lambda(mixed s){ werror("%O\n",s); } ); ({ /* 1 element */ "" }) ({ /* 1 element */ "oo" }) ({ /* 1 element */ "" }) ({ /* 1 element */ "" }) ({ /* 1 element */ "" }) ({ /* 1 element */ "" }) (6) Result: Regexp.PCRE.StudiedWidestring("o*") ---->8---->8---->8---->8---- Should be applied to 7.6 too. Thanx, -- Bertrand LUPART http://bertrand.gotpike.org/

1 0

[Bug] Regexp() and $ (was: Re: [Bug] Regexp.PCRE("n*") multiple match endless loop)
by bertrand.lupart＠linkeo.com 16 Apr '08

16 Apr '08

Johan Sundström (Achtung Liebe!) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > > If you don't have a PCRE enabled Pike, then there should be a solution > > with Regexp(). But it seems like there's a little bug with $ on > > Regexp(), but one bug at a time :) > > Not if it is the stone age Regexp(), as that one did/does not handle > strings with null characters in it (except in cases where you really > *want* it to treat \0 as end-of-string). Interresting to know. \0 could be replaced beforehand using replace(), then Regexp() used. Even in this case, i guess we have a problem: ^ works: ----8<----8<----8<----8<---- > string bar = "oofoo"; > Regexp("^[o]+")->replace(bar, ""); (1) Result: "foo" ---->8---->8---->8---->8---- While $ seems not: ----8<----8<----8<----8<---- > Regexp("[o]+$")->replace(bar, ""); (2) Result: "f" ---->8---->8---->8---->8---- -- Bertrand LUPART http://bertrand.gotpike.org/

1 0

[Bug] Regexp.PCRE("n*") multiple match endless loop (was: Re: Regexp troubles)
by bertrand.lupart＠linkeo.com 16 Apr '08

16 Apr '08

Mirar @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > >However, i'd like to know why while doing this: > >----8<----8<----8<----8<---- > >> object r = Regexp.PCRE.Studied("[\\W]*$"); > >> r->replace(foo, ""); > >---->8---->8---->8---->8---- > >Pike eats all my CPU and the command never finish. > > Good question. The PCRE code should be easy to read though, feel free > to investigate? :) When using n* (zero or more n), Regexp.PCRE._pcre()->exec() returns an array of two identical int. ----8<----8<----8<----8<---- $ pike Pike v7.6 release 112 running Hilfe v3.5 (Incremental Pike Frontend) > Regexp.PCRE._pcre("o+")->exec("foobar",0); (1) Result: ({ /* 2 elements */ 1, 3 }) > Regexp.PCRE._pcre("o*")->exec("foobar",0); (2) Result: ({ /* 2 elements */ 0, 0 }) ---->8---->8---->8---->8---- For each replace, Regexp.PCRE()->replace() attempts to execute the regular expression at the end of the previous hit. It uses the return from exec as a start and end offset. Since the start and end offset returned by exec() are the same, this results in a infinite loop. ----8<----8<----8<----8<---- $ pike Pike v7.6 release 112 running Hilfe v3.5 (Incremental Pike Frontend) > string foo = "foobar"; > Regexp.PCRE("o+")->replace(foo,""); ({ /* 2 elements */ 1, 3 }) -1 (1) Result: "fbar" > Regexp.PCRE("o*")->replace(foo,""); ({ /* 2 elements */ 0, 0 }) ({ /* 2 elements */ 0, 0 }) ({ /* 2 elements */ 0, 0 }) ({ /* 2 elements */ 0, 0 }) ... infinite loop ... ---->8---->8---->8---->8---- Please note that Regexp.PCRE()->matchall() obviously suffers from the same problem: ----8<----8<----8<----8<---- $ pike Pike v7.6 release 112 running Hilfe v3.5 (Incremental Pike Frontend) > string foo = "foobar"; > Regexp.PCRE("o+")->matchall(foo, lambda(mixed s){ werror("%O\n",s); } ); ({ /* 1 element */ "oo" }) (1) Result: Regexp.PCRE.StudiedWidestring("o+") > Regexp.PCRE("o*")->matchall(foo, lambda(mixed s){ werror("%O\n",s); } ); ({ /* 1 element */ "" }) ({ /* 1 element */ "" }) ... infinite loop ... ---->8---->8---->8---->8---- I don't know which code should be fixed for now. I don't understand the documentation for exec() when it returns an array here: <http://pike.ida.liu.se/generated/manual/modref/ex/predef_3A_3A/Regexp/P CRE/_pcre/exec.html> -- Bertrand LUPART http://bertrand.gotpike.org/

4 4

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