Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

eureka reinstall
by Peter Bortas ＠ Pike developers forum 07 Jan '10

07 Jan '10

Some time next week I'll upgrade eureka from Solaris Express snv_81 to whatever the latest stable OpenSolaris release is. There is no straight forward upgrade path from SXCE to OpenSolaris, so the machine will be reinstalled and the data restored from backup. That means there will be some substancial downtime for people using services on eureka. More details later.

4 13

Tabular.pike 1.8
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 05 Jan '10

05 Jan '10

+ if(String.width(out)>8) + out=string_to_utf8(out); Ok, seriously, I think for every proper use of String.width (are there any?) there are at least two improper ones. If the string is supposed to be transport encoded with UTF-8, you need to do it for _all_ strings, otherwise you will get invalid UTF-8 if the string contains characters > 127 but < 256. But who says that a "tabular" should be UTF-8 encoded anyway? For a format that has no builtin encoding indicator, transport en/decoding should be the task of the caller.

4 9

convert_1_to_0() truncating instead of skipping?
by Stephen R. van den Berg 03 Jan '10

03 Jan '10

I noticed that e.g. convert_1_to_0() (actually any conversion that goes from wider to narrower) in stralloc.c just chops off the wider part instead of actually leaving out the characters which cannot be represented in the narrower string. Is there are a reason why it is truncated instead of skipped? I'd presume that actually omitting the characters which cannot be represented would be more correct. Simply truncating them generates garbage. And, subsequently, if everyone agrees to the above, can/should I fix this? -- Sincerely, Stephen R. van den Berg. "If you make people think they're thinking, they'll love you; but if you really make them think, they'll hate you."

2 2

String.strim_whites(), any objections of other suggestions?
by Stephen R. van den Berg 02 Jan '10

02 Jan '10

