(I apologize profusely for the formatting--I'm writing this on a rather primitive
webmail system.)
Disclaimer: this is all from possibly faulty memory, except where it's pure
speculation.
Leopold Toetsch:
I'd like to layout some thougts, which get quite dim, when it comes to
threads. So there a
> Yep. But when it comes to multithreading you can't assume the same
> behavior on e.g. single or multiprocessor systems anway.
> leo
Sounds like a user-land implementation should be default then, to guarentee
consistancy across hardware let alone machines. Software targeted for specific
uses c
> Clint, I'm not sure which feature you mean is confusing here. I think you are
> referring to supporting .local outside of subs, and I agree with that. However,
> I think symbol tracking and scope checking is the high level language's
> responsibility so the example you provided really should not
At 10:46 AM 6/28/2003 -0400, Clinton Pierce wrote:
> If you want true variables around compilations units, please use globals
> or lexicals if they are in the same lexical pad.
>
> [1] This "feature" is IMHO at the boarders of imcc as the namespace
> instructions is. Should the HL handle these or
> The story is like this:
> - the "pseudo gloabal" declaration of C declares a variable usable in
> both subs. This was invented[1] to cover vars outside of all subs in a
> main execution stream, which is intersparsed with sub declarations, like
> a perl programm could be.
> - both subs "_foo1"
Luke Palmer <[EMAIL PROTECTED]> wrote:
> So, now that we're using CPS, will there be a standard way of seeing
> what the call stack is (for purposes of debugging/C/&c.)? Is
> it just a matter of looking in P0 and then P0's P0, and so on? Or
> will that croak in certain cases?
These are $HL featu
K Stol <[EMAIL PROTECTED]> wrote:
> (... skipping (1) and (2) ...)
>> 3) Threads
> Is 'the underlying model' the implementation of the OS running parrot (as
> oppposed to a self-made system,
On Linux there are many threading libs. E.g. pth (GNU portable threads)
and pthread (POSIX threads). The
In the meantime interpreter->warns has moved to the context structure
and gets now restored for CPS subroutine calls.
But there is a slight problem (as well as with e.g. pad_stacks)
When we have:
warningson 1
newsub .Sub, .Continuation, _func, _ret
...
invoke
and _func turns warnings off,
So, now that we're using CPS, will there be a standard way of seeing
what the call stack is (for purposes of debugging/C/&c.)? Is
it just a matter of looking in P0 and then P0's P0, and so on? Or
will that croak in certain cases?
Luke
- Original Message -
From: "Leopold Toetsch" <[EMAIL PROTECTED]>
To: "Luke Palmer" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, June 28, 2003 9:34 AM
Subject: Re: Tentative [PATCH]: valclone
> Luke Palmer <[EMAIL PROTECTED]> wrote:
> > Consider this Perl 6 code:
>
> >
(... skipping (1) and (2) ...)
> 3) Threads
> The underlaying model are posix threads if available. This implies
> that all interpreter data are shared by default. So we'll need per
> thread data: interpreter, prederef & JIT code ...
Is 'the underlying model' the implementation of the OS running
I'd like to layout some thougts, which get quite dim, when it comes to
threads. So there are a lot of questions.
1) Exceptions
There are 3 kinds of exception sources:
- hard: e.g. SIGFPE, SIGHUP. They get catched by signal handlers[1]
- soft: internal_exception()
- user: a C opcode signals a warnin
> Luke Palmer <[EMAIL PROTECTED]> wrote:
> > Consider this Perl 6 code:
>
> > sub refinc($var) {
> > my $myvar = $var;
> > $myvar += 1;
> > }
>
> > If you pass an integer in here, it should do nothing. However, if you
> > pass an object with an overloaded += in, it should
Clinton Pierce <[EMAIL PROTECTED]> wrote:
>> Yeah, I don't think you can use .local across subs like that. I think
>> .local means "local to this sub" and *inner subs aren't closures*. In
>> fact, I don't think inner subs are useful for much of anything at all.
> Aside from that, I think .local
Luke Palmer <[EMAIL PROTECTED]> wrote:
> Consider this Perl 6 code:
> sub refinc($var) {
> my $myvar = $var;
> $myvar += 1;
> }
> If you pass an integer in here, it should do nothing. However, if you
> pass an object with an overloaded += in, it should have the
> side-eff
Clinton Pierce wrote:
Sorry, the example was unnecessarily long.
After a quick reading of this, I'd have expected the value of "f" at the indicated point to be 1, but instead it's 2.
The dark chapters of imcc documentations and functionality are getting
revealed again ;-)
The story is like thi
16 matches
Mail list logo
