Opcodes normally have a specifier that indicates, if a register is
written to or only used, e.g.
null (out PMC)
An C register gets a new value at that point, the register
allocator can reuse this register because the old contents got
discarded. This information is necessary for the register
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> So, I'm doing these, because I need 'em, and we might as well get the
> things in now. For the record, these things will be called as
> functions (not methods), with three parameters, so the signature
> looks like:
A short question WRT implementation: shou
[EMAIL PROTECTED] (Joe Gottman) writes:
> This function would be very useful in inner loops, so if it is possible to
> implement it more efficiently in the core than as a sub in a module I think
> we should do so.
And, if it's possible to implement it more efficiently in the core than as a
sub in
Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> wrote:
> Dan Sugalski wrote:
>> This becomes a bit less efficient when we're looking at intermediate
>> values of expressions. Something like:
>>
>>a = b + c + d
>>
>> turns to
>>
>>new $P0, SomeIntermediateType
>>add $P0, b, c
>>add a, $
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> This becomes a bit less efficient when we're looking at intermediate
> values of expressions. Something like:
> a = b + c + d
> turns to
> new $P0, SomeIntermediateType
> add $P0, b, c
> add a, $P0, d
> and we need to create that $P0 te
On Fri, Mar 19, 2004 at 03:53:05PM +, [EMAIL PROTECTED] wrote:
> Is there a way to nest usage of Test::Harness? I have an application
> with a number of custom modules. I want to structure my test suite this
> way:
>
> myapp.t
>module_a.t
>module_b.t
>
> modul
- Original Message -
From: "Luke Palmer" <[EMAIL PROTECTED]>
> Juerd writes:
> > Has this C already been decided?
>
> Doesn't matter, because most of these decisions are up for discussion.
> I think everything that was "decided" when Apocalypse 3 was written has
> changed at least three
Dan Sugalski wrote:
If that works better, great. The hack fix apparently didn't, at least
according to the tinder builds.
Had a massive think-o about the meaning of --define. The version now in
CVS should work. (Tested it on my own box--had to add make, gcc, and
perl to Cygwin, but it builds n
Dan Sugalski wrote:
This becomes a bit less efficient when we're looking at intermediate
values of expressions. Something like:
a = b + c + d
turns to
new $P0, SomeIntermediateType
add $P0, b, c
add a, $P0, d
Well...how about this:
1. Have all vtable methods which take a dest retur
This has come up before and the discussion always semi-warnocks, but
it's time to bring it up again.
All the vtable operations that do PMC things are three-arg
versions--they get both the args and the destination PMCs passed in.
This is done specifically for speed reasons, as the assumption is
At 9:19 PM +0100 3/26/04, Leopold Toetsch wrote:
Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> wrote:
Done. (Done hackishly, but done.)
A bit too hackish IMHO. The Configure --define switch can take multiple
arguments, separated by commas.
A hint equivalent could be:
Configure::Data->set {
On Fri, 2004-03-26 at 15:20, Luke Palmer wrote:
> When writing Perl 5, I always find myself writing @{ more often than @$.
> Maybe it's just a bad habit that I don't tend to use a lot of
> intermediate variables.
Well, one of the big problems with Perl 5's dereferencing is that it's
painful to cr
Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> wrote:
> Done. (Done hackishly, but done.)
A bit too hackish IMHO. The Configure --define switch can take multiple
arguments, separated by commas.
A hint equivalent could be:
Configure::Data->set {
D_inet_aton => 1
D_xxx => 1
}
Will Coleda <[EMAIL PROTECTED]> wrote:
> #3 0x001a8c6c in Parrot_Continuation_mark (interpreter=0x923400,
> pmc=0x984588) at continuation.c:53
Seems to be dead context.
Does this help?
--- parrot/classes/continuation.pmc Mon Mar 22 13:38:09 2004
+++ parrot-leo/classes/continuation.pmc Fri
Larry Wall writes:
> On Fri, Mar 26, 2004 at 09:41:23AM -0700, Luke Palmer wrote:
> : Is @{$foo} going away? More specifically, how do I write that map if
> : $baz is some more complex expression, and I don't want to use * (say I
> : want to adhere if map decides to change its signature to take a
On Fri, Mar 26, 2004 at 09:41:23AM -0700, Luke Palmer wrote:
: Okay, good. So this is correct:
:
: my $baz = @foo;
: @bar = map { ... } @$baz;
:
: (to be equivalent of mapping over @foo)?
Yes, that's correct.
: Is @{$foo} going away? More specifically, how do I write that map if
: $ba
Another job for the intrepid configure and/or makefile hacker.
Right now, there's a languages-test target in the top level makefile.
This is good.
Unfortunately, the way it works is... sub-good. What it does is do a
"make test" in the languages directory, and that target runs each
language tes
I finally applied the long missing bits of a patch by Gordon Henriksen -
thanks again.
So the macros C and C are already history.
PObj_bufstart(b) and PObj_buflen(b) is now the way to go.
leo
Dan Sugalski wrote:
At 7:26 PM +0100 3/26/04, Leopold Toetsch wrote:
--define=inet_aton Quick hack to use inet_aton instead of inet_pton
Sounds like a job for a hints file. :)
Done. (Done hackishly, but done.)
--
Brent "Dax" Royal-Gordon <[EMAIL PROTECTED]>
Perl and Parrot hacker
Oceania has
At 7:26 PM +0100 3/26/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
The cygwin build sorta kinda works OK, but the link fails because of
a missing _inet_pton. I seem to remember this cropping up in the past
and I thought we'd gotten it fixed, but apparently not.
Kind of fix
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> The cygwin build sorta kinda works OK, but the link fails because of
> a missing _inet_pton. I seem to remember this cropping up in the past
> and I thought we'd gotten it fixed, but apparently not.
Kind of fixed:
$ perl Configure.pl --help
...
--defi
I finally figured out why the windows machine wasn't showing in the
tinderbox, and fixed that. (System dates. D'oh!) We now have (again)
a reliable windows machine building parrot for test, both under
Cygwin and Visual Studio/.NET (though it builds a native executable
there rather than a .NET o
Leopold Toetsch wrote:
>Steve Hay <[EMAIL PROTECTED]> wrote:
>
>
>>HANDLE __stdcall WSAAsyncGetServByName(HWND hWnd, u_int wMsg,
>>const char * name,
>>const char * proto,
>>
Nick Kostirya <[EMAIL PROTECTED]> wrote:
> I have built Parrot on NetBSD with GNU Portable Threads.
> All (except SKIP) threads.t tests is successful,
> BUT "interp identity" and "thread - kill".
> Test "interp identity" sleep perpetual after printing ok1 and ok2.
Strange. Actually no PASM thread
Juerd writes:
> Larry Wall skribis 2004-03-25 12:33 (-0800):
> > On Thu, Mar 25, 2004 at 11:35:46AM -0800, Brent 'Dax' Royal-Gordon wrote:
> > : Larry Wall wrote:
> > : > say @bar.elems;# prints 1
> > : C? Not C?
> > It's just a "println" spelled Huffmanly.
>
> Can't we instead just hav
At 4:34 PM +0100 3/26/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
At 6:46 PM +0100 3/17/04, Leopold Toetsch wrote:
Or: after the 1st delegate lookup create a JITed stub
Which is swell, except for that pesky can't-guarantee-a-JIT thing... :)
I've running that now for the C
Larry Wall skribis 2004-03-25 12:33 (-0800):
> On Thu, Mar 25, 2004 at 11:35:46AM -0800, Brent 'Dax' Royal-Gordon wrote:
> : Larry Wall wrote:
> : > say @bar.elems; # prints 1
> : C? Not C?
> It's just a "println" spelled Huffmanly.
What happened to the principle that things that work
Steve Hay <[EMAIL PROTECTED]> wrote:
> HANDLE __stdcall WSAAsyncGetServByName(HWND hWnd, u_int wMsg,
> const char * name,
> const char * proto,
> char * buf, int obj.u._b._buf
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 6:46 PM +0100 3/17/04, Leopold Toetsch wrote:
>>Or: after the 1st delegate lookup create a JITed stub
> Which is swell, except for that pesky can't-guarantee-a-JIT thing... :)
I've running that now for the C<__init> call. In the absence of
C<__init> t
I have built Parrot on NetBSD with GNU Portable Threads.
All (except SKIP) threads.t tests is successful,
BUT "interp identity" and "thread - kill".
Test "interp identity" sleep perpetual after printing ok1 and ok2.
Test "thread - kill" running perpetual using 100% CPU.
Than I can help?
Nick.
Larry Wall writes:
> : Also, how does the use of *$foo differ from @$foo here? Is the later
> : going away? (I'd think that horrible, for the same reason as above: C
> : is confusing because it's not always clear what you get when you *.)
>
> No, @$foo is not going away. You can write it that
On 2004-03-26 at 08:16:07, Larry Wall wrote:
> And "say" isn't in there because of APL or PHP. It's actually inspired
> by something worse in Ruby.
Presumably by "something worse" you mean "puts"? Not a great name, to
be sure, but it does have a venerable tradition behind it. :)
I do like ha
On Fri, Mar 26, 2004 at 09:23:25AM -0500, Dan Sugalski wrote:
: At 11:01 PM -0500 3/25/04, Will Coleda wrote:
: >Would a patch be accepted that let split work on non empty strings
: >(not treated as REs) as a stopgap until RE support?
:
: Yep.
Especially since we'll be revising P6 split to do th
On Fri, Mar 26, 2004 at 09:26:45AM -0500, Dan Sugalski wrote:
: Yup. Subroutines and methods are privilege boundaries, and code with
: extra rights may call into less privileged code safely. We need to
: work out the mechanism though.
One thing you'll have to do in that case is disable the abili
On Fri, Mar 26, 2004 at 08:59:36AM +0100, James Mastros wrote:
: Larry Wall wrote:
: >Yes, * was originally a no-op in list context, but I think now we can
: >use it to deref a list that would otherwise not interpolate itself.
: >It maps better onto how a C programmer thinks, and if in scalar
: >co
At 10:12 AM + 3/26/04, Harry Jackson wrote:
Dan Sugalski wrote:
I've fixed up the dependency problem in the makefile generation
that was getting in the way of multithreaded makes. Shouldn't cause
any problems, but it never hurts to double-check these things
elsewhere.
Was that were "make -jN
At 2:57 PM +0100 3/26/04, James Mastros wrote:
Larry Wall wrote:
Do bear in mind that Perl can execute bits of code as it's compiling,
so if a bit of code is untrustworthy, you shouldn't be compiling it
in the first place, unless you've prescanned it to reject C,
C, and other macro definitions, or
At 11:01 PM -0500 3/25/04, Will Coleda wrote:
Would a patch be accepted that let split work on non empty strings
(not treated as REs) as a stopgap until RE support?
Yep.
--
Dan
--"it's like this"---
Dan Sug
Larry Wall wrote:
Do bear in mind that Perl can execute bits of code as it's compiling,
so if a bit of code is untrustworthy, you shouldn't be compiling it
in the first place, unless you've prescanned it to reject C,
C, and other macro definitions, or (more usefully) have hooks
in the compiler to c
Ah, good call.
Adding -G causes the code to complete with no crash. (This also clears
the two hurdles in the test suite I mentioned elsewhere.)
(debugger) - I'm not sure I can get anything more helpful out of the
debugger than the crash log (with stack trace) from an earlier post -
Here's the
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> > Causes a crash, instead of raising an exception.
>
> as probably any other IO opcode. Proper error handling for IO is much
> work and a lot of fun.
>
> Patches welcome.
These were things I wanted to do quite a while ago, but then I got a
new job,
Dan Sugalski wrote:
I've fixed up the dependency problem in the makefile generation that was
getting in the way of multithreaded makes. Shouldn't cause any problems,
but it never hurts to double-check these things elsewhere.
Was that were "make -jN" was failing. I tried to get this running for
a
Will Coleda <[EMAIL PROTECTED]> wrote:
> This rather dodgy bit of code
> .sub main
>$S0 = read $P1, 1
>end
> .end
> Causes a crash, instead of raising an exception.
as probably any other IO opcode. Proper error handling for IO is much
work and a lot of fun.
Patches welcome.
leo
Will Coleda <[EMAIL PROTECTED]> wrote:
> I'm still seeing both bugs, with a cvs update, make realclean; perl
> Configure.pl, make. (if I do a cvs diff in my repo, the only changed
> files are tcl related.)
> What other intel do you need to help duplicate the bugs?
Try with -G to turn off DOD/GC.
Larry Wall wrote:
Yes, * was originally a no-op in list context, but I think now we can
use it to deref a list that would otherwise not interpolate itself.
It maps better onto how a C programmer thinks, and if in scalar
context it also happens to defer the signature checking to use the
interpolated
45 matches
Mail list logo
