Pike-devel

pike-devel@lists.lysator.liu.se

3044 discussions

icc & INT64
by Mirar ＠ Pike developers forum 05 Apr '03

05 Apr '03

I see that icc no longer can compile long-long-int Pike's. [...]Gmp/mpz_glue.c(207): error: identifier "_I64_MIN" is undefined *i = MIN_INT64; ^ [...]Gmp/mpz_glue.c(210): error: identifier "_I64_MIN" is undefined *i = neg ? MIN_INT64 : MAX_INT64; ^ [...]Gmp/mpz_glue.c(210): error: identifier "_I64_MAX" is undefined *i = neg ? MIN_INT64 : MAX_INT64; ^ Did anyone do anything to how MAX & MIN_INT64 was defined?

2 2

Autodoc
by Martin Nilsson (har bott i google) ＠ Pike (-) developers forum 05 Apr '03

05 Apr '03

To all of you that helps out with the important tak of improving the Pike documentation (three, or so, people): The code/tt markup is now as follows. General computer-stuff should be marked with @tt, e.g. @tt{--help@}, @tt{/bin/sh@}, @tt{POST@}. Code expressions in flowing text should be marked with @expr, e.g. @expr{7@}, @expr{"POST"@}, @expr{i=i++;@}. Code expressions may be broken into several lines, as can @tt, but we have the possibility to break the expressions between tokens instead of at white spaces. Code snippets should be marked with @code, e.g. @code int i=4; i=i++; @endcode

3 5

7.4.20
by Johan Sundstr�m (folksk�dare) ＠ Pike (-) developers forum 04 Apr '03

04 Apr '03

A small heads up before airing on the Pike list; we have put up a 7.4.20 dist on the site now, and are busy preparing some binary dists for linux-ppc and solaris-8-sparc. Linux-x86 is already available. ftp://pike.ida.liu.se/pub/pike/latest-stable/Pike-v7.4.20.tar.gz Feel free to contribute a binary dist for your platform too; just make bin_export and upload the result along with your config.info to ftp://pike.ida.liu.se/incoming/. And thanks in advance. :-)

5 10

Autodoc
by Martin Nilsson (har bott i google) ＠ Pike (-) developers forum 03 Apr '03

03 Apr '03

(Not that it matters. If you use @code you'll get a preformatted paragraph with your code, while @expr gives you something that looks like @tt.)

1 0

7.4.18
by Martin Nilsson (har bott i google) ＠ Pike (-) developers forum 03 Apr '03

03 Apr '03

New release candidate is Pike 7.4.18. Unless someone has a problem with it I suggest it is released tomorrow.

1 0

Release time
by Johan Sundstr�m (folksk�dare) ＠ Pike (-) developers forum 03 Apr '03

03 Apr '03

Still two checkins in 7.4 unaccounted for in CHANGES: http://pike.ida.liu.se/development/cvs/pike.xml?v=7.4&build=217&between=200… grubba?

2 2

... and thanks for all the fish
by Martin Baehr 03 Apr '03

03 Apr '03

enough is enough! i've had it! with pike: calendar failing, floatingpoint bugs, blocking i/o callbacks upgrading woes with caudium: php problems parser bugs entity problems licensing problems camas problems with roxen: mysql dependancy complex rxml classes with sTeam: confusing web interface problems with access to pike lack of good search facility complicated irc access complex xslt for webpages. supports to many protocols time to switch! to python: negative indices in arrays clear indenting syntax no more braces and brakets to apache: excellent php support no more rxml bussinessfriendly license plenty of webmailers to choose from to zope: cool leaders (hi paul) instant and easy websites. large user community. it was a fun ride and i enjoyed working with all of you, but now it's time to move on. greetings, martin. -- interested in doing python programming, zope/python training, zope/python and/or unix system administration anywhere in the world. -- junior python working in europe csl-gmbh.net programmer zope.org (www.archlab|(www|db).hb2).tuwien.ac.at unix bahai.or.at iaeste.(tuwien.ac|or).at systemadministrator (stuts|black.linux-m68k).org is.(schon.org|root.at) Martin Bähr http://www.iaeste.or.at/~mbaehr/

8 16

SSL problems
by Alexander Demenshin 01 Apr '03

01 Apr '03

Hi there, I found that there is no way to enforce inquiry of client certificate, for instance. In particular, there is no variable "auth_level" in SSL.context class, but it is used in SSL.handshake. Obvious fix (adding this variable and setting it to AUTHLEVEL_ask) doesn't help much, though - certificate is not requested anyway (not properly, at least). Additional problem - server's request for certificate is not handled at all: "Certificate request not yet implemented." I do something wrong or? :) If not - is it planned to be fixed or it is better to use OpenSSL glue? Regards, /Al

