Pike-devel

pike-devel@lists.lysator.liu.se

4 participants
3044 discussions

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

Re: sslfile
by Martin Nilsson (saturator) ＠ Pike (-) developers forum 28 Jan '04

28 Jan '04

query_fd previously returned -1. / Martin Nilsson (saturator) Previous text: >2004-01-28 19:35: >Subject: Re: sslfile >-------------------------------------------------------------------- >What methods, specifically? I know that die() is one of them... > >Bill > >On Wednesday, January 28, 2004, at 12:30 PM, Martin Nilsson (saturator) >@ Pike (-) developers forum wrote: > >> After the rewrite of SSL.sslfile some methods available before are >> gone. >> Is that a mistake in terms of removal or in terms of not adding >> compatibility? > > > > / Brevbäraren >

1 0

sslfile
by Martin Nilsson (saturator) ＠ Pike (-) developers forum 28 Jan '04

28 Jan '04

After the rewrite of SSL.sslfile some methods available before are gone. Is that a mistake in terms of removal or in terms of not adding compatibility?

1 0

win32 builds
by Peter Bortas ＠ Pike developers forum 28 Jan '04

28 Jan '04

If someone feel they don't have enough exitement in their lives feel free to test <URL:http://peter.bortas.org/pikedev/Pike-7.4.35beta-win32-bhelliom.exe> or <URL:http://peter.bortas.org/pikedev/Pike-7.5.17alpha-win32-bhelliom.exe> They are totally untested and only intended for testing some changes to the installation package: * ICON rescource in pike.exe * New installer icon * Added possibility to use 10 instead on 1 argument to pike.exe on the command line. * Fixed up my win32 compileation environment again. Observe: I haven't even tried to run these executables since my win32 testing system is currently spread all over my workbench. Feel free to report back if it does work though.

3 17

Re: Pike @ Debian
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 27 Jan '04

27 Jan '04

Hm. Marek, if I just made an ass of myself by assuming you just took some quarantine time off the list, and thus incorrectly addressed you in third person like this, I'm sorry. (For which I whole-heartedly put all blame on Embee's sudden recurring diversion tactics, in a not very successful effort at humour on my part. Got to practice some more. :-)

3 3

Re: Pike @ Debian
by Per Hedbor () ＠ Pike (-) developers forum 27 Jan '04

27 Jan '04

Then they simply won't work in Pike 7.5. If you had used pike -x module you would have got the .pmod files for free. / Per Hedbor () Previous text: >2004-01-26 21:41: >Subject: Re: Pike @ Debian >-------------------------------------------------------------------- >On Mon, Jan 26, 2004 at 09:35:07PM +0100, Per Hedbor () @ Pike (-) developers forum scribbled: >> Even pure C-modules generate .pmod files nowdays. Which is what I >> wrote, I think. >None of the pexts, caudium or php4 modules do. What's your point? > >marek > > > > / Brevbäraren >

2 1

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