Threading Debate-- Where ??
I have personally agonized about the threading issue, basically w/o every writing a usable script in it. I would like to know where the archive is, its not really obvious, before comenting that we may need two cores, on with one w/o. cheers, john
Re: Threading Debate-- Where ??
At 03:28 PM 9/18/00 +, John van V wrote: I have personally agonized about the threading issue, basically w/o every writing a usable script in it. I would like to know where the archive is, its not really obvious, before comenting that we may need two cores, on with one w/o. Well, you can check out the p5p archives at http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/ and wade through them to pick the bits out. That's about the best archive of stuff at the moment. Dan --"it's like this"--- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
Re: Perl Implementation Language
In message [EMAIL PROTECTED] Dan Sugalski [EMAIL PROTECTED] wrote: As for the language we implement perl in (and thus ultimately need to translate to the compiler-target language), I'm thinking of something like Chip's PIL. (Or PIL itself--I've not actually seen it) Is there any information on PIL available anywhere? Basically the macro/tracking translator from hell that'll automagically generate header files, provide all the permutations of vtable functions, and suchlike things. Doesn't this run a significant danger of leading us straight back into the perl5 problem of making debugging of the source code more or less impossible? Tom -- Tom Hughes ([EMAIL PROTECTED]) http://www.compton.nu/ ...You have the capacity to learn from mistakes. You will learn a lot today.
Re: Accessing a variable's attributes (was Re: RFC 241 (v1) ...)
At 04:04 PM 9/18/00 +0100, Simon Cozens wrote: On Mon, Sep 18, 2000 at 10:51:52AM -0400, John Porter wrote: I would think that if it could be done at all, it would only be in extension (formerly XS) code. Why? I don't want to go to C just to add a flag to a variable. That smacks of making easy things hard and hard things impossible. You'll note that that isn't the motto of Perl. I'd rather this sort of thing be visible everywhere as well. I don't see any reason that we should force folks to write extensions to get this stuff. (The deadline for collecting ideas passed two weeks ago. Why is this all still going on?) Who meets deadlines anyway? :) This is more a question of ramifications than anything else, and those are bound to show up in chunks as development proceeds. Dan --"it's like this"--- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
Re: Accessing a variable's attributes (was Re: RFC 241 (v1) ...)
Simon Cozens wrote: (The deadline for collecting ideas passed two weeks ago. Why is this all still going on?) Because there are still many worthy ideas which have not surfaced yet. Which is the higher priority? -- John Porter We're building the house of the future together.
Re: Accessing a variable's attributes (was Re: RFC 241 (v1) ...)
On Mon, Sep 18, 2000 at 04:04:56PM +0100, Simon Cozens wrote: On Mon, Sep 18, 2000 at 10:51:52AM -0400, John Porter wrote: I would think that if it could be done at all, it would only be in extension (formerly XS) code. Why? I don't want to go to C just to add a flag to a variable. That smacks of making easy things hard and hard things impossible. You'll note that that isn't the motto of Perl. I'll have to go with John here. Mucking about with variable attribute flags (with the exceptions of the fixed set which have been proposed) falls firmly into the "hard but possible" realm of things. It should be done in XS code. Also, just being able to tack flags onto a variable means each variable (that has a flag) would have to carry around a hash! Anyhow, this doesn't mean someone couldn't write a module to do it and then you use that. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse "You are wicked and wrong to have broken inside and peeked at the implementation and then relied upon it." Tom Christiansen in 31832.969261130@chthon
