Pike-devel

pike-devel@lists.lysator.liu.se

3 participants
3048 discussions

nettle
by Mirar ＠ Pike developers forum 04 Feb '04

04 Feb '04

| AC_MSG_ERROR([Cannot compile --with-bignums without the GMP library | It is highly recommended that you install a working GMP | library on your system as that will add features to Pike | required by many applications (such as Roxen). However, | if you know that you do not need GMP, you may re-run configure | with the option --without-bignums instead.]) Considering that Pike now needs Nettle to have at least a semi-usable make verify, maybe adding such a test to configure for Nettle too wouldn't be a bad idea?

4 9

Nettle or no Nettle?
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 03 Feb '04

03 Feb '04

Hm, what's up with this: misao:/space/hack/Pike/7.5/build% ls -l lib/modules/*Nettle* -rw-rw-r-- 1 marcus local 147 Feb 3 22:44 lib/modules/Nettle.pmod -rwxrwxr-x 1 marcus local 92147 Feb 3 22:44 lib/modules/___Nettle.somisao:/space/hack/Pike/7.5/build% ldd lib/modules/___Nettle.so libnettle.so.2 => /usr/lib/libnettle.so.2 (0x6ff97000) libc.so.6 => /lib/libc.so.6 (0x0fe80000) libgmp.so.3 => /usr/lib/libgmp.so.3 (0x6ff43000) /lib/ld.so.1 => /lib/ld.so.1 (0x08000000) misao:/space/hack/Pike/7.5/build% grep HAVE_LIBNETTLE post_modules/Nettle/nettle_config.h #define HAVE_LIBNETTLE 1 misao:/space/hack/Pike/7.5/build% make run_hilfe /space/hack/Pike/7.5/build/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/space/hack/Pike/7.5/build/master.pike Pike v7.5 release 17 running Hilfe v3.5 (Incremental Pike Frontend) > indices(Nettle); (1) Result: ({ }) >

1 0

mktime
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 03 Feb '04

03 Feb '04

The function my_tm_diff() in buildint_functions.c is bugged. It doesn't differentiate between months of different length, but treats all months as having 30 days, 10 hours and 30 minutes. This means that e.g. the dates 2004-01-31-12:00:00 and 2004-02-01-01:30:00 will be considered _equal_. The recent failures of the testsuite is due to these state of affairs. The bug can be reproduced with mktime(gmtime(1075550400)) The bug is likely to occur with any date being the last day of a month containing 31 days, after 10:30 AM.

3 3

Pike module initialization at compile time
by Alexander Demenshin 03 Feb '04

03 Feb '04

Hi, I asked this once on general Pike list, nobody answered, so I'll try here :) The question is - why create() is called when module is inherited, not when it is instaniated? If there is Parent.pmod (with create() defined), and Child.pmod, which inherits Parent, then create() defined in Parent will be called when Child is _compiled_. Compilation of Parent won't call it's create() method. In case if module is _imported_, such behavior is logical, but when inherited... What especially confuses me is the fact that regular parent class definition won't cause such effect... Any ideas/explanations? :) Is this "behavior by design" or? Regards, /Al

5 18

Re: Default backend and thread backends?
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 02 Feb '04

02 Feb '04

Correction: Thread A might release its read lock after checking that the object is thread local, and then the fact that no other thread can access it is relevant. I don't think it'd be good to make threads keen on releasing the read lock though, since they can't reasonably do any significant amount of work without reading global objects.

1 0

7.6
by Mirar ＠ Pike developers forum 02 Feb '04

02 Feb '04

How is the plan for 7.6? Would it be possible to split 7.5 into a 7.7 and a 7.6 and just fix bugs in the 7.6 branch until it can be released? (Just asking. Or nagging... :) )

1 0

mktime
by Mirar ＠ Pike developers forum 02 Feb '04

02 Feb '04

| home/xenofarm/xenoclient/pike-7.5/orchid.mirar.org/buildtmp/Pike7.5-2004013…: | Test 6748 (shift 0) (CRNL) failed. | 1: mixed a() { int x=time(); return mktime(localtime(x)) == x;; } | 2: mixed b() { return 1; } | 3: | | Error: Cannot convert. | Unknown program: mktime(12,5,18,31,0,104,0,-3600) | testsuite:1: testsuite()->a() What's with that, and how was it fixed by this: | 2004-02-02 03:02:22 (nilsson) Pike/7.5/src/svalue.c, (+12/-2) (2271 lines) dl | \a and \v is recognized on the input side, so let's format them as | such on the output side as well. ??!?

