Pike-devel

pike-devel@lists.lysator.liu.se

2 participants
3046 discussions

Pike 7.8/Roxen5 problem
by Coen Schalkwijk 28 Nov '10

28 Nov '10

Hi All, I have a serious issue with Roxen5/Pike7.8: there seems to be no block_crypt anymore of AES: Crypto.AES cr = Crypto.AES(); cr->set_decrypt_key(enc_key); decrypted = cr->crypt_block(String.hex2string(in)) - "\0"; Throws an exception with Pike7.8/Roxen5 Where can I find any 7.8 documentation by the way? -- Met vriendelijke groet / With kind regards / mit besten Grüßen, Coen Schalkwijk Software Engineer coen.schalkwijk(a)rtl.nl <mailto:coen.schalkwijk@rtl.nl> coen(a)rtlinteractief.nl <mailto:coen@rtlinteractief.nl> +31 (0)35 671 8915

3 2

io redirection question
by Csürke Tamás 22 Nov '10

22 Nov '10

Hi, Is there any command in pike to make the same that expect does in TCL (i.e. http://en.wikipedia.org/wiki/Expect)

4 4

sscanf
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 21 Nov '10

21 Nov '10

Well, the weirdnesses keep popping up as I write this program... :-) Pike v7.8 release 473 running Hilfe v3.5 (Incremental Pike Frontend) > int z; > sscanf("HOPP", "%*s%n", z); (1) Result: 2 > z; (2) Result: 4 > "HEJHOPP"[3..]; (3) Result: "HOPP" > sscanf("HEJHOPP"[3..], "%*s%n", z); (4) Result: 2 > z; (5) Result: 7 > Surely the result of sscanf("HOPP", ... should be the same regardless of how I compute the value "HOPP"?

3 5

Constant definition is not constant.
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 18 Nov '10

18 Nov '10

Pike v7.8 release 350 running Hilfe v3.5 (Incremental Pike Frontend) > class c { int foo() { constant a = 17<<1; return a; } }; > class c { int foo() { constant a = 17<<0; return a; } }; Compiler Error: 1: Constant definition is not constant. > Excuse me? Why is 17<<0 less constant than 17<<1?

2 3

Ignoring config.h.in
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 29 Oct '10

29 Oct '10

Git status bothers me about untracked files: # Untracked files: # (use "git add <file>..." to include in what will be committed) # # src/modules/Gz/zlib_machine.h.in # src/modules/Pipe/config.h.in # src/modules/SANE/config.h.in # src/modules/_Image_GIF/config.h.in # src/modules/_Image_JPEG/config.h.in # src/modules/_Image_TIFF/config.h.in # src/modules/_Image_XFace/config.h.in # src/modules/_Regexp_PCRE/pcre_machine.h.in # src/post_modules/_ADT/config.h.in # src/post_modules/_Image_SVG/config.h.in Turns out that the patterns for these files in .gitignore have trailing whitespace, something cvs apparently ignored but git does not. It'd be nice if the conversion had taken care of this, but I guess the only option now is to correct the patterns at the branch heads?

5 21

Outage for CodeLibrarian
by Peter Bortas ＠ Pike developers forum 25 Oct '10

25 Oct '10

I'm tracking down some bugs in the live installation of Librarian, so it might go up and down a bit for the next hour.

2 2

inotify
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 25 Oct '10

25 Oct '10

>hope you returned home well. I remember us talking about that you have a >file notification module somewhere that you wanted to commit into 7.9. As >i still have my inotify stuff lying around, do you think you can make >your code available somewhere in some git so that i can have a look and >possibly merge (if there is something to merge). I'll have to clear it with Roxen first, since it's part of the product. BTW: It seems inotify is on the way to being obsoleted by fanotify. BTW2: I just performed some comparisons of Pike's default string hashing function (aka DO_HASHMEM()) with CRC32, and the variance difference to a perfect hash function for the both are comparable, with CRC32 consistently being somewhat better. ZERO below is the pessimal hashfunction that returns zero for all strings. Hashfunction: DO_HASHMEM CRC32 ZERO Hilfe: 0.0368884 0.0359854 2.67415 GTK1: 0.0319663 0.0301390 1.90823 GTK2: 0.0320599 0.0305676 1.96876 Shuffler: 0.0496259 0.0475051 2.42460

3 3

Merge vs rebase policy
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 24 Oct '10

24 Oct '10

Shall we try to decide on a policy for merging vs rebasing? Personally I prefer simple linear histories. That makes it easy to follow the log, and it simplifies bisecting. Iow, the default would be to use "rebase = true" in tracking branches. Branches and merges still have their place, but imo they're better suited for more long-lived topic branches.

5 12

"Corrected" shell quoting
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 11 Oct '10

11 Oct '10

821fbe3a seems to have broken compilation on Solaris: sh: syntax error at line 1: `(' unexpected *** Error code 2 The following command caused the error: MAKE="`if [ "xmake" = "x" ]; then echo "${MAKE-make}"; else echo "make"; fi`" export MAKE && "${MAKE}" `$MAKE force --no-print-directory >/dev/null 2>&1 && echo --no-print-directory || :` "MAKE=${MAKE}" "CONFIGUREARGS=" "BUILDDIR=build/${PIKE_BUILD_OS:-`uname -s -r -m|sed "s/ /-/g"|tr "[A-Z]" "[a-z]"|tr "/()" "___"`}" METATARGET= _make_in_builddir Frankly I don't understand the change; the double quotes inside the backquotes need to be escaped, otherwise they end the double-quoted string which starts with "BUILDDIR=... Different quotes do not nest in sh, when a startquote is found the matching end quote is looked for using only the rules which applies to the start quote. So to have "s inside a double-quoted string (which also happens to contain a couple of backquotes), they need to be escaped.

2 3

merges in git
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 11 Oct '10

11 Oct '10

Hm, maybe any branch which does not have "/" in its name could be considered a "main branch"?

3 3

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