Pike-devel December 2014

pike-devel@lists.lysator.liu.se

5 participants
17 discussions

Failure to compile 8.0 on CentoOS 6.6 without g++ installed
by Peter Bortas ＠ Pike developers forum 16 Dec '14

16 Dec '14

Just noticed this failure on CentOS 6.6 where g++ is not installed: checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking how to run the C preprocessor... gcc -E checking how to run the C++ preprocessor... /lib/cpp configure: error: in `/home/zino/local/src/pike/build/linux-2.6.32-504.1.3.el6.x86_64-x86_64': configure: error: C++ preprocessor "/lib/cpp" fails sanity check config.log: configure:4087: g++ -E conftest.cpp /home/zino/local/src/pike/src/configure: line 4089: g++: command not found configure:4094: $? = 127 configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME "" | #define PACKAGE_TARNAME "" | #define PACKAGE_VERSION "" | #define PACKAGE_STRING "" | #define PACKAGE_BUGREPORT "" | /* end confdefs.h. */ | #ifdef __STDC__ | # include <limits.h> | #else | # include <assert.h> | #endif | Syntax error configure:4087: /lib/cpp conftest.cpp cpp: error trying to exec 'cc1plus': execvp: No such file or directory configure:4094: $? = 1 configure: failed program was: | /* confdefs.h. */ | #define PACKAGE_NAME "" | #define PACKAGE_TARNAME "" | #define PACKAGE_VERSION "" | #define PACKAGE_STRING "" | #define PACKAGE_BUGREPORT "" | /* end confdefs.h. */ | #ifdef __STDC__ | # include <limits.h> | #else | # include <assert.h> | #endif bash-4.1$ /lib/cpp --version cpp (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11)

3 3

Can Pike 8.0 drop string_to_unicode/unicode_to_string?
by Chris Angelico 13 Dec '14

13 Dec '14

These functions are somewhat misnamed anyway (they convert to UTF-16 byte streams), and you can always explicitly manipulate UTF-16 using the Charset.encoder/decoder functions. UTF-8 is far more common, and the corresponding string_to_utf8/utf8_to_string functions are more usefully named too. Is Pike 8.0 a good time to drop string_to_unicode() and unicode_to_string()? ChrisA

4 4

Re: Can Pike 8.0 drop string_to_unicode/unicode_to_string?
by Chris Angelico 12 Dec '14

12 Dec '14

On Fri, Dec 12, 2014 at 8:55 PM, Peter Bortas @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > No. Nothing gets dropped from 8.0 at this point. If they should be > dropped in the future we could still potentially mark them as > depricated in 8.0. > > I'm not sure I understand your objection to them though. Is it just > that they are redundant? I keep getting reminded of them when I tab-complete "string_", but my main objection is the confusing name. If they were called string_to_utf16/utf16_to_string, as Arne suggests, then they wouldn't be confusing; I'm not sure they're even needed at all, but they aren't a *problem* per se. ChrisA

1 0

visit to Linköping
by H. William Welliver III 10 Dec '14

10 Dec '14

I’ll be in Linköping visiting with Tobi and Company the weekend of December 5-7. If anyone is interested, perhaps we could broaden the scope to have more of a general Pike development meeting. Feel free to drop a note (this list is probably a fine place) if anyone’s interested! Bill

7 11

8.0 windows build status
by H. William Welliver III 09 Dec '14

09 Dec '14

I’ve got pike 8.0 building (for the most part) on windows. A few problems that still exist: 1. not all of the modules are working properly, though i suspect that’s primarily due to my build environments libs being out of whack. 2. Hilfe doesn’t seem to work properly: it starts and then immediately exits. 3. there is a problem on modules that execute pike scripts using $(RUNPIKE)… these scripts run on the host computer, and since RUNPIKE by default points to the newly built binary, the build isn’t able to continue because the host isn’t windows. It seems like it should be using the pike script in the build directory, which would probably be $(FINAL_PIKE), but I don’t want to make that change to configure.in without some feedback. For now, I’m going to move on to other things until some more feedback arrives. Bill

2 1

feedback request: ZIP archives on module path
by H. William Welliver III 06 Dec '14

06 Dec '14

I’ve committed a new feature to 8.1 that I’d like to get feedback on. The feature extends master()->add_module_path() to allow the path to point to a ZIP archive which will be searched as if it were a regular module directory. Things I’d especially like feedback on: 1. Is the current API acceptable (the simplest form is built into add_module_path(), more complex use cases may be accounted for using lower level APIs) 2. A minor overhead exists (a mapping lookup on the path prefix) which may impact performance for non-archive path searches. Since classes are cached after lookup, is this overhead a concern? Quick benchmarking doesn’t seem to indicate a significant performance change, however I’d like to hear thoughts from users whose use case may vary from my own. 3. Does it make sense to extend this feature to add_*_path? My sense is yes, but wanted to check. Sample Usage: 1. Create a zip file with the following structure: modules/ modules/Some.pmod/ … etc 2. Run pike -M path/to/some.zip 3. Access Some.whatever… Bill

1 0

xenofarm?
by Stephen R. van den Berg 04 Dec '14

04 Dec '14

Xenofarm seems to have been out of order since a while, correct? -- Stephen.

6 7

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 December 2014