2 1

A correction to Protocols.HTTP.Server.Port
by Alexander Demenshin 29 Jan '04

29 Jan '04

Hi, During long (and very active) run of simple web server, implemented using standard module, found a problem: Indexing the NULL value with "set_nonblocking". /usr/local/pike/7.4.28/lib/modules/Protocols.pmod/HTTP.pmod/Server.pmod/Request.pike:62: Protocols.HTTP.Server.Request()->attach_fd(0,Protocols.HTTP.Server.Port(),bin/shttpd()->Handler) /usr/local/pike/7.4.28/lib/modules/Protocols.pmod/HTTP.pmod/Server.pmod/Port.pike:56: Protocols.HTTP.Server.Port()->new_connection() The fix is trivial (for 7.4.28; but the problem exists in 7.5.* as well): --- Port.pike~ 2004-01-30 00:45:12.000000000 +0100 +++ Port.pike 2004-01-30 00:45:12.000000000 +0100 @@ -52,6 +52,10 @@ static void new_connection() { Stdio.File fd=port->accept(); + + if (!fd) + return; // There is nothing to accept --aldem + Request r=request_program(); r->attach_fd(fd,this_object(),callback); } The reason is unknown - why there is nothing to accept, but I guess it happens under _very_ heavy load (or DoS). Regards, /Al

2 1

Culture Surprises in Remote Software Development Teams
by Martin Bähr 29 Jan '04

29 Jan '04

hi, i found this interresting article, which as it touches on our situation, i think is worth reading. Culture Surprises in Remote Software Development Teams http://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=105 Technology has made it possible for organizations to construct teams of people who are not in the same location, adopting what one company calls "virtual collocation." Worldwide groups of software developers, financial analysts, automobile designers, consultants, pricing analysts, and researchers are examples of teams that work together from disparate locations, using a variety of collaboration technologies that allow communication across space and time. Although solving the problems of space and time is difficult, these are not the only issues. Work that takes place over long distances means that communication will often involve different cultures. Participants may be surprised by such interactions because they have not considered various cultural differences and how they impact the daily work of long-distance teams. Our own culture is invisible to us. "We don't see our own ways of doing things as conditioned in the cradle," writes Esther Wanning, author of Culture Shock! USA. "We see them as correct, and we conclude that people from other countries have grave failings." The goal of this article is to review various cultural differences likely to appear in the work setting and explore their implications for virtual collocation of software development teams. We begin with a definition of culture and various dimensions of cultural difference that have emerged. Then we examine two cases: (1) one in which the team members are collocated; and (2) one involving the team in virtual collocation. From this analysis we draw some practical implications. greetings, martin.

1 0

Re: Pike @ Debian
by David Hedbor ＠ Pike developers forum 29 Jan '04

29 Jan '04

The one and only way to compile Pike modules that should be endorsed and/or developed is "pike -x module". That's it. If it doesn't work it. If it requires the entirety of Pike, deal with it. That's about all I have to say. / David Hedbor Previous text: >2004-01-26 21:32: >Subject: Re: Pike @ Debian >-------------------------------------------------------------------- >On Mon, Jan 26, 2004 at 08:55:02PM +0100, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum scribbled: >> _No_. It can _not_ be tailored to the distribution, because then the >> Pike modules you distribute could only be compiled with that >> distrubution. That would be totally useless. >Huh? pike.m4's purpose is would be to: > > a) detect the presence of the Pike binaries on the system (or requested > components thereof) > > b) inform the application where the .h, .pmod etc. etc. files are located. > >How could that prevent the code from being compiled on different operating >systems??? Since when the contents of the information above matters and not >the way you get the information? If you have 10 OSes and each of them keeps >the .h files in a different location, but you have one pike.m4 which has a >macro > > PIKE_C_HEADER_FILES > >which sets the PIKE_HEADERS variable to the location of the .h files on the >system, then where is the problem? > >You put > >CC_INCLUDES=$(PIKE_HEADERS) > >in your makefile and your code perfectly compiles on any OS, no matter where >it keeps the files. Suspecting that you might have misunderstood the >'tailoring' part - I meant by it that the maintainer of the Pike port for a >particular system can modify it and customize for his platform. I didn't >mean it has to be done in the Pike core, all gods of the universe forbid! As >said previously somewhere, the .m4 could just source a config file put in a >well-known location. That would make it extremely configurable and flexible, >not to mention simple. > >marek > > > > > / Brevbäraren >

6 7

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