I think we are talking about the same issues, but we can't seem to get
in sync on the terminology. I'm going to try to get off the
merry-go-round by recapitualting the two approaches.
RFC178
- globals are shared unless localized
- file-scoped lexicals are shared by all code in the file
- block-s
> "SWM" == Steven W McDougall <[EMAIL PROTECTED]> writes:
PRL> All threads see the same compiled subroutines
>>
>> Why? Why not allow two different threads to have a different view of
>> the universe?
SWM> 1. That's how it works in compiled languages. You have one .exe, and
SWM> all threads
> "SWM" == Steven W McDougall <[EMAIL PROTECTED]> writes:
>> Single thingee access mediation, should be done automatically by perl.
>> The multi-thingee complex mediation should have the user step in, since
>> solving it (correctly and efficiently) is a complex problem.
SWM> I'm not sure we
On Sat, Sep 02, 2000 at 07:22:08PM +, Nick Ing-Simmons wrote:
>
> This is from a perl5.7.0 (well the current perforce depot) compiled
> with -pg and then run on a smallish example of my heavy OO day job app.
>
> The app reads 7300 lines of "verilog" and parses it with (tweaked) Parse-Yapp
>
> Single thingee access mediation, should be done automatically by perl.
> The multi-thingee complex mediation should have the user step in, since
> solving it (correctly and efficiently) is a complex problem.
I'm not sure we have a common understanding of the terms we are using.
Can you give som
What I'm trying to do in RFC178 is take the thread model that you get
in compiled languages like C and C++, and combine it with the Perl5
programming model in a way that makes sense.
There may be reasons not to follow RFC178 in Perl6. Maybe
- it's too hard to implement
- there are performance pr
> "PRL" == Perl6 RFC Librarian <[EMAIL PROTECTED]> writes:
PRL> =head2 Freezing state for keys and values efficiently
PRL> I believe this problem can be solved by using the vtable for the
PRL> hash to wrap any mutating functions with a completion routine that
PRL> will advance the iterator t
> "SWM" == Steven W McDougall <[EMAIL PROTECTED]> writes:
SWM> All I want the language to guarantee is internal thread-safety.
SWM> Everything else is the user's problem.
Somehow I would have thought that goes without saying.
But I don't agree that all the rest is a user issue, is too short
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Implementation of hash iterators
=head1 VERSION
Maintainer: Tom Hughes <[EMAIL PROTECTED]>
Date: 20 Aug 2000
Last Modified: 4 Sep 2000
Mailing List: [EMAIL PROTECTED]
Version: 2
Number: 136
St
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Transaction-enabled variables for Perl6
=head1 VERSION
Maintainer: Szabó, Balázs <[EMAIL PROTECTED]>
Date: 17 Aug 2000
Last Modified: 02 Sep 2000
Mailing List: [EMAIL PROTECTED]
Version: 5
Numbe
> SWM> Question: Can the interpreter determine when a variable becomes
> SWM> shared?
> SWM> Answer: No. Then neglecting to put a :shared attribute on a shared
> SWM> variable will crash the interpreter. This doesn't seem very Perlish.
> Err, no. It won't crash the interpreter. It'll make the sc
> "SWM" == Steven W McDougall <[EMAIL PROTECTED]> writes:
>> Aha, I get it. -internals has been assuming that one _must_ specify
>> the sharing. You want it to be infered.
>> I think that's asking for too much DWIMery.
SWM> Question: Can the interpreter determine when a variable becomes
SWM
Raptor <[EMAIL PROTECTED]> writes:
>What is interesting to me :
>
>1. "push" is used more than any of the other array ops, even than "shift"
>2. "use" is very good candidate for speedup
>3. We still use very much "goto" :")
>4. "each" is used more than "values" and "keys"
>5. Things like "hex,chr,
hi,
here is one simple script (Requires Parse::RecDescent) that count operators
in scripts.(and my fisrt grammar ;") )
OK. I started this against my current perl installation.
(it is not pure RH6.2 install, but many things are added)
i.e.
find /perl_dir -name *.pm | ./count.pl | tee allops.txt
i
14 matches
Mail list logo
