Pike-devel January 2003

pike-devel@lists.lysator.liu.se

11 participants
88 discussions

Start a nNew thread

XPM and sort
by Mirar ＠ Pike developers forum 31 Jan '03

31 Jan '03

No, it isn't. The testsuite print fooled me. It's 2. Now I start to feel quite sane again :)

2 2

Re: OpenSSL wrapper vs Pike's SSL (Was: Bz2)
by Niels M�ller () ＠ Pike (-) developers forum 30 Jan '03

30 Jan '03

And I feel it's not worth the effort to try to do anything fancy with "secure deletion", mlock etc. mlock is pretty useless as it only works for root, and one don't want to encourage people to run their processes as root "for security reasons". (I'm sure not everybody agrees with that). Clearing strings and other memory when they're deallocated is reasonable, if you want to pay the extra cycles. Only question is how configurable that should be. A flag to make a particular string not appear in backtraces (or more generally, by sprintf("%O", s)) seems a little obscure, but it might be useful. Anything more complex than that? I don't think that's a good idea.

7 44

3.0 > 4.0?
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 30 Jan '03

30 Jan '03

This is rather bad: Pike v7.4 release 13 running Hilfe v3.5 (Incremental Pike Frontend) > for(int i=0; i<3.0; i++) >> if(i>4.0) error("Feh!\n"); Feh! HilfeInput:2: HilfeInput()->___HilfeWrapper() > Testsuite test committed.

3 4

zero_type() & UNDEFINED (bug?)
by Alexander Demenshin 29 Jan '03

29 Jan '03

Hi all, It is logical to expect that if zero_type(X) == zero_type(Y) then X == Y However: 0 == UNDEFINED but zero_type(0) != zero_type(UNDEFINED) this means that checks like some_value == UNDEFINED will never work correctly if some_value is an integer zero. Using zero_type() is not always convenient, at least not for readability... I suspect that this wasn't intended to operate this way, or? Regards, /Al

13 64

Bz2
by Mirar ＠ Pike developers forum 29 Jan '03

29 Jan '03

I noticed that we now have a Bz2 packer in the Pike tree. (Good job Andreas!) I did some work to get it to compile with my libbz2, and now it compiles and links fine. However, it segfaults on my machine and on some machines in xenofarm it gives funny errors in the testsuite (hence all the new yellow dots). I'm out of debugging tokens for today, so I don't mind at all if someone else makes it work... :)

18 149

CMOD and `-=
by Peta, jo det �r jag ＠ Pike developers forum 29 Jan '03

29 Jan '03

It looks like naming a function `-=() give you problems in the precompile.

1 0

MySQL configure-script is borken
by Marcus Agehall (Tr�dl�s) ＠ Pike (-) developers forum 29 Jan '03

29 Jan '03

And a closer examination of my Pikefarm logs shows that the build done by Pikefarm works correctly! Very strange.

1 0

MySQL configure-script is borken
by Marcus Agehall (Tr�dl�s) ＠ Pike (-) developers forum 29 Jan '03

29 Jan '03

I belive that the configure-script for the MySQL is broken. It does detect my MySQL installation and allows for the module to be compiled, but it doesn't detect the features of the lib correctly. I belive that the problem is that the PIKE_CHECK_MYSQL_FUNC in configure.in somehow doesn't link against the libmysqlclient.so lib. Can somebody confirm this or give me some other explaination of why it won't work?

1 0

Death to strlen! Death to the demoness Allegra Geller!
by Martin Nilsson (�skblod) ＠ Pike (-) developers forum 29 Jan '03

29 Jan '03

I have a theory that strlen is bad. 1. The function itself is completly redundant, since it is a direct alias for sizeof. The language is simpler and faster to learn without strlen. (Although not by much.) 2. We'd like things in Pike to be as general as possible, e.g. + should add any kind of ADT, not just integers. Hence it is bad to make specializations of general functions. 3. As a specialization strlen is flawed, since it accepts nonstring arguments. 4. strlen provides a "transition aid" for C programmers, who can still write strlen and get a somewhat expected result. This advantage is however consumed by the implication that since Pike has strlen and sizeof, and strlen works as in C, sizeof would also work as in C. Proposed course of actions: 1. Document strlen as deprecated. 2. Replace all strlen instances in Pike with sizeof.

9 22

Re: reasons why pike is better than python?
by Mirar ＠ Pike developers forum 29 Jan '03

29 Jan '03

At a closer inspection, it seems that the culprit is that I use |, not +. + is optimized, while | isn't. That should be easy to fix, shouldn't it? (mapping size 100000:) > gauge { m|=([-1:17]); }; Result: 0.160000 > gauge { m=([-2:17])|m; }; Result: 0.170000 > gauge { m+=([-3:17]); }; Result: 0.000000 <- lo! > gauge { m=([-4:17])+m; }; Result: 0.030000

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

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 January 2003