I'm looking for, but not finding, information regarding the character
type and encoding on parrot io objects.
As an example of why... I found this in io.ops :
op write(in PMC) {
PMC *p = $1;
STRING *s = (VTABLE_get_string(interpreter, p));
if (s) {
PIO_write(interpreter, PIO_STDOUT(int
Leopold Toetsch wrote:
[snip]
> [1] when we want to thaw/clone big structures, we should have some means
> to estimate the amount of needed headers. If we will not have enough, we
> do a DOD run before clone/thaw and then turn DOD off - it will not yield
> any more free headers anyway. This can avo
Leopold Toetsch wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
> >class freezer {
> >class thawer {
> >class cloner {
>
> [ big snip ]
>
> Do you expect that these are overridden by some languages using parrot?
> I.e. that p
Nicholas Clark wrote:
>
> On Sat, Aug 30, 2003 at 10:13:02PM -0400, Benjamin Goldberg wrote:
> > Nicholas Clark wrote:
>
> > > The attacker can craft a bogus CGITempFile object that refers to any
> > > file on the system, and when this object is destroyed it
Leopold Toetsch wrote:
>
> Nicholas Clark <[EMAIL PROTECTED]> wrote:
> > -#define PMC_sub(pmc) ((parrot_sub_t)((pmc)->cache.pmc_val))
> > +#define PMC_sub(pmc) (*((parrot_sub_t *)&((pmc)->cache.pmc_val)))
>
> This seems to work. Thanks for the patch.
> (the tcc tinderbox seems to be missing a m
Nicholas Clark wrote:
>
> On Fri, Aug 29, 2003 at 05:30:37PM +0200, Leopold Toetsch wrote:
>> I think, we need a general solution for freeze, dump and clone. As
>> shown
>
> I don't know if this is relevant here, but I'll mention it in case.
> For perl5 there isn't a single good generic clone sys
Leopold Toetsch wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
> > Actually, I think the following interface would be better:
>
> >void freeze(PMC *freezer);
> >void thaw (PMC *thawer);
>
> I'm thinking of (in horrible pseudo code
Dan Sugalski wrote:
>
> On Fri, 29 Aug 2003, Leopold Toetsch wrote:
>
>> Dan Sugalski <[EMAIL PROTECTED]> wrote:
>>> I think we'd be better served getting the freeze/thaw stuff in and
>>
>> We were just discussing this in the f'up.
>
> I read those, but I wanted to make sure the discussion went
Piers Cawley wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> writes:
[snip]
>>> Reading or writing from the hash does a lookup in the backing database
>>> and reads or writes from it. A handy thing, with the variable getting
>>> in the way of reads or wri
Dan Sugalski wrote:
>
> I've talked about this before and generally I've assumed that people
> know what I'm talking about, but that's not true anymore, so an
> explanation of this is in order.
>
> "Active Data" is data that takes some active role in its
> use--reading, writing, modifying, deleti
Juergen Boemmels wrote:
>
> Leopold Toetsch <[EMAIL PROTECTED]> writes:
>
> > Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
> >
> > > #define PARROT_DECLARE_STATIC_STRING(name, cstring) \
> >
> > [ big snip ]
> >
> > While Jue
Leopold Toetsch wrote:
>
> We currently have constant Key and Sub PMCs both created from the
> packfile at load time. They live in the constant_table pointing to a
> constant PMC pool. But we need more.
>
> We have allover the core code like this:
>
>string_from_cstring(interpreter, "pIt",
Juergen Boemmels wrote:
> Leopold Toetsch wrotes:
>
> > We currently have constant Key and Sub PMCs both created from the
> > packfile at load time. They live in the constant_table pointing to a
> > constant PMC pool. But we need more.
> >
> > We have allover the core code like this:
> >
> >st
Luke Palmer wrote:
>
> I started working on some XS code for embedding a Parrot interpreter in
> Perl. I ran into a few problems:
>
> 1) I don't know XS :-) (good way to learn, though)
>
> 2) What do I put as stacktop in Parrot_init()? I can't just use a
>local variable in
Gordon Henriksen wrote:
>
> Benjamin Goldberg wrote:
>
> > Gordon Henriksen wrote:
[snip]
> > > [3] Unshift hack #1: Where commit appears in the above, exit the
> > > grammar, trim the beginning of the string, and re-enter. (But that
> > > forces the
Gordon Henriksen wrote:
>
> Now, I don't really have much of an opinion on compound strings in
> general. I do want to address one particular argument, though—the lazily
> slurped file string.
>
> On Thursday, August 21, 2003, at 07:22 , Benjamin Goldberg wrote:
>
&
Dan Sugalski wrote:
>
> At 12:07 AM -0400 8/19/03, Benjamin Goldberg wrote:
> >There are a number of shortcomings in the API, which I'd like to address
> >here, and propose improvments for.
>
> You're conflating language level strings with low-level string
Dan Sugalski wrote:
>
> At 9:27 PM -0400 8/21/03, Benjamin Goldberg wrote:
> >I would like for Parrot to have some way of creating Weak References; I
> >think that this is probably a vital feature.
>
> No, it isn't, and we've discussed this before. (You
Gordon Henriksen wrote:
>
> On Saturday, August 23, 2003, at 08:17 , Benjamin Goldberg wrote:
>
> > The reason this is safe to do is because it's *only* created by the
> > dod,
>
> Allocating memory during garbage collection?
Why not? Or at least, why no
Togos wrote:
>
> What's the reasoning behind putting the object a
> method is being called on in P2 instead of in the
> first parameter of the method? I have a feeling that
> putting it as the first parameter of the method would
> make the lives of the python folks a little bit
> easier. Would i
Robert Spier wrote:
>
> > > The HLL doesn't know, how many ops one source line will need.
> >
> > Not *normally*, but if it's including code which is already literal
> > assembler, it does: Imagine a version of lex/yacc wherein the the
> > blocks of code you give are imcc or pasm (instead of C).
Juergen Boemmels wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> writes:
>
> > But suppose that at the end of DoD, the object we're weakly referring
> > to gets marked as alive? Now, we would need to look through that
> > object's list of destroy-f
Juergen Boemmels wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> writes:
>
> > > Normal processors also don't have setline and setfile operations. They
> > > use an extra segment in the *.o file, which is only used by the
> > > debugger. This
Leopold Toetsch wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
>
> > In other words, setline and setfile ops in source don't translate to
> > actual ops in the bytecode, but instead translate to additions/changes
> > to the debugging segment?
&g
I dislike replying to myself, however, it seems I haven't been clear
enough in describing how I think this (c|sh)ould be implemented.
Let's abstract DoD to the following psuedocode:
function markalive(p) {
if(!p.is_alive)
interpreter->dod_queue.enqueue(p);
}
for p in all
Juergen Boemmels wrote:
>
> Leopold Toetsch <[EMAIL PROTECTED]> writes:
>
> > Further:
> > The C and C opcodes are suboptimal, they impose
> > runtime penalty on each run core, so they will go finally. The
> > C and C can map to the functionality used in
> > warnings.c.
>
> Normal processors a
This message was cancelled from within Mozilla.
Juergen Boemmels wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> writes:
>
> > I would like for Parrot to have some way of creating Weak References;
> > I think that this is probably a vital feature.
> >
> > The way I envision this is as follows. The
Juergen Boemmels wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> writes:
>
> > I would like for Parrot to have some way of creating Weak References;
> > I think that this is probably a vital feature.
> >
> > The way I envision this is as follows. The
Michal Wallace wrote:
>
> On Thu, 21 Aug 2003, Benjamin Goldberg wrote:
>
> > I hope you aren't planning on serializing just a single isolated
> > microthread... that wouldn't work well with what I've got in mind due
> > to how much stuff com
Leopold Toetsch wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
>
> >inline op mthread_create(inconst INT) {
> > opcode_t *dest = PTR2OPCODE_T(CUR_OPCODE + $1));
> > PMC * p = new_ret_continuation_pmc(interpreter, dest)
>
> P
Leopold Toetsch wrote:
>
> IMHO is
>
>$a = \$h{"a"};
>print $$a;
>$$a = "xxx\n";
>$a = $h{"a"};
>print $a;
>
> the same as:
>
>new P1, .PerlHash
>set P0, P1["a"]
>print P0
>set P0, "xxx\n"
>set P2, P1["a"]
>print P2
>end
>
> (PMCs have referenc
Juergen Boemmels wrote:
>
> "Vladimir Lipskiy" <[EMAIL PROTECTED]> writes:
>
> [...]
>
> > sub runstep {
> > my $inc = 'include/parrot';
> >
> > my @headers=(
> > sort
> > map { m{\./$inc/(.*)} }
> > glob "./$inc/*.h"
> > );
>
> in a non clean tree the gener
I would like for Parrot to have some way of creating Weak References; I
think that this is probably a vital feature.
The way I envision this is as follows. The following typedef and new
function would be added:
typedef void (*pobject_died_cb)(INTERP, PMC* who_asked,
Pobj* weakref, void *call
Tom Locke wrote:
>
> OK, here's what I'm hoping Parrot can provide for the language I'm building.
>
> My big requirement is for lightweight microthreads (hopefully *very*
> lightweight - I'm considering one scheduler that can handle *millions*
> of threads on a single machine).
Hmm, I can envi
Leopold Toetsch wrote:
>
> Benjamin Goldberg wrote:
>
> >
> > Leopold Toetsch wrote:
> > Not having an INTERP argument severely limits us, even in other ways.
>
> The INTERP argument is fine. The user defined encoding is/was my
> problem.
As in, you
Nicholas Clark wrote:
>
> On Wed, Aug 20, 2003 at 07:19:42PM -0400, Benjamin Goldberg wrote:
>
> > Leopold Toetsch wrote:
>
> > > But these could be converted to utf32 as soon as they are seen.
> >
> > For a long string, that could be quite a bit o
Dave Mitchell wrote:
>
> On Wed, Aug 20, 2003 at 06:40:51PM -0400, Benjamin Goldberg wrote:
> > Dave Mitchell wrote:
> > >
> > > On Sun, Aug 17, 2003 at 05:48:14AM -0600, Luke Palmer wrote:
> > > > Here comes that ever-reincarnating thread again, sorry.
Leopold Toetsch wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
> > Leopold Toetsch wrote:
> >>
> >> Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
> >> > There are a number of shortcomings in the API, which I'd like to
>
Dave Mitchell wrote:
>
> On Sun, Aug 17, 2003 at 05:48:14AM -0600, Luke Palmer wrote:
> > Here comes that ever-reincarnating thread again, sorry.
> >
> > This is a proposal for an efficient solution to the timely destruction
> > problem, which doesn't use refcounting, and fits in to the current
Tim Bunce wrote:
>
> On Tue, Aug 19, 2003 at 12:07:22AM -0400, Benjamin Goldberg wrote:
> > There are a number of shortcomings in the API, which I'd like to
> > address here, and propose improvments for.
>
> Just to be sure people are keeping it in mind, I'll
Leopold Toetsch wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
> > There are a number of shortcomings in the API, which I'd like to
> > address here, and propose improvments for.
>
> > To allow user-defined encodings, and user-defined transcod
Luke Palmer wrote:
>
> Benjamin Goldberg writes:
[snip]
> >9/ New ops which provide access to the string iterator API.
>
> Yes. What is going to be used to store an iterator. An I reg, a P reg?
> If it's a PMC, would it be possible to just implement the iterator
Steve Fink wrote:
>
> In light of the insane amount of work that's gone into Parrot
> recently, I'd say it's about time to cut another release. What else
> would people like to slip in? This is not a freeze announcement yet --
> I want to know what people think of the state of things they're
> wor
There are a number of shortcomings in the API, which I'd like to address
here, and propose improvments for.
Not so much the string_* functions, but rather with how they work (the
encoding API, the transcoding functions).
To allow user-defined encodings, and user-defined transcoding, (written
in p
Michael G Schwern wrote:
[snip stuff, including a mention of refcounting and it's
(dis)advantages]
> So Parrot is going with something else. Don't ask me what it is, I
> don't know.
Parrot will do it like Java -- a mark-and-sweep garbage collector --
with the difference that garbage collection wi
Michal Wallace wrote:
>
> On Sun, 17 Aug 2003, Benjamin Goldberg wrote:
>
> > Michal Wallace wrote:
> >
> > > Uh-oh. I just went to implement "del x"
> > > and there's no op to remove a variable
> > > from a lexical pad! :)
>
Luke Palmer wrote:
>
> Benjamin Goldberg writes:
> > Hmm... I just thought of something. Since 'set' semantics can be
> > easily simulated when we have only ops for 'assign' semantics, maybe
> > imcc itself could do this for us.
> >
> >
Luke Palmer wrote:
>
> Here comes that ever-reincarnating thread again, sorry.
>
> This is a proposal for an efficient solution to the timely destruction
> problem, which doesn't use refcounting, and fits in to the current
> scheme pretty well.
>
> It is based on the fact that 90% of the time (o
Togos wrote:
>
> --- Sean O'Rourke <[EMAIL PROTECTED]> wrote:
> > Luke Palmer <[EMAIL PROTECTED]>
> > writes:
> >
> > > How does one call a parrot Sub from
> > > C and get the
> >
> > I'd vote for stuffing args into the
> > interpreter, calling the sub's invoke()
> > method, then digging through
Michal Wallace wrote:
>
> Uh-oh. I just went to implement "del x"
> and there's no op to remove a variable
> from a lexical pad! :)
Why would you want to remove a variable from a lexical pad?
Surely the "right thing to do" would be to create a new pad (scope),
then add your 'x' variable which
Benjamin Goldberg wrote:
> Brent Dax wrote:
> > TOGoS:
> > # When I say in IMCC:
> > #
> > # $P0 = $P1 + $P2
> > #
> > # , I expect it to create a new value and store it in
> > # $P0, not give me a segfault because I didn't say
> > #
&
In the second chunk of the patch [classes/env.pmc], what is free_it set
to if the else branch is taken? IOW, I think you should have free_it
initialized to 0 when you declare it.
In the last part of the patch [config/gen/platform/win32.c], why do you
set *free_it to 0 even when you return NULL?
Brent Dax wrote:
>
> TOGoS:
> # When I say in IMCC:
> #
> # $P0 = $P1 + $P2
> #
> # , I expect it to create a new value and store it in
> # $P0, not give me a segfault because I didn't say
> #
> # $P0 = new # $P0 is supposed to be based
> # on the types of $P1 and
In pmc_new_noinit, I see a switch() which decides whether or not to do
add_pmc_ext. Why not have that information (whether or not an ext is
needed) defined in each of the .pmc files, and stuck in the vtable?
That would allow other cache-only pmcs to avoid getting an unnecessary
chunk of bytes al
Shouldn't the get_number() method use string_from_num, instead of
calling sprintf/snprintf?
--
$a=24;split//,240513;s/\B/ => /for@@=qw(ac ab bc ba cb ca
);{push(@b,$a),($a-=6)^=1 for 2..$a/6x--$|;print "[EMAIL PROTECTED]
]\n";((6<=($a-=6))?$a+=$_[$a%6]-$a%6:($a=pop @b))&&redo;}
Dan Sugalski wrote:
>
> Well, it turns out that at least some compilers (AIX's) are really
> unhappy about redefined #defines in the C source. This turns out to
> be a problem with things like HAS_STDLIB_H, which is common enough to
> cause collisions. So, we need to go name-prefix all the #defi
Luke Palmer wrote:
>
> Leopold Toetsch writes:
> > Juergen Boemmels <[EMAIL PROTECTED]> wrote:
> > > what still fails is pbc2c.pl (This needs Parrot::Packfile, which can
> > > only read format 0 (old assemble.pl) bytecodes).
> >
> > This is obsoleted by Daniel's exec patches.
>
> Sadly. I mean
Michael G Schwern wrote:
>
> On Mon, Aug 11, 2003 at 01:45:35AM -0700, Ask Bjoern Hansen wrote:
> > We totally need to have Parrot running on this thing when it comes
> > out. :-)
> >
> > http://www.xgamestation.com/
>
> Great idea, shame the hardware is crap. :(
>
> "Third-generation Motorol
What's the difference between VTABLE_set_pmc and VTABLE_clone?
--
$a=24;split//,240513;s/\B/ => /for@@=qw(ac ab bc ba cb ca
);{push(@b,$a),($a-=6)^=1 for 2..$a/6x--$|;print "[EMAIL PROTECTED]
]\n";((6<=($a-=6))?$a+=$_[$a%6]-$a%6:($a=pop @b))&&redo;}
Leopold Toetsch wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
> > Leopold Toetsch wrote:
> >>
> >> Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
> >>
> >> > I would suggest the opnames/categories "mutate," "al
Leopold Toetsch wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
>
> > I would suggest the opnames/categories "mutate," "alias," and
> > "create."
>
> IMHO, we could leave PASM syntax as it is and create opcode aliases
&g
Having read this thread, I think that the real problem is not just that
there are multiple assignment semantics -- it's that the names "set" and
"assign" are not really meaningful -- that is, they *look* to english
speakers as if they are synonyms... their names alone aren't enough info
to know wh
Leopold Toetsch wrote:
>
> I hopefully got the semantics of assign Px,Py right now. The LHS gets
> the value of RHS, eventually morphing itself to the source type.
>
> Anyway:
>
>assign Px, {Iy,Sy,Ny}
>
> are not needed IMHO, these end up as set__native and are identical
> to set Px, {Iy,
Dan Sugalski wrote:
>
> At 11:06 AM +0200 8/8/03, Leopold Toetsch wrote:
[snip]
> >PMC methods
> >---
> >ParrotIO has methods via find_method/invoke. Should that be a general
> >mechanism in default.pmc with one vtable slot for the meth hash?
>
> We're going to want lexially nested method
Brent Dax wrote:
>
> TOGoS:
> # Personally, I would like "=" to mean 'set', and
> # maybe "<-" do 'assign'.
>
> I usually think of registers as variables with fixed names, so the Perl
> 6 part of my brain suggests:
>
> $P0 = $P1 #assign
> $P0 := $P1 #set
Which is wh
Michal Wallace wrote:
> Benjamin Goldberg wrote:
> > Michal Wallace wrote:
[snip]
> > Also... why is $P2 merely an imcc temporary, without a real name?
> > That is, why not do:
> >
> > .pcc_sub _sub1 non_prototyped
> > .local object sub1
> &
Michal Wallace wrote:
[snip]
> def f():
> return g()
[snip]
> # f from line 3
> .pcc_sub _sub1 non_prototyped
> .local object res1# (visitReturn:528)
> find_lex $P2, 'g' # (callingExpression:325)
> newsub $P3, .Continuation, ret0# (callingExpressi
Togos wrote:
>
> > Anyway:
> >
> > assign Px, {Iy,Sy,Ny}
> >
> > are not needed IMHO, these end up as
> > set__native and are identical
> > to set Px, {Iy,Sy,Ny}.
>
> Yes, but as we were discussing in the
> Set vs. Assign thread, it makes more sense
> to call them 'assign', as it morphs the
> e
Juergen Boemmels wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> writes:
[snip]
> > Except that generational_dod_helper is much simpler and faster -- it
> > doesn't mark anything as alive or free, it only adjusts the generation
> > of those pmcs that were c
Having applied a bit more thought, having the generation field as part
of the PMC isn't all that great -- it makes PMCs larger, but it's really
only needed for new/neonate pmcs.
Instead of attatching the generation directly to the pmc, have a global
(per-interpreter) stack of neonate pmcs. Each
Juergen Boemmels wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> writes:
>
> > I was recently reading the following:
> >
> >http://www.parrotcode.org/docs/dev/infant.dev.html
> >
> > It's missing some things. One of which is the (curre
I was recently reading the following:
http://www.parrotcode.org/docs/dev/infant.dev.html
It's missing some things. One of which is the (currently used?) way of
preventing infant mortality: anchor right away, or else turn off DoD
until the new object isn't needed.
This document doesn't mentio
Considering that parrot is now emitting an executable (on some
platforms)... and IIRC, C will be one of the languages we plan to have
parrot support for... will parrot be able to compile itself? :)
--
$a=24;split//,240513;s/\B/ => /for@@=qw(ac ab bc ba cb ca
);{push(@b,$a),($a-=6)^=1 for 2..$a/6
Leopold Toetsch wrote:
>
> Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
>
> > Also, although we're told at the top of string.c to not look at
> > s->bufstart or s->buflen, I'd like to know if we are allowed to
> > assume/assert that for all stri
Luke Palmer wrote:
>
> Benjamin Golberg writes:
> > Actually, these are mostly questions about the string_str_index
> > function.
>
> Uh oh...
>
> > I've some questions about bufstart, strstart, bufused, strlen and
> > encoding->characters?
> >
> > In string_str_index_multibyte, the lastmatch
Since I don't see anything to save/restore the instack on subroutine
calls, I am wondering what happens if a regex has a (?{ CODE }), and
that CODE calls a regex. Are we garunteed that after a regex completes
(either succeeds or fails) that the intstack is in the same state it
started? If not (a
Actually, these are mostly questions about the string_str_index
function.
I've some questions about bufstart, strstart, bufused, strlen and
encoding->characters?
I *think* that ->characters is a fuction which gets passed a pointer to
the start of a buffer, and the number of bytes in the buffer,
Leopold Toetsch wrote:
> OK here it is.
> Again the description for the record:
>
> 1) Initialization:
> - normal core: build op_func_table with all opcode #4 [1]
> - CG core: build ops_addr[] filled with this opcode
> - prederef cores: build a list of (backward) branch instructions
>
Benjamin Goldberg wrote:
[snip]
> If someone's code emits something like:
>
>save $P1
>restore $P2
>
> Then IMCC should be able to optimize that to:
>
>$P = $P1
>$P2 = $P
Actually, that (sometimes) should be able to be changed to:
$P2 = $
Joseph F. Ryan wrote:
> Benjamin Goldberg wrote:
>> Joseph Ryan wrote:
>>> Benjamin Goldberg wrote:
[snip]
>>>> Hmm... If imcc is smart enough, (or perhaps I should say, when the
>>>> flow control is simple/clear enough) it should be able to see when
K Stol wrote:
>
> - Original Message -
> From: "Michal Wallace" <[EMAIL PROTECTED]>
> To: "Luke Palmer" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Thursday, July 24, 2003 12:01 PM
> Subject: Re: approaching python
>
> >
> > On 24 Jul 2003, Luke Palmer wro
K Stol wrote:
>
> - Original Message -
> From: "Michal Wallace" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, July 23, 2003 4:48 PM
> Subject: approaching python
>
> >
> > Hey all,
> >
> > I've been thinking about the "compiling python to
> > parrot" concept. Right now
What kind of semantics do we want for perl6, if we have:
my $fh1 = fdopen( $n );
do {
my $fh2 = fdopen( $n );
};
# is $fh1 valid or not at this point?
For that matter, what about:
for(1..2) {
my $fh = fdopen( $n ); # does this succed the second time?
}
Should thes
Lars Balker Rasmussen wrote:
>
> # New Ticket Created by Lars Balker Rasmussen
> # Please include the string: [perl #23025]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=23025 >
>
> There's no reason to test for the pr
Dan Sugalski wrote:
[snip]
> Here's what we *are* doing.
>
> We are going to do all I/O under the hood asynchronously. Completed
> async IO puts an event in the event queue.
>
> We are going to have a single unified event queue. All IO, timer,
> signal, and UI events go in it. All of 'em. We aren
Josh Wilmes wrote:
>
> At 12:48 on 07/14/2003 +0200, Lars Balker Rasmussen <[EMAIL PROTECTED]> wrote:
>
> > I've taken this very simple approach to the problem. A perl-wrapper
> > for the CC lines in makefiles/root.in
> >
> > .c$(O) :
> > $(PERL) tools/dev/cc_flags.pl $(CC) $(CFLAGS)
Maybe someone should write a script like this:
#!/usr/local/bin/perl -wlpi.bak
s/
(\$?\w+) \s* -> \s* vtable \s* -> \s* (\w+) \s*
\( \s* (interp\w*) \s* , \s* \1 \s*,
/VTABLE_$2($3, $1,/xg;
__END__
[untested]
Then run it on all the code, except that which actually define
With this increase in the number of files, I'm going to ask for
something I've thought of for a while, but not had the guts to ask for.
Could we try and clean up the parrot/ directory? Specifically, I'd like
all of the source code itself moved into a single subdirectory, leaving
at the toplevel
Damien Neil wrote:
[snip]
> Also, given that asynchronous IO is a fairly unpopular programming
> technique these days (non-blocking event-loop IO and blocking
> threaded IO are far more common), I would think long and hard before
> placing support for it as a core design goal of the VM. If there
>
Sean O'Rourke wrote:
>
> On Thu, 17 Jul 2003, Leopold Toetsch wrote:
> > PC = ((op_func_t*) (*PC)) (PC, INTERP); // prederef functions
> >
> > To be able to switch function tables, this then should become:
> >
> > PC = ((op_func_t*) (func_table + *PC)) (PC, INTERP);
> >
> > Thus prederefernc
"Graciliano M . P ." wrote:
>
> # New Ticket Created by Graciliano M. P.
> # Please include the string: [perl #22922]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.html?id=22922 >
>
> There is some plan of how threading will w
Leopold Toetsch wrote:
[snip]
> - When will we check, it there are events in the event queue?
If we check too often (between each two ops), it will slow things down.
If we don't check often enough, the code might manage to avoid checking
for events entirely.
I would suggest that every flow contr
Leopold Toetsch wrote:
> Nick Glencross wrote:
>
> > Having read up in the past on Perl5 internals, it seems to be
> > capable of keeping more than one representation of a Scalar active
> > at a time.
> >
> > Anyone know if there are plans to do this kind of optimisation?
>
> I don't think, this
Leopold Toetsch wrote:
>
> Tupshin Harper wrote:
>
> >
> > I'm not a "GCC person", but I do have an interest in this working. I
> > did some exploratory work (mostly getting familiar with the GCC
> > backend mechanism and with PASM), and quickly ran into what appeared
> > to be fundamental roadbl
Luke Palmer wrote:
>
> I'd like to go about implementing [Perl]?LazyArray and LazySequence
> pmcs, possibly with a TiedArray (and Infinity) in the interim. I have
> a few semantic questions, but first, here's what I have in mind:
>
> LazySequence: Manages individual lazy sequences like 1..I
Leopold Toetsch wrote:
>
> Andy Dougherty <[EMAIL PROTECTED]> wrote:
> > On Thu, 3 Jul 2003, Juergen Boemmels wrote:
>
> >> more errors like this: t/op/interp_1.pasm and t/op/gc_1.t are the ones
> >> I know of. We will have much fun with bugs like this.
>
> > This might be another one -- t/op/
Andy Dougherty wrote:
>
> On Tue, 1 Jul 2003, Leopold Toetsch wrote:
>
> > Andy Dougherty <[EMAIL PROTECTED]> wrote:
> > > On Mon, 30 Jun 2003, Leopold Toetsch wrote:
> >
> > >> Attached is a minimum patch to build imcc as the parrot executable
> >
> > >languages/imcc/*.o
> >
>
Brent Dax wrote:
>
> Benjamin Goldberg:
> # Concievably, we could then examine the exception, and maybe decide
> # that it was nonfatal, and resume execution from just after the place
> # it was thrown from.
>
> The problem with that is that some exceptions are unresu
Dave Whipp wrote:
> Matt Fowles
>> Were this C++ I would say that we could write a single general
>> purpose stack and use template meta-programming to avoid the
>> overhead. Is there a similar solution available in C?
>>
>> My instincts tell me that this solution will be dirty to the tune of
>> m
1 - 100 of 145 matches
Mail list logo
