Aaron Sherman <[EMAIL PROTECTED]> writes:
> On Thu, 2002-04-11 at 00:47, Damian Conway wrote:
>
>> sub load_data ($filename) { load_data($filename, 1) }
>>
>> sub load_data ($filename, $version) {...}
>
> Interesting. This brings goto to mind. Above, I could just assume
> that inlining
> I think you're right that this is a valid distinction, I'm just not
> sure if it's not a little too subtle and that the two different
> notations won't cause confusion.
Well, I had been hoping to appeal to the mathematical mindset of the list,
but there is a second reason for = in addition to /
On Thu, 2002-04-11 at 00:47, Damian Conway wrote:
> sub load_data ($filename) { load_data($filename, 1) }
>
> sub load_data ($filename, $version) {...}
Interesting. This brings goto to mind. Above, I could just assume that
inlining will happen, but what about goto? Obviously:
s
On Wed, Apr 10, 2002 at 10:45:55PM -0600, Luke Palmer wrote:
> Indeed, and with the //= thing, you can let parameters in the middle
> default.
Except that I haven't heard anyone say that given
sub foo ($a//=1, $b//=2, $c//=3) {...}
foo(5,,6); # that
On Thu, 2002-04-11 at 00:42, Luke Palmer wrote:
> > Ah, but I think the mnemonic value of the '.' more than earns its keep
> > here. C is doing a slightly different job
> > anyway. And instance variables are *not* the same as 'normal'
> > variables, they hang off a different symbol table (or syte,
On Thu, 2002-04-11 at 09:36, Jonathan Scott Duff wrote:
> On Wed, Apr 10, 2002 at 10:45:55PM -0600, Luke Palmer wrote:
> > Indeed, and with the //= thing, you can let parameters in the middle
> > default.
>
> Except that I haven't heard anyone say that given
>
> sub foo ($a//=1, $b//=2, $
[Apologies to Aaron Sherman, who gets this twice due to my
dunderheadedness]
Aaron Sherman <[EMAIL PROTECTED]> writes:
[...]
> Also, another though:
>
> sub foo($a = 1, $b, $c) { ... }
>
> In C++ at least, I think this is an error. However, it seems to me that
> in Perl it could be inte
This one too.
--Josh
At 19:10 on 04/11/2002 EDT, Simon Glover <[EMAIL PROTECTED]> wrote:
>
> This patch tidies up a few of the comments in string.c, and fixes one
> actual documentation bug -- namely, string_chopn removes the last
> n _characters_, not the last n _bytes_.
>
> Simon
>
>
Cool, applied.
At 18:21 on 04/11/2002 EDT, Simon Glover <[EMAIL PROTECTED]> wrote:
>
> We no longer pass a PMC pointer into pmc_new, but the comment hasn't been
> changed to reflect that. Patch below corrects, and also adds an
> appropriate comment for pmc_new_sized.
>
> Simon
>
> --- p
On Thursday 11 April 2002 07:03 pm, Michel J Lambert wrote:
> Dan Sugalski wrote:
> > That's because GC_DEBUG is fundamentally broken by design. It's doing
> > things it shouldn't be doing--the system is such that it shouldn't
> > ever trigger GC before the memory allocation system is set up.
> >
im a newcomer, particulalry intrested in the jit part.
is there anyone working on the sparc asm?
/joh
On Thu, 11 Apr 2002, Steve Fink wrote:
> These are my idea of new TODO items. Note that I don't really know
> anything about some of the things I added, so someone should probably
> read this
At 12:02 PM +0100 4/11/02, Simon Cozens wrote:
> > I'm also chipping away at a certain unnamed company to donate an AIX box
>> for official testbed
>
>Another unnamed company offered us one, and nobody collected it in
>time, so it got scrapped. :(
Argh, bummer. On the other hand, a certain unna
At 11:12 PM -0400 4/10/02, Melvin Smith wrote:
>3) Going to fixup the IO system to be more Parrot like, including stringifying
>and making a real PMC out the PIO object.
>Dan I did send you an initial PDD for IO which you
>acknowledged but then
>I think you ate it. Still n
The memory_collected GC statistic does not get updated at present. Patch
below fixes.
Note that a 5000-generation run of life.pasm allocates 32K, and copies
almost 58MB.
--
Peter Gibbs
EmKel Systems
Index: resources.c
===
RCS file:
> > How about the JIT engine then.
>
> JIT runs on bytecode, producing bytecode.
>
> > When does parrot use it?
>
> Before executing bytecode.
>
> > how well does it scale? ( has anyone done some benchmarking )
>
> Don't ask me :P If you haven't already, then you'd
> be best looking at the b
Jonathan E. Paton:
# > How about the JIT engine then.
#
# JIT runs on bytecode, producing bytecode.
No, JIT runs on bytecode, producing equivalent machine code.
# > When does parrot use it?
#
# Before executing bytecode.
#
# > how well does it scale? ( has anyone done some benchmarking )
#
# Don
Melvin Smith:
> I'm getting married Saturday and going on honeymoon for 10 days.
Congratulations! Enjoy.
> I'm also chipping away at a certain unnamed company to donate an AIX box
> for official testbed
Another unnamed company offered us one, and nobody collected it in
time, so it got scrapped.
Hello.
Where in the parrot code does the actual translation from byte code to
binary code occur?
where does it get executed?
Im having a hard time finding things in the code..
/joh
> Where in the parrot code does the actual translation
> from byte code to binary code occur?
Parrot eq. an interpreter, all the byte codes are like
commands to tell it what actions to take... it doesn't
directly take byte codes and turn them into binary code.
Conversion would be compiling, but
How about the JIT engine then.
When does parrot use it?
how well does it scale? ( has anyone done some benchmarking )
On Thu, 11 Apr 2002, [iso-8859-1] Jonathan E. Paton wrote:
> > Where in the parrot code does the actual translation
> > from byte code to binary code occur?
>
> Parrot eq. a
On Thu, 11 Apr 2002, [latin1] Josef Höök wrote:
>
> How about the JIT engine then.
> When does parrot use it?
> how well does it scale? ( has anyone done some benchmarking )
The JIT engine produce machine code for a given bytecode, but there are
only a few opcodes that are coded in assembly so
At 5:13 PM +0200 4/11/02, Peter Gibbs wrote:
>The memory_collected GC statistic does not get updated at present. Patch
>below fixes.
>
>Note that a 5000-generation run of life.pasm allocates 32K, and copies
>almost 58MB.
Applied, as I make the interpreter crash badly in another directory. :)
I'm
The attached patch disables GC at startup. If you turn on GC_DEBUG, you'll
see parrot crash at startup because dod runs and collection runs are being
performed before the interpreter is fully initialized, causing all sorts
of havoc.
This also means that if our default GC allocation values do not
At 5:35 PM -0400 4/11/02, Michel J Lambert wrote:
>There are still plenty of problems with GC_DEBUG turned on, but at least
>it passes all the non-pmc tests now. Has anyone done anything with
>attempting to get a make tinder and tindertest set up?
That's because GC_DEBUG is fundamentally broken b
We no longer pass a PMC pointer into pmc_new, but the comment hasn't been
changed to reflect that. Patch below corrects, and also adds an
appropriate comment for pmc_new_sized.
Simon
--- pmc.c.old Thu Apr 11 18:02:16 2002
+++ pmc.c Thu Apr 11 18:17:30 2002
@@ -16,14 +16,12 @@
#incl
Dan Sugalski wrote:
> That's because GC_DEBUG is fundamentally broken by design. It's doing
> things it shouldn't be doing--the system is such that it shouldn't
> ever trigger GC before the memory allocation system is set up.
>
> If this patch disables the GC only when GC_DEBUG is in place, I'll p
This patch tidies up a few of the comments in string.c, and fixes one
actual documentation bug -- namely, string_chopn removes the last
n _characters_, not the last n _bytes_.
Simon
--- string.c.oldThu Apr 11 19:01:31 2002
+++ string.cThu Apr 11 19:06:47 2002
@@ -87,7 +87,7 @@
> "David" == David Whipp <[EMAIL PROTECTED]> writes:
David> If every object has a C method (C?), then you could
David> always call class-methods as class.m2().
Wouldn't that be .class.m2(), or did I miss something in the flurry?
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc.
> "Dan" == Dan Sugalski <[EMAIL PROTECTED]> writes:
Dan> (Or maybe attributed string eval, like:
Dan> $foo = eval.Parrot sub I0, I0, 5
Dan>EOP
That would make more sense to me (for whatever that's worth) as
$foo = Parrot.eval < http:
>sub foo($a=1, $b, $c=3) { ... }
>
> is ambiguous: While foo(2) sets $a=1, $b=2, $c=3, it's impossible to
> say what foo(4,5) should do.
foo(2) means that $a = 2, $b defaults to undef, $c defaults to 3
foo(4,5) means $a = 4, $b = 5, and $c defaults to 3.
-Miko
Aaron Sherman writes:
: On Thu, 2002-04-11 at 00:42, Luke Palmer wrote:
: > > Ah, but I think the mnemonic value of the '.' more than earns its keep
: > > here. C is doing a slightly different job
: > > anyway. And instance variables are *not* the same as 'normal'
: > > variables, they hang off a
On Thu, 2002-04-11 at 09:59, Ariel Scolnicov wrote:
> [Apologies to Aaron Sherman, who gets this twice due to my
> dunderheadedness]
No problem. I usually reply to the person and CC the list because some
folks have filters that will make discussions easier if I'm replying to
them vs. sending just
On Thu, 2002-04-11 at 11:49, Larry Wall wrote:
> Aaron Sherman writes:
> : This should not be allowed.
>
> Well, that depends on what you mean by "this". :-)
[...]
> : In Perl5 C<$object{instancevar} = 7> is just frowned on. In Perl6, I
> : thought we had agreed that it would flat out be imposs
At 7:25 AM -0700 4/11/02, Randal L. Schwartz wrote:
> > "Dan" == Dan Sugalski <[EMAIL PROTECTED]> writes:
>
>Dan> (Or maybe attributed string eval, like:
>
>Dan> $foo = eval.Parrot set I0, 12
>Dan> sub I0, I0, 5
>Dan> EOP
>
>That would make more sense
On Thu, 2002-04-11 at 11:55, Aaron Sherman wrote:
> 1. The first default marks the beginning of optional parameters.
> 2. An optional parameter with no default will automatically default to
> undef.
Interestingly, I just said something that I did not mean to, but it
opens up an interesting avenu
> class myobj {
> ...
> int a,b,c;
> myobj(int aa, int bb, int cc) :
> a(aa), b(bb), c(cc) const {}
> ...
> };
Ummm no. Straight from Bjarne: "You can't have a const constructor." You
just do what you did w
On Thu, 2002-04-11 at 12:44, Luke Palmer wrote:
> > class myobj {
> > ...
> > int a,b,c;
> > myobj(int aa, int bb, int cc) :
> > a(aa), b(bb), c(cc) const {}
> > ...
> > };
>
> Ummm no. Straight from Bjarne: "You can't ha
Miko O'Sullivan writes:
: > I think you're right that this is a valid distinction, I'm just not
: > sure if it's not a little too subtle and that the two different
: > notations won't cause confusion.
:
: Well, I had been hoping to appeal to the mathematical mindset of the list,
: but there is a
On Thu, 2002-04-11 at 14:34, Larry Wall wrote:
> Miko O'Sullivan writes:
> : Well, I had been hoping to appeal to the mathematical mindset of the list,
> : but there is a second reason for = in addition to / /=: it's simpler to
> : understand. I just think that the potential Perl hackers will un
At 04:03 PM 4/11/2002 -0400, Aaron Sherman wrote:
>On Thu, 2002-04-11 at 14:34, Larry Wall wrote:
> > Miko O'Sullivan writes:
>
> > : Well, I had been hoping to appeal to the mathematical mindset of the
> list,
> > : but there is a second reason for = in addition to / /=: it's simpler to
> > : un
40 matches
Mail list logo
