I've just delivered v2 of "Parrot: Evolution" at OSCON '06. This
presentation is a bit different in content but looks a lot more, well,
plain. Not that there's anything wrong with that.
I suggested to the people present that they might visit
http://use.perl.org/~chip/journal/30455
where I l
# New Ticket Created by Kay-Uwe Huell
# Please include the string: [perl #39987]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39987 >
Hi parrot-team,
there were a few words highlighted wrong in vim, like .endm, .endnames
# New Ticket Created by Jerry Gay
# Please include the string: [perl #39992]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39992 >
r13601 added a test to check parsing of every parrot opcode. but those
that accept pmc cons
Am Donnerstag, 27. Juli 2006 20:27 schrieb chromatic:
> When embedding or extending Parrot through the external API, most of the
> strings go into and come out of Parrot as the type Parrot_STRING. This is
> painful and somewhat tedious from C (where these are usually -- but not
> always -- C strin
Am Donnerstag, 27. Juli 2006 19:44 schrieb Matt Diephouse:
> .sub __get_string :method
> $P0 = new .Exception
> throw $P0
> .end
>
> Running this gives:
>
> caught
> No exception to pop.
PIR code running on behalf of a vtable (or MMD) function is implemented by
entering a se
On 7/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Author: audreyt
Date: Thu Jul 27 10:44:22 2006
New Revision: 10492
Modified:
doc/trunk/design/syn/S04.pod
Log:
* S04: More nits from agentzh++.
(However, the period-inside-parens style, as seen in
this sentence, is not changed.)
# New Ticket Created by chromatic
# Please include the string: [perl #39990]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39990 >
When embedding or extending Parrot through the external API, most of the
strings go into a
Author: audreyt
Date: Thu Jul 27 10:44:22 2006
New Revision: 10492
Modified:
doc/trunk/design/syn/S04.pod
Log:
* S04: More nits from agentzh++.
(However, the period-inside-parens style, as seen in
this sentence, is not changed.)
Modified: doc/trunk/design/syn/S04.pod
# New Ticket Created by Matt Diephouse
# Please include the string: [perl #39988]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39988 >
The example:
.sub main :main
$P0 = get_hll_global ['Foo'], 'load'
$P0()
# New Ticket Created by chromatic
# Please include the string: [perl #39986]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39986 >
Hi there,
When creating a new interpreter with Parrot_new(), it should be possible to
com
Author: audreyt
Date: Thu Jul 27 10:38:08 2006
New Revision: 10490
Modified:
doc/trunk/design/syn/S02.pod
doc/trunk/design/syn/S06.pod
Log:
* S02, S06: gaal++ suggested s/sending a feed into/feeding into/.
Modified: doc/trunk/design/syn/S02.pod
=
I've eventually reinstalled my AMD X2 box. It's now running x86_64-linux.
r13597 enables compiling 32 bit executables (with JIT - yay!) on this arch.
$ perl Configure.pl --m=32
does almost all that is needed. See F for more.
leo
Audrey, I know the feeling of processing a "large" patch. :=)
As Larry said, there're always nits. :(
Here're even more fixes for S04:
Index: D:/projects/Perl6-Syn/S04.pod
===
--- D:/projects/Perl6-Syn/S04.pod (revision 10
Bill Coffman wrote:
> There is no platform independent way to produce "NaN" or "Inf", so IMHO,
> you
> did it the only way it can be done.
>
> That being said, you can optimize by looking at the bits. Wikipedia
> explains IEEE-754 http://en.wikipedia.org/wiki/IEEE_754
Many thanks for your though
14 matches
Mail list logo