I found myself reimplementing this functionality in a number of projects over the course of the past ten years, and I finally bit the bullet. Any objections when this is committed? Or perhaps better suggestions as to the naming and/or implementation? commit dda53cbadcf125f207878e8a5ac04ac936b21782 Author: Stephen R. van den Berg <srb(a)cuci.nl> Date: Fri Jan 1 23:12:18 2010 +0100 New member String.strim_whites which sanitises a string by stripping leading and trailing whitespace, in addition to reducing all strains of spaces and tabs to a single space. diff --git a/lib/modules/String.pmod/module.pmod b/lib/modules/String.pmod/module.pmod index 2696d93..e70c848 100644 --- a/lib/modules/String.pmod/module.pmod +++ b/lib/modules/String.pmod/module.pmod @@ -6,6 +6,7 @@ constant Buffer = __builtin.Buffer; constant count=__builtin.string_count; constant width=__builtin.string_width; constant trim_whites = __builtin.string_trim_whites; +constant strim_whites = __builtin.string_strim_whites; constant trim_all_whites = __builtin.string_trim_all_whites; constant Iterator = __builtin.string_iterator; constant SplitIterator = __builtin.string_split_iterator; diff --git a/src/builtin.cmod b/src/builtin.cmod index 4085f4e..1dda4dd 100644 --- a/src/builtin.cmod +++ b/src/builtin.cmod @@ -750,6 +750,55 @@ PIKEFUN string string_trim_whites (string s) RETURN string_slice (s, start, end + 1 - start); } +/*! @decl string strim_whites (string s) + *! @belongs String + *! + *! Trim leading and trailing spaces and tabs from the string @[s]. + *! Also reduces strains of multiple spaces and tabs to a single space. + */ +PMOD_EXPORT +PIKEFUN string string_strim_whites (string s) + errname String.strim_whites; + optflags OPT_TRY_OPTIMIZE; +{ size_t len = s->len; + void *src = s->str; + unsigned shift = s->size_shift; + unsigned foundspace = 0; + struct string_builder sb; + init_string_builder_alloc (&sb, len, shift); + sb.known_shift = shift; + + switch (shift) { +#define DO_IT(TYPE) \ + { TYPE *start = src, *end = start+len, *dst = (void*)sb.s->str; \ + for (; start < end; start++) { \ + int chr = *start; \ + if (chr != ' ' && chr != '\t') break; \ + } \ + for (; start < end; start++) { \ + int chr = *start; \ + if (chr == ' ' || chr == '\t') \ + if (foundspace) \ + continue; \ + else \ + chr=' ',foundspace=1; \ + else \ + foundspace=0; \ + *dst++ = chr; \ + } \ + len = dst - (TYPE*)sb.s->str; \ + } + case 0: DO_IT (p_wchar0); break; + case 1: DO_IT (p_wchar1); break; + case 2: DO_IT (p_wchar2); break; +#undef DO_IT + } + if (foundspace) + len--; + sb.s->len = len; + RETURN finish_string_builder (&sb); +} + /*! @decl string trim_all_whites (string s) *! @belongs String *! diff --git a/src/builtin_functions.h b/src/builtin_functions.h index 9da458a..1183d21 100644 --- a/src/builtin_functions.h +++ b/src/builtin_functions.h @@ -181,6 +181,7 @@ PMOD_EXPORT void f_ctime(INT32 args); PMOD_EXPORT void f_mkmapping(INT32 args); PMOD_EXPORT void f_string_count(INT32 args); PMOD_EXPORT void f_string_trim_whites(INT32 args); +PMOD_EXPORT void f_string_strim_whites(INT32 args); PMOD_EXPORT void f_string_trim_all_whites(INT32 args); PMOD_EXPORT void f_program_implements(INT32 args); PMOD_EXPORT void f_program_inherits(INT32 args); -- Sincerely, Stephen R. van den Berg.

3 2

Re: String.strim_whites(), any objections of other suggestions?
by Stephen R. van den Berg 02 Jan '10

02 Jan '10

Peter Bortas @ Pike developers forum wrote: >A more descriptive name would be good. The trouble with "more descriptive" is that it implies absolute accuracy in the naming. I.e. the following names crossed my mind: - sanitise_whites(): The definition of "to sanitise" is subject to personal taste, and therefore inaccurate. - strip_and_trim_whites(): Some whites are stripped, but not all, and some tabs are being replaced by spaces, so this name is inadequate as well. - replace_multiple_with_one_and_trim_whites(): would be sort of accurate, but is ridiculously long. Considering the above, I thought that "strim_whites()" is not so bad, since it somehow contracts "strip and trim" to "strim", which means it doesn't say "strip" explicitly (since it doesn't strip everything), and it does more than trimming alone. And since the name is too short to exactly describe what happens, one needs to look it up in the docs to find out what it does exactly anyway. AFAIK there is no equivalent function in other languages, so borrowing the name from there was/is not possible (maybe someone can prove me wrong here?). -- Sincerely, Stephen R. van den Berg. "The difficult we do today; the impossible takes a little longer."

2 1

More rtldebug to get better info when gc_mark problems happen.
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 13 Dec '09

13 Dec '09

Um, the latest commit to Makefile (by mast) was a mistake, no?

4 4

precompile problem on 7.8.352
by Bill Welliver 09 Dec '09

09 Dec '09

I've been trying to track down a problem when compiling CMODs on 7.8.352. It seems that there should be a define for DEFAULT_CMOD_STORAGE, but it never makes it to the output file. I verified that it's in the declarations at one point, but it seems to disappear or is ignored when it comes time to output. Any suggestions as to the problem? Bill

1 0

sscanf bug?
by Martin Bähr 04 Dec '09

04 Dec '09

hi, shouldn't those two examples be the same? > array_sscanf("124dsf134", "%d%s%3d"); (5) Result: ({ /* 2 elements */ 124, "dsf134" }) > array_sscanf("124dsf134", "%d%s%d"); (6) Result: ({ /* 3 elements */ 124, "dsf", 134 }) greetings, martin.

3 2

patch for string_builder_vsprintf
by Arne Goedeke 30 Nov '09

30 Nov '09

Hello, I noticed that only %f is supported in string_builder_vsprintf(). I would like to use something else in JSON2, so it would be nice if someone could review this and maybe commit. arne diff --git a/src/stralloc.c b/src/stralloc.c index eb60b8b..e75d45b 100644 --- a/src/stralloc.c +++ b/src/stralloc.c @@ -2945,13 +2945,17 @@ PMOD_EXPORT void string_builder_vsprintf(struct string_builder *s, flags, min_width, precision); break; - /* FIMXE: TODO: Doubles (ie 'a', 'e', 'E', 'g', 'G'). */ - /* %f used in modules/Image/colors.c. */ + case 'a': + case 'g': + case 'G': + case 'e': + case 'E': case 'f': { double val = va_arg(args, double); size_t bytes; + char nfmt[] = { '%', *(fmt-1), 0 }; if (PIKE_ISNAN(val)) { /* NaN */ @@ -2974,9 +2978,9 @@ PMOD_EXPORT void string_builder_vsprintf(struct string_builder *s, break; } /* FIXME: Field lengths and precision. */ - if ((bytes = SNPRINTF(NULL, 0, "%f", val))) { + if ((bytes = SNPRINTF(NULL, 0, nfmt, val))) { p_wchar0 *p = string_builder_allocate(s, bytes, 0); - size_t check = SNPRINTF((char*)p, bytes+1, "%f", val); + size_t check = SNPRINTF((char*)p, bytes+1, nfmt, val); if (check != bytes) { Pike_fatal("string_builder_vsprintf(): snprintf(%f) is not " "trustworthy: %"PRINTSIZET"u != %"PRINTSIZET"u\n",

3 2

The OOB working test
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 28 Nov '09

28 Nov '09

I noticed that the OOB check fails with TIMEOUT in 7.8 on my linux box. It produces SEMIWORKING in 7.6, so something is different in the configure script, although the test itself is identical. The log doesn't say much. Here's from 7.8: configure:70034: checking how well OOB handling works configure:70366: /home/mast/Pike/no-changes-7.8/build/linux-x86_64/smartlink gcc -o conftest -g -O3 -pipe -ggdb3 -m64 -I/home/mast/Pike/no-changes-7.8/build/linux-x86_64/bundles/include -I/usr/local/include -I/home/mast/Pike/no-changes-7.8/src -I/home/mast/Pike/no-changes-7.8/build/linux-x86_64 -L/home/mast/Pike/no-changes-7.8/build/linux-x86_64/bundles/lib64 -L/home/mast/Pike/no-changes-7.8/build/linux-x86_64/bundles/lib/64 -L/home/mast/Pike/no-changes-7.8/build/linux-x86_64/bundles/lib/. -L/usr/local/lib -L/usr/lib/gcc/x86_64-linux-gnu/4.4 -R/usr/lib/gcc/x86_64-linux-gnu/4.4 conftest.c -ldl -lrt -lnsl -lm -lpthread -lcrypt >&5 conftest.c: In function 'my_socketpair': conftest.c:362: warning: incompatible implicit declaration of built-in function 'memset' conftest.c: In function 'ping': conftest.c:527: warning: incompatible implicit declaration of built-in function 'exit' conftest.c:535: warning: incompatible implicit declaration of built-in function 'exit' conftest.c: In function 'pong': conftest.c:552: warning: incompatible implicit declaration of built-in function 'exit' conftest.c: In function 'pang': conftest.c:570: warning: incompatible implicit declaration of built-in function 'exit' conftest.c: In function 'main': conftest.c:591: warning: incompatible implicit declaration of built-in function 'exit' configure:70366: $? = 0 configure:70366: ./conftest my_socketpair: succeeded configure:70366: $? = 0 configure:70381: result: TIMEOUT Compared to 7.6: configure:50000: checking how well OOB handling works configure:50342: /home/mast/Pike/frozen/build/linux-x86_64/smartlink gcc -o conftest -g -O2 -pipe -Wa,--execstack -I/home/mast/Pike/frozen/build/linux-x86_64/bundles/include -I/usr/local/include -I/home/mast/Pike/frozen/src -I/home/mast/Pike/frozen/build/linux-x86_64 -L/home/mast/Pike/frozen/build/linux-x86_64/bundles/lib -z execstack -R/usr/local/lib -L/usr/local/lib -R/usr/X11R6/lib -L/usr/X11R6/lib -R/usr/lib/gcc/x86_64-linux-gnu/4.4 -L/usr/lib/gcc/x86_64-linux-gnu/4.4 conftest.c -ldl -lrt -lnsl -lm -lpthread -lcrypt >&5 conftest.c: In function 'my_socketpair': conftest.c:333: warning: incompatible implicit declaration of built-in function 'memset' conftest.c: In function 'ping': conftest.c:498: warning: incompatible implicit declaration of built-in function 'exit' conftest.c:506: warning: incompatible implicit declaration of built-in function 'exit' conftest.c: In function 'pong': conftest.c:523: warning: incompatible implicit declaration of built-in function 'exit' conftest.c: In function 'pang': conftest.c:541: warning: incompatible implicit declaration of built-in function 'exit' conftest.c: In function 'main': conftest.c:562: warning: incompatible implicit declaration of built-in function 'exit' configure:50345: $? = 0 configure:50351: ./conftest my_socketpair: succeeded configure:50354: $? = 0 configure:50375: result: SEMIWORKING I've tried changing the compiler flags to match 7.6 (-O2 instead of -O3 etc), but it doesn't change anything. What could the problem be?

2 2

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