Leopold Toetsch:
# And finally: Parrot will (again[2]) track HLL source line info like:
#
##line 17 "sourcefile.p6"
Why create a new directive syntax when we already have one?
.line 17 "sourcefile.p6"
--Brent Dax <[EMAIL PROTECTED]>
Perl and Parrot hacker
"Yeah, and my underwear i
Benjamin Goldberg <[EMAIL PROTECTED]> writes:
> I like the ideas of a range of characters, and of variable amount of
> information. So, how about multiple setline variants?
>
>setline Ix # all code from here to the next set{line,file} op is line
> x
>setline Ix, Iy # set line,col number fr
According to Benjamin Goldberg:
> > >#line 17 "sourcefile.p6"
>
> I don't like this syntax -- it sounds too easy for someone to write a
> comment like:
> #When this was in the original foobar language, it was on
> #line 17
Do you worry about Perl too? Because Perl already has this.
Funny
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
Benjamin Goldberg writes:
> Juergen Boemmels wrote:
> > Benjamin Goldberg <[EMAIL PROTECTED]> writes:
> >
> > > The pobject_weakref function first checks if the 'weakref' argument
> > > has been marked as alive -- if so, nothing happens. Then, it adds the
> > > Pobj* to a lookup table, pointing f
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 following typedef and new
> > function would
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 following typedef and new
> > function would
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 comes along when you serialize a continuation --
> > you
On Thu, Aug 21, 2003 at 06:37:52PM -0400, Benjamin Goldberg wrote:
>
>
> Nicholas Clark wrote:
> > Particularly when the regexp engine is written assuming O(1) random
> > access.
>
> It doesn't *need* to assume O(1) random access; after all, it's never
> accessing *randomly*, it's always access
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)
>
> Please note that the ret_continuation is inten
Vladimir Lipskiy <[EMAIL PROTECTED]> wrote:
> s/$inc/^$inc/;
Thanks.
leo
[EMAIL PROTECTED] writes:
> Nicholas Clark <[EMAIL PROTECTED]> writes:
>
> > I think that it has practical uses for other, dimensionally inferior
> > languages. It would often be nice to know which bit of this line:
> >
> > } elsif ($host =~ /([^.]+\.[^.]{3}$)/ || $host =~
> /([^.]{4,}\.[^.]{2}
I sent something similar to this about 6 hours
ago but it never showed up so I think it
got spam filtered or something. <:-/
Anyway, just to clear things up, here
is my take on 'set' and 'assign':
set: replace the reference in the
destination register
assign: don't change the reference in the
On Thursday 21 August 2003 21:40, Brent Dax wrote:
> # we're already running with a faster opcode dispatch
Man I wish I had the time to keep up with parrot development. Though, as
others have pointed out, the core archetecture is somewhat solidified by this
point, I thought I'd put in my tw
On Friday, August 22, 2003, at 02:52 , Leopold Toetsch wrote:
Gordon Henriksen wrote:
(PMCs have reference semantics[1])
Isn't that the job of Perl's \ operator?
Did you read on to [1] too?
I read
[1]
new P1, .PerlHash
new P3, .PerlString
set P3, "yyy\n"
set P1["a"], P3
set P0, P1["a"]
Nicholas Clark <[EMAIL PROTECTED]> writes:
> On Fri, Aug 22, 2003 at 02:30:13PM +0200, Juergen Boemmels wrote:
>
> > a format for the line-info bytecode segement. The only question is
> > reinvent the wheel, or use an already established format (stabs or
> > DWARF).
>
> can they do the things be
I just peeped in headers.pl and alighted on that you had forgotten
to put ^ in front of $inc according to Benjamin's advice(if you had
meant that advice, of course) .
s/$inc/^$inc/;
On Fri, Aug 22, 2003 at 02:30:13PM +0200, Juergen Boemmels wrote:
> a format for the line-info bytecode segement. The only question is
> reinvent the wheel, or use an already establiched format (stabs or
> DWARF).
can they do the things below?
> It might be nice to have column information to. Th
On 08/21/03 Tom Locke wrote:
> Note that I have *absolutely* no opinion on this (I lack the knowledge).
> It's just that with Perl, Python, Ruby, the JVM and the CLR all stack based,
> Parrot seems out on a limb. That's fine by me -- innovation is not about
> following the crowd, but I feel it does
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 also don't have setline and setfile operations.
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 following typedef and new
> function would be added:
>
> typedef void (*pobject_d
The debug segment (generated with -w or -d commandline options) has
source file name and line number information.
When now parrot is run with the slow core and warnings are enabled, the
location of the warnings is printed.
$ parrot -bw h.pasm #[1]
Use of uninitialized value in string context at
Graciliano M . P . <[EMAIL PROTECTED]> wrote:
> ... I already
> sent a bug report about this problem for Parrot 0.0.10, and nothing
> yet!
And I did answer:
Post error message(s).
leo
S. entry on Dan's blog: Registers vs stacks for interpreter design. It's on
this page:
http://www.sidhe.org/~dan/blog/archives/2003_05.html
klaas-jan
- Original Message -
From: "Brent Dax" <[EMAIL PROTECTED]>
To: "'Tom Locke'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, Augu
> ITYM:
>
> > my @headers=(
> > sort
> > map { m{^$inc/(.*\.h)\z} }
> > keys %{maniread()}
> > );
>
> Otherwise, someone might at some future date, write:
>
>langauges/mylang/include/parrot/oops.txt
>
> And that would get picked up ;)
Or he might even
Gordon Henriksen wrote:
(PMCs have reference semantics[1])
Isn't that the job of Perl's \ operator?
Did you read on to [1] too?
leo
Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
>> (PMCs have reference semantics[1])
I should have started with [1]:
new P1, .PerlHash
# new P3, .PerlString
# set P3, "yyy\n"
# set P1["a"], P3
set P0, P1["a"]
print P0
set P0, "xxx\n"
set P2, P1["a"]
print P2
end
When the hash e
Benjamin Goldberg <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch wrote:
>> I have problems imaginating such kind of STRINGs.
> You lack sufficient imagination -- Larry's suggested that Perl6 strings
> may consist of a list of chunks. I can easily imagine each of those
> "chunks" being full-fledged
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)
Please note that the ret_continuation is intended for returning only, not
for executing
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 comes along when you serialize a continuation -- you'd
> get almost the whole interpreter ser
On Thu, 21 Aug 2003, Tom Locke wrote:
(not sure who you're quoting here... dan I think)
> > > But Parrot has continuations. Doesn't this gives me (cooperative)
> > > microthreads? (with a little work on my part).
> >
> > Sure...
>
> So these would be real cheap right? Time and space overheads si
On Thursday, August 21, 2003, at 11:50 , 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 reference semantics[1])
# New Ticket Created by Graciliano M. P.
# Please include the string: [perl #23552]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=23552 >
Hy,
Sorry for the !!!, but when we will be able to compile IMCC on Win32?
I think
34 matches
Mail list logo
