Benjamin Goldberg <[EMAIL PROTECTED]> writes:
> There's no way, in this program, for $x to be out of scope while $y is
> in scope.
But we're in Perl6(66)-land, where "delete caller.MY{'$x'}" and
"delete %OUTER::x" (sp?) can wreak havoc on your pad from all
sorts of strange places. It ain't moral,
> Doesn't compile. Its seems to be the #ifdef vs #if issue.
Seems. I've fixed it. Try to compile the patch one more time,
please.
prefixing.diff
Description: Binary data
On Mon, 18 Aug 2003, Benjamin Goldberg wrote:
> > Hmm. Do you mean
> >
> > if for stmt in block:
> > if stmt.type == undef:
> > flag_as_going_to_delet(stmt.varname)
> >
> > So I can create a new pad when it's assigned?
>
> Right. You'd create a new pad just before the "for", and
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! :)
> >
> > Why would you want to remove a variable from a lexical pad?
> >
On Sun, 17 Aug 2003, 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.
> >
> > That is, by default,
> >$P0 = $P1 +
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! :)
>
> Why would you want to remove a variable from a lexical pad?
>
> Surely the "right thing to do" would be to
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.
> >
> > That is, by default,
> >$P0 = $P1 + $P2
> > will be tran
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
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.
>
> That is, by default,
>$P0 = $P1 + $P2
> will be translated by imcc into
>add $P0, $P1
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
> > #
> > # $P0 = new > # $P0 is supposed to be based
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> Andy Bussey <[EMAIL PROTECTED]> wrote:
>> Here's a revised patch to add the IMCC tests
>> to 'make test' and 'make fulltest' - this time
>> patched against root.in.
>
> Thanks, applied.
t/syn/file.t relies on . being in path (in the 3 system("imcc...")
Not sure if this has been flagged up here or not yet, but it looks
interesting:
http://nickle.org/implement/html
" For non-local jumps caused by break, continue and return statements, Nickle
automatically builds a continuation if necessary to ensure that intervening
twixt blocks are executed
Michal Wallace <[EMAIL PROTECTED]> wrote:
> I haven't looked into this at ALL, but I was
> curious about the IMCC optimization flags:
Its barely tested and in an early stage. Anyway -O2c works.
> Sincerely,
>
> Michal J Wallace
leo
Luke Palmer <[EMAIL PROTECTED]> writes:
> FWIW, here's my personal imcc syntax highlighting file for vim. I've
> found it very useful in reading imc code (but then, I'm very attached
> to my syntax highlighting).
Auto-generated editor configuration? Cool...
> I'm still not sure how to add new
Kenneth A Graves (via RT) <[EMAIL PROTECTED]> writes:
> Should the word "argv" be explicitly mentioned, or is "command line
> arguments" clear enough?
Thanks, applied (w/ mention of argv).
/s
I haven't looked into this at ALL, but I was
curious about the IMCC optimization flags:
[~/pirate]: ./pirate.py -d weightless.py > weightless.imc
[~/pirate]: parrot weightless.imc
ended with: L 450
total time: 23
[~/pirate]: parrot -O=1 weightless.imc
ended with: L 450
total time: 22
[~/
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> Dan Sugalski <[EMAIL PROTECTED]> wrote:
>> And semantic differences--don't forget those.
>
> A keyed "add" vtable doesn't help to provide more semantics. The set vs
> assign thread applies here too. On the contrary: to provide all
> semantics you would
Hi,
A little while back I said I'd start making regular binary builds of Parrot
for those on Win32 who don't want to or can't compile Parrot for whatever
reason. I've finally found the time to sort this out, and my first attempt
is available.
You can download it at:-
http://www.jwcs.net/develop
FWIW, here's my personal imcc syntax highlighting file for vim. I've
found it very useful in reading imc code (but then, I'm very attached
to my syntax highlighting).
I'm still not sure how to add new files with cvs diff, so I used a
normal diff against /dev/null.
Enjoy,
Luke
--- /dev/null 1
Hi!
I'm using a current MS compiler (Version 13.10.3077) and ActiveState Perl
5.8.0 (Build 806) to compile parrot. The compiler warns about
c1 : warning C4349: /Gf is deprecated and will not be supported in future
versions of Visual C++; remove /Gf or use /GF instead
which is specified by Activ
Dan Sugalski wrote:
No. It isn't, and JITting doesn't have anything to do with this. The
issue is expressable semantics, and in languages with active data (which
encompasses a number of the languages we're interested in, icluding
perl, python, and ruby) not allowing direct access to members of a
# New Ticket Created by Kenneth A Graves
# Please include the string: [perl #23346]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=23346 >
I was trying to figure out how to access argv from within parrot code,
and didn't se
Vladimir Lipskiy <[EMAIL PROTECTED]> wrote:
> This patches touches 22 files and deals with
> -DHAVE_COMPUTED_GOTO
> -DHAS_JIT
> -DGC_IS_MALLOC
Doesn't compile. Its seems to be the #ifdef vs #if issue.
leo
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 (or more), all objects
needing timely
Michal Wallace <[EMAIL PROTECTED]> wrote:
> I expected getprop to behave like find_lex
> and throw an exception if the property doesn't
> exist, but it doesn't:
C returns a PerlUndef on failure, which isn't what I would
expect (compared to C) either.
leo
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 6:06 PM +0200 8/16/03, Leopold Toetsch wrote:
>>How long does it take to compile core_ops_cg.c with 60 times the opcode,
>>we now have?
> We'll only have double the number of ops (since we did decide, ages
> ago, that if one PMC in an all-PMC operation
Andrew savige wrote in perl.qa :
> Running variants of:
>
> tar tzf perl-5.8.0.tar.gz | perl -lne'print if tr|-_./a-zA-Z0-9||c'
>
> suggests only [-_./a-zA-Z0-9] are valid characters in a path name.
>
> Then I noticed 'perldoc perlport' lists the portable filename
> characters as defined by ANSI
29 matches
Mail list logo