1 0

Pike reference manual
by Martin Nilsson (har bott i google) ＠ Pike (-) developers forum 31 Mar '03

31 Mar '03

I've put some effort in the reference manual generation during the last days. The predef namespace is now the default namespace, but the other ones are still available and crosslinks works. If you have any suggestions while I'm at it, now is the time to communicate it...

3 3

Calendar failure
by Johan Sundstr�m (folksk�dare) ＠ Pike (-) developers forum 31 Mar '03

31 Mar '03

Interesting. The DST shift seems to do bad things to the Calendar module, or vice versa. Below, I am skeptical to (5), and find (7) onwards a bit odd, though perhaps correct as designed? Pike v7.4 release 13 running Hilfe v3.5 (Incremental Pike Frontend) > Calendar.parse("%Y-%M-%D %h:%m:%s %z","2003-03-30 01:00:00 Europe/Stockholm"); (1) Result: Second(Sun 30 Mar 2003 1:00:00 CET) > Calendar.parse("%Y-%M-%D %h:%m:%s %z","2003-03-30 02:00:00 Europe/Stockholm"); (2) Result: 0 > Calendar.parse("%Y-%M-%D %h:%m:%s %z","2003-03-30 03:00:00 Europe/Stockholm"); (3) Result: Second(Sun 30 Mar 2003 3:00:00 CEST) > Calendar.parse("%Y-%M-%D %h:%m:%s %z","2003-03-30 22:00:00 Europe/Stockholm"); (4) Result: Second(Sun 30 Mar 2003 22:00:00 CEST) > Calendar.parse("%Y-%M-%D %h:%m:%s %z","2003-03-30 23:00:00 Europe/Stockholm"); (5) Result: 0 > Calendar.Second(2003,3,30,1,0,0); (6) Result: Second(Sun 30 Mar 2003 1:00:00 CET) > Calendar.Second(2003,3,30,2,0,0); (7) Result: Second(Sun 30 Mar 2003 3:00:00 CEST) > Calendar.Second(2003,3,30,3,0,0); (8) Result: Second(Sun 30 Mar 2003 4:00:00 CEST) > Calendar.Second(2003,3,30,22,0,0); (9) Result: Second(Sun 30 Mar 2003 23:00:00 CEST) > Calendar.Second(2003,3,30,23,0,0); not in range (second 0..82799 exist) /usr/local/pike/7.4.13/lib/modules/Calendar.pmod/YMD.pmod:871: Day(Sun 30 Mar 2003)->get_unit("second",82800) /usr/local/pike/7.4.13/lib/modules/Calendar.pmod/Time.pmod:128: Second(Sun 30 Mar 2003 0:00:00 CET sharp)->create_backtry(23,0,0) /usr/local/pike/7.4.13/lib/modules/Calendar.pmod/YMD.pmod:2368: Second(Sun 30 Mar 2003 0:00:00 CET sharp)->create_backtry(2003,3,30,23,0,0 ) /usr/local/pike/7.4.13/lib/modules/Calendar.pmod/Time.pmod:109: Second(Sun 30 Mar 2003 0:00:00 CET sharp)->create(2003,3,30,23,0,0) object_program(Calendar.ISO): ISO->cSecond() HilfeInput:1: HilfeInput()->___HilfeWrapper() / Johan Sundström (folkskådare) Previous text: >2003-03-30 12:35: >Subject: http://pike.ida.liu.se/development/cvs/pike.xml?between=2003-03-30&and=2003… >-------------------------------------------------------------------- >Jag fick just följande överst på ovanstående sida: > >RXML run error: Illegal time "2003-03-30 23:59:59". > | <emit source="timerange"> > | <define variable="var.navi"> > | <cache flush-on-no-cache="yes" nocache="for date nav"> > | <nocache> > | <cache profile="browser"> > > / Henrik Grubbström (Lysator) >

6 30

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