Pike-devel

pike-devel@lists.lysator.liu.se

4 participants
3044 discussions

[Pike-devel] the Pike module system
by Mikael Brandstr�m (ogg! ogg! ogg!) ＠ Pike (-) developers forum 03 Sep '02

03 Sep '02

To nitpick: no module is ever executed, and no module will be executed at pike startup. There has, however, been discussions on a .pikerc and/or /etc/pikerc program that would be cloned and executed on Pike startup, although I don't remember if this has been suggested only for interactive Pike (hilfe). The latter would be preferable IMO. / Mikael Brandström (ogg! ogg! ogg!) Previous text: >2002-09-03 20:14: >Subject: the Pike module system >-------------------------------------------------------------------- >exactly - there's no module executed/loaded at the startup, and that's the >feature which would be interesting to have - for the purposes described >elsewhere in this thread. > > / Marek Habersack (Grendel) >

2 1

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

03 Sep '02

Ok, I'm getting annoyed. Quit babbling about fork(). Fork is HARD to support and has less portable semantics than Process.create_process(). Yes, there are some instances when it would be useful but it WILL NOT be supported in Pike with threads. Personally I don't care if it is POSIX or not, because while POSIX may be a standard, it is a backwards and awkward standard that doesn't actually allow you to write useful applications. On top of that, many OS only implement parts of POSIX or have bugs in some of their POSIX calls. Using POSIX as a guide for Pike APIs is like using ASCII as a guide for drawing fonts. / Fredrik (Naranek) Hubinette (Real Build Master) 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) >

2 1

[Pike-devel] Green threads
by Fredrik (Naranek) Hubinette (Real Build Master) ＠ Pike (-) developers forum 03 Sep '02

03 Sep '02

Actually, there is a POSIX-compliant way to create a new stack. The GNU pthreads package use this and it's an interesting read. However, many existing thread packages use the stack pointer to identify which thread is currently running, which means that it is impossible for software that creates it's own stack to co- exist with these thread packages. This was all discovered while trying to make Pike dynamically allocate more C stack. There is even a libc call for doing this on some platforms, but unless the thread package is aware of what is going on it crashes horribly when you run that call in a threaded application. When it comes right down to it, it's better (and easier) to implement a better pthreads package then to implement green threads into Pike. / Fredrik (Naranek) Hubinette (Real Build Master) Previous text: >2002-08-29 15:06: >Subject: Green threads >-------------------------------------------------------------------- >I'm actually not that deep into the intricacies of thread >implementations either, but afaik there's no reasonably standard way >to create a new C stack without getting a new OS level thread at the >same time. Also, longjmp() is only defined to be able to jump to some >state "higher up" in the same stack and not between different stacks. > >Many times it'd probably work to allocate a slab of memory with >malloc() and then use a bit of implementation-dependent magic to set >up a jmp_buf struct that points to it, and then start using longjmp() >and setjmp() to switch between the stacks. It's just a "small matter >of programming" to get that working on all the different platforms. > >Libraries for this probably exists already. It'd be very appreciated >if someone set out to find one and verify that it works well on all >the platforms Pike supports. > > / Martin Stjernholm, Roxen IS >

1 0

[Pike-devel] Re: pike-devel@caudium.info
by Peter Bortas ＠ Pike developers forum 03 Sep '02

03 Sep '02

*greps through the archive* Yes, under the subject "Getting hold of a working LysKOM client". The answer to that question had been answered much earlier in the thread so I never read that far. / Peter Bortas Previous text: >2002-09-03 21:06: >Subject: Re: pike-devel(a)caudium.info >-------------------------------------------------------------------- >On Tue, Sep 03, 2002 at 08:50:03PM +0200, Peter Bortas @ Pike developers forum wrote: >> You haven't asked. > >i HAVE asked!!!!!!! >noone answered!!!! > >on the pike list of course. >(because asking inside of lyskom for a mailinglist for it, >was a chicken end egg problem i did not manage to solve due to >a lack of understanding swedish) > >> *click* *click* There you go: >> http://lists.lysator.liu.se/mailman/listinfo/pike-devel > >excellent!!! >of course i prefer having the lists on lysator too. >hedda would you mind getting that set up? >we'll drop the lists on the caudium server as soon as it does. > >greetings, martin. >ps: any way i can get the complete conference exported so that i can read it? > > > / Brevbäraren >

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