Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Process.split_quoted_string
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 09 Sep '02

09 Sep '02

Is there any particular reason why Process.split_quoted_string("") returns (1) Result: ({ /* 1 element */ "" }) ? Shouldn't it return the empty array?

1 0

Mapping a variable in an object from C
by Marek Habersack (Grendel) ＠ Pike (-) developers forum 06 Sep '02

06 Sep '02

How can I map a C variable in a C module between two objects? I.e. object1 (C): storage->somevar; object2 (C or Pike) anothervar -> object1.storage->somevar; map_variable doesn't seem to be the right solution, or is it?

2 10

Mapping a variable in an object from C
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 06 Sep '02

06 Sep '02

>Then you need to index it out, using object_index_no_free. Or rather, since you wanted to set it, use object_set_index. Both are declared in object.h.

1 0

-x
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 06 Sep '02

06 Sep '02

I have now implemented the flag -x in the master. pike -x foo will run the program which Tools.Standalone.foo resolvs to using the module system. rsif has been adapted to use this system, and I made a small "pv" as well. Now for `pike -x module'...

6 10

empty_string
by David Hedbor (I live in interesting times) ＠ Pike (-) developers forum 06 Sep '02

06 Sep '02

Just recently an empty_string was added to Pike. This is a problem because PHP4 also has a global empty_string variable. I fixed this exact problem way back in modules/spider/spider.c. A quick grep shows that this problem exists in Parser.HTML and now globally (the two use a different empty string however). Suggestion: make it pike_empty_string or empty_pike_string or something that is unique. That way PHP won't break. I should note that this time the problem was more obvious as it broke compilation rather than being a run time error. If there are no complaints, I will make this change.

1 0

Re: Pike dev import/export to/from LysKOM
by David Hedbor (I live in interesting times) ＠ Pike (-) developers forum 05 Sep '02

05 Sep '02

> huh? where am i expecting the users to change? > getting cc'd messages exported is an implementation issue of the exporter > and has nothing to do with user behaviour. In the statement Martin's commented: > as i said elsewhere, if they are not interresting then cc is not needed > at all, if they are interresting enough to get cc'd then they should > get exported too. You said right there "if they are not interesting then cc is not needed at all". However "cc" in LysKOM is, as Martin pointed out, not used in the same way it's used in mail. It's not always used to add possibly interested recpients to a message but most often used to divert an off-topic discussion from one conference to another. Now, it is at times used to simply add a recipient that might possibly be interested as well. The only REAL difference between a normal recipient and a CC recipient is that comments to a message only gets sent to forums which has an actual recipient. CC recipients are ignored in that case. / David Hedbor (I live in interesting times) Previous text: >2002-09-05 16:20: >Subject: Re: Pike dev import/export to/from LysKOM >-------------------------------------------------------------------- >On Thu, Sep 05, 2002 at 03:55:01PM +0200, Martin Nilsson (Fake Build Master) @ Pike (-) developers forum wrote: >> > as i said elsewhere, if they are not interresting then cc is not needed >> > at all, if they are interresting enough to get cc'd then they should >> > get exported too. >> The common practice in LysKOM is to CC the message just when a thread >> changes conference. I don't think you'll succeed in making all LysKOM >> users change their behavior so that it suits you. > >huh? where am i expecting the users to change? >getting cc'd messages exported is an implementation issue of the exporter >and has nothing to do with user behaviour. > >> LysKOM does not map fully to emails. >> Accept that or upgrade to a LysKOM client. > >i do accept that, there will be a gap, i am just trying to get this gap >to become smaller. > >> (and to prevent whining about unavailability of LysKOM clients for your >> platform, I want to stress that your platform is part of your choice). > >bah, the whole thing is about choice! >most of all i choose not to use multiple programs to do the same job. >for editing i only use vi, >for programming only pike >and to send and receive messages, only email. > >greetings, martin. > > > / Brevbäraren >

1 0

[Pike-devel] argv[0]?
by Fredrik (Naranek) Hubinette (Real Build Master) ＠ Pike (-) developers forum 05 Sep '02

05 Sep '02

POSIX sucks / Fredrik (Naranek) Hubinette (Real Build Master) Previous text: >2002-09-03 17:41: >Subject: argv[0]? >-------------------------------------------------------------------- >What I understood from the previous discussion, some people don't consider >POSIX calls portable (mainly because Win32 doesn't support the calls). If >my understanding is correct, then I must say that I don't like the >approach. POSIX is much more of a standard than Win32 will ever be >(i.e. how can something used by one company and one family of products be a >standard?) > > / Marek Habersack (Grendel) >

5 5

Bug?
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 05 Sep '02

05 Sep '02

master.pike: [...] ({"nowarnings",tmp->NO_ARG,({"-W", "--woff", "--no-warnings"})}), [...] case "no-warnings": [...] Borde det inte stå "nowarnings" i casen också?

2 1

argv[0]?
by Leif Stensson, Lysator ＠ Pike developers forum 05 Sep '02

05 Sep '02

("Leif", not "Lief".) My point wasn't really that fork() was a part of unix whether one likes it or not, but rather that fork() was a perfectly good API to process creation _for an operating system_. It doesn't follow from this that the operating system API must be literally reflected in the API of a programming language; especially not a programming language for portable script-like application, rather than low-level system-specific programs. It might be nice to provide access to the operating system functions generally, so that people who really need them to do lower-level things can do so. But in my opinion, that's not a high priority for a language like Pike. / Leif Stensson, Lysator Previous text: >2002-09-03 17:50: >Subject: argv[0]? >-------------------------------------------------------------------- >What about people other than "we"? As Lief (I think) stated fork() is at the >base of any *nix system whether one likes it or not - as such, it is very >useful since pike runs on many *nix systems... > > / Marek Habersack (Grendel) >

1 0

GTK and events
by Mikael Brandstr�m (ogg! ogg! ogg!) ＠ Pike (-) developers forum 05 Sep '02

05 Sep '02

Is it possible to send an event/signal to a GTK widget? I have searched the manuals extensively, but not found anything helpfull. I've found perl-gtk examples on how to do it *shrug*, but not anything that works in Pike. The reason is that I want to propagate events to a sister-widget.

1 0

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