> Can anyone point me at examples of pod6 in use?… Concise would be nice,
One concise example I've found useful is the Pod::Load script,
https://modules.raku.org/dist/Pod::Load:cpan:JMERELO/lib/Pod/Load.pm6
This short script shows pod6 used both as a more full-featured
documentation format (the
> $ raku --version
> This is Rakudo version 2020.07 built on MoarVM version 2020.07
> implementing Raku 6.d.
> Whats is new??
Release notes are at
https://github.com/rakudo/rakudo/blob/master/docs/announce/2020.07.md
I'm most excited for new the Unicode operators, ≡ and ≢ (though the
permutatio
tion of the docs is so different. I've been trying to
contribute to the docs more in the past few weeks, so maybe I can play a small
part in making that situation better for us all.
Best,
Daniel
> Here is my keeper on a hash
Thanks for sharing :)
I like Bruce's Regex-based approach.
Here's how I'd probably approach the problem:
raku -e 'say [+] @*ARGS.grep(+*)' 0 100 200 300 apples 400oranges 2kilos
18.7876 500 grams14 10stars10 sun100moon 77
August 31, 2020 2:28 PM, "Bruce Gray" wrote:
> my $is_a_number = / ^ \d+ [ '.' \d* ]? $ /;
>
On Tue, Oct 10, 2000 at 08:23:07PM +0100, Nicholas Clark wrote:
> Having had cause to root around in the archives of perl6 and perl5 lists,
> can I suggest that we use the system that perl5-porters is archived on in
> preference to the system that the perl6 lists use (MHonArc, apparently).
> Perso
On Wed, Dec 06, 2000 at 08:31:07AM -0700, Nathan Torkington wrote:
> Simon Cozens writes:
> > Why does string C have to screw everything up?
>
> It doesn't. String eval is the escape hatch from a language that
> can't do what you want it to do. As such it's okay for it to be
> slow--consider it
On Wed, Dec 27, 2000 at 04:08:00PM -0500, Uri Guttman wrote:
> i can see things changing very easily. but to me, how perl handles
> overflow is a language semantic as much as implementation. in 5 it is
> well defined (ilya not withstanding) and you are talking bigint stuff
> which scares me. i don
It also coredumps on Solaris 7, when running the test2.pbc - test.pbc is
fine. The coredump doesn't show much, only that it keeled over at
interpreter.c line 16, which is the while() loop.
Once upon a time Philip Kendall shaped the electrons to say...
>
>
> Hi.
>
> I've just tried getting Pa
parses code
looking for identifiers. You can find that here:
<http://www.brockman.se/software/hyphen-ruby/>
Finally, I realize that this is a religious issue, I hope
that I have not stepped on anybody's toes, and I humbly ask
that you approach this discussion with an open mind.
Kind regards,
--
Daniel Brockman <[EMAIL PROTECTED]>
n, but the problem will not arise
unless people start mixing these two styles --- something
which is very obviously not a good idea.
Besides, another couple of hundred lines down, you might
(but you probably won't) find the following code:
eval ("foo", "bar").join(&q
usly: just override the Perl 6
> grammar's identifier rule. All the edge cases will be resolved by the
> longest token principle, so `foo-bar-baz` will be an identifier.
Yes, it's very comforting to know that even if Perl 6 won't
have this feature built in, it will be so amazingly easy to
implement in a beautifully clean way.
But what about class Foo::Bar-2.10-cpan:BRENTDAX?
--
Daniel Brockman <[EMAIL PROTECTED]>
t about this. I would be happy if the
standard distribution came with a package that enabled the
hyphenated identifiers syntax in the lexical block:
use hyphenated_identifiers;
Hopefully the name of that package won't actually have
any underscores in it.
--
Daniel Brockman <[EMAIL PROTECTED]>
s.
Having used that style for a while, I don't see any good
reason to write them smashed together.
> trying to change that in a scoped way will only cause pain
> somewhere else.
If so, then that is a symptom of a wider problem. I mean,
wasn't Perl 6 supposed to make this kind of hack a breeze?
--
Daniel Brockman <[EMAIL PROTECTED]>
> No sane person would put their braces in different places in
> different parts of their code, so why don't we just say,
> "from now on, you must use brace style X"?
Have you never seen code that's been worked on by several people with
differing tastes in brace positioning and no coding standard?
rscores should probably warn about $i+1 and $i*1.
I would still use that package, and your example doesn't
bother me personally. I would never write $i-1 or $i+1.
But I wouldn't want to be the one to have to reply to all
the complaints about the unintuitive meaning of
@bar, or throwing an
exception if the new element is not a Pair?
(What is Perl's pair terminology, by the way?)
--
Daniel Brockman <[EMAIL PROTECTED]>
> If .indexes turns out to be used a lot, then let's have .i -- "i" for
> "index" is accepted abbreviation, isn't it? (Think for (i = 0; ...;
> ...))
+1 here. I too find ^$n a bit bizarre, but I like the look of
for @foo.i
OTOH, I like the parallels between %foo.keys and @foo.keys -- it recalls
t
> As a third possibility, could we huffman-code "do nothing" clauses by
> leaving out the appropriate argument? That is:
>
> while $x-- && some_condition($x);
That's a bit too short for my liking: it is likely to lead to the
traditional C undetectable bug when you write
while $x-- && some_cond
> +use Sense :EXPORT<@horse>; # import "common" but exports
> # "@horse"
As typos seem to be in favour today, might I suggest s/exports/export/
so all the verbs agree in number? Apologies for the short context but I
had enough of a fight with the wrapp
> Values with these types autoboxes to their uppercase counterparts when
Sorry to be picky after your quick response, but
s/autoboxes/autobox/;
--
Mary had a little sprout,From week to week, from month to month,
Its fleece was green as grass, She kept the sprout in tow,
She
> +If this MMD dispatch succeeds, the result becomes the result of the
> +of the reduce.
"MMD dispatch" ~~ "RAS syndrome"
Also note the two "of the"s.
> +Otherwise, if the MMD dispatch fails, then if there is one argument,
> +while the single argument form can MMD dispatch based on the type of
D
> +insert a line break into a sequence of methods calls include:
s/methods/method/
> A consequence of the postfix rule is that (except when delimiting a
...
> +a quote or terminating a "long dot") a dot with whitespace in front
Too many a's.
> +you to insert optional whitespace and commentsbetwe
> I *still* don't understand the problem this long dot is trying to
> solve.
I'm a bit with you, there. I can see why you might want to do
$query
.fetchrow($i)
.selectcolumn($j)
.say;
rather than
$query.
fetchrow($i).
selectcolumn($j).
say;
but surely
$query.
.fetchrow($i).
.selectcolumn($j).
> +but rather easier to read. The bare C<*>, C<+> and C quantifiers
> +never backtrack in a C unless some outer rule has specified a
> +C<:panic> option that applies. If you want to prevent even that, use
> +C<*:>, C<+:> or C to prevent any backtracking into the quantifier.
> +If you want to expl
> return a boolean for either 1 or 0 arguments. Negated operators,
> -return Bool::False, and all the rest return Bool::True.
> +return C, and all the rest return C.
The comma on the first line is superfluous.
--
I will take my life into my hands And I will use it.'MacArthur Park'
I will w
> qX ::= "q:x:y:z";
>
> as a simple, argumentless "word" macro.
But would that DWIM when I come to write
qX(stuff, specifically not an adverb argument);
?
--
"The rules of programming are transitory; only Tao is eternal.
Therefore you must contemplate Tao before you receive en
> >Including :skip(//). Yes, agreed, it's a huge
> >improvement. I'd be more comfortable if the default rule to use for
> >skipping was named instead of . (On IRC was also
> >proposed, but the connection between :skip and is more
> >immediately obvious.)
> Yes, I like too. I too keep mistakel
> (string) context. You can force list context on the expression using
> -either the C<*> or C operator if necessary.
> +either the C operator if necessary.
English not being executable line noise, you can't use "either" to force
a scalar into list context.
--
"Twelve? Who needs twelve? Couldn'
Wrt your second problem, if this
> $arg_for = [ ( 0 .. $arg_for ) »*« $arg_for ];
is not rw so is not actually adding the entry to the hash (btw,
shouldn't the >>*<< be >>* as the right-hand operand is a scalar?), then
it is possible that
> > > And then I get an error telling me 'No such method in
> what problems Perl 5 has that Perl 6 fixes
A type system to die for.
I think that is enough of a win on its own that mentioning any of the
other features will only muddy the issue :->
--
"The fact that some geniuses were laughed at does not imply that all who
are laughed at are geniuses. The
> (would that be a "pliki"? a "sixwiki"? a "plixi"? erm-)
psiki, where the "p" is silent. Like what you throw when you fancy a
free day off work.
--
Humpty Dumpty sat on the wall, Humpty Dumpty had a great fall,
All the King's horses and all the King's men | http://surreal.istic.org/
> How does an atomic block differ from one in which all variables are
> implicitly hypotheticalized?
I assume that the atomicness being controlled by some kind of lock on
entry, it also applies to I/O and other side-effecty things that you
can't undo.
--
Hats are no worse for being made by ancien
> +an function-arguments (C) context on its arguments.
You might have fixed the other error while you were at it. s/an/a/
--
"My invention can be exploited for a certain time as a scientific
curiosity, but apart from that it has no commercial value whatsoever."
Auguste Lumiere, on his a
> Ask Bj�rn Hansen <[EMAIL PROTECTED]> writes:
> > Woah, we are getting really far away from talking about perl6
> > here...
>
> Kind of a usenet law or corollary? "Every discussion about wikis ends
You're being a bit optimistic there, aren't you? The only way you'd end
a my-wiki-is-better-than-y
I only vaguely recall the discussions a while back about what
smart-matching against Booleans should do. IIRC, there are two
positions, and a good argument for either side:
C<$foo ~~ True> means C; C<$foo ~~ False> means C
or
C<$foo ~~ True> means C; C<$foo ~~ False> means C
The first of these ad
Can someone explain to me how } on a line on its own can end a statement
(as described in the second section of S04), but the following still
works?
if $condition
{
...
}
else
{
...
}
i.e. Why doesn't the } on the fourth line terminate the if statement,
leaving the compiler terminally confuse
> Also realize that it is not necessarily the duty of Textile (et al) to
> handle that aspect beyond text formatting. A diff or history-revision
> view goes beyond the context of the tool.
I don't think Juerd was talking about tables for the purposes of showing
version diffs, but so you can give p
> > -post-assigment forms such as C is allowed.)
> > +post-assigment forms such as C are allowed.
> s/allowed\./allowed)./
Umm, no. The ) was correct in its original position (after the full
stop). It just seems to have disappeared.
--
Always crash crash crashWell come on and
I've just thought of an interesting interaction with lvalue functions
and call by foo. What if I want to write, say, an lvalue ?? !! function
thus
sub cond(Bool $c, $a, $b) is rw {
if $c return $a else return $b;
}
Will this fail because $a and $b are not rw? If so, will it fail at run-
or comp
Would it be useful to have a way of 'binding' a variable name to a given
type, in a given lexical scope, such that every time a variable with
that name is declared in that scope it gets to be of that type? What I'm
thinking of is a bit like how in Fortran variables called n are
automatically intege
> Multimethods are not just overloading as in C++.
To expand upon this point a little, you can use multimethods to do
pattern-matching in the style of ML and similar languages. So, to pinch
an example from the pugs tree (examples/functional/fp.p6)
multi sub length () returns Int { 0
> +This hides any qX rule that might be defined in the gramma. Note
s/gramma/grammar/ if you please. I prefer the new quoting behaviour and
I like << and >> as word boundaries. (Sometimes I miss Vim regexes' \<
and \>.) Are << and >> zero-width?
--
"The rules of programming are transitory;
> > +This hides any qX rule that might be defined in the gramma. Note
> s/gramma/grammar/ if you please.
Erm, credit TreyHarris on this one, as he seems to have spotted it
first on #perl6.
--
"Of all things, good sense is the most fairly distributed: everyone
thinks he is so well supplie
Sorry to patch the patch, but in
> -Other sigils binds only to the I argument with that name:
> +Other sigil binds only to the I argument with that name:
the replacement makes no more sense than the original. "Other sigils
bind" or "Any other sigil binds" would work here.
Also, I believe the origi
> Oh, thank you very much for correcting this. I didn't even read the
> sentence after I made the change. ;-) I should be more careful the
> next time.
Bah, you don't need to with an army of attentive proof-readers.
> I'm sorry that I disagree with this one since I am following Audrey's
> changes
> Is it possible to say this one expression? Haskell's syntax is shiny
> but everybody wants the colon:
>
> foo( ( $x :: Moose ) );
I may be in a little world of my own here, but isn't this what 'as' is
supposed to do?
foo($x as Moose);
--
"Of all things, good sense is the most fairly
> "Stuart Cook" schreef:
> > Larry Wall:
>
> >> if 0 {
> >> ...
> >> }
> >
> > The one disadvantage of that approach is that it will break if the
> > "commented-out" code temporarily fails to compile.
>
> How frequent does that happen?
All the time. I often comment out bits of code wh
> : my $a = q:t /END/
> : test
> : END;
> :print qq:to/END/;
> :Give $amount to the man behind curtain number $curtain.
> :END
> : Which is correct?
> Both of them are. See the table further down that says:
What about the semicolon? After the terminator, or after the openin
> If "changing that functionality beyond recognition" means changing its
> external behavior (as opposed to its internal behavior) so that it
> acts differently from what the superclass had promised to do, then
> no, it's not any weirder--but I can't figure out how the contract
> would work, eith
> See diagram case 2 (Class A and Class B intersect):
> & B are built from a role that represents their intersection ( Class
> A U Class B), and then code is added in the definitions of the
It may be just me being confused, but the symbol that looks like a U
(U+222a) is usually union; intersect
> +Note that only the first term of an C operator may reasonably be
> +an infinite list.
Now all we need is a variant that does the diagonal order and we'll be
home and dry.
'a'..* diagX 1..*
->
['a', 1],
['a', 2],
['b', 1],
['a', 3],
['b', 2],
['c', 1],
['a', 4],
['b', 3],
['c', 2],
['d', 1],
> svn log, speaking on larry's behalf (>):
> > +The string concatenating form is:
> > +
> > + X~X <1 2> # 'a1', 'a2', 'b1', 'b2'
> > +
> > +The C operator desugars to something like:
> > +
> > +[~]�( X <1 2> ) # 'a1', 'a2', 'b1', 'b2'
^
> If the C variant
> What am I doing wrong?
Sounds like you need to define (or at least declare) the new operator
before you use it. Perl 6, like Perl 5 compiles with a single pass, so
when you are using your random operator, it hasn't yet read the
declaration further down the file.
It does its best to DTRT with mos
> names they're given. "The Beatles" probably sounded like a really
> dumb name for a band once.
But maybe less dumb than 'The Quarrymen', which was the original name of
the band. (They all went to Quarry Bank school, now Calderstones.)
Perhaps the renaming, unfettered by their history or by a
I liked it. Just one nit, near the end:
>You can also preconfigure L, by
>naming them with a pair of angles as a suffix. For example:
>
> =comment Always allow E<> codes in any (implicit or explicit) V<>
> code... =config V<> :allow
>
> =comment All code to be italiciized...
> +This is particularly useful for establishing grammatical categories
> +in a grammar be declaring a C C or C. (Perl 6's
> +grammar does this, for instance.)
Unless you be a pirate, you may want to revise the above, and add
commas.
--
Paraphernalia/Never hides your broken bones,/ And I don't k
What about this?
given @foo {
for $_ -> $x { ... }
when .empty { ... }
}
You can reverse the order if you want:
given @foo {
when .empty { ... }
for $_ -> $x { ... }
}
I don't like C<$_>, but I can't think of a way to get rid of it.
--
D
What happens if a resumable exception is propagated through a block with
a LEAVE, KEEP, or UNDO block? S04 seems to be a bit vague on this point.
It strikes me that what we want it to do is not execute them when the
exception is propagated, because we don't know whether it's going to be
resumed or
On Mon, Mar 05, 2007 at 09:01:13AM -0800, Larry Wall wrote:
> I don't see a problem here. I think you maybe missed the bit that says:
>
> A C block sees the lexical scope in which it was defined, but
> its caller is the dynamic location that threw the exception. That is,
> the stack
On Sun, Mar 11, 2007 at 02:17:25PM -0700, [EMAIL PROTECTED] wrote:
> Author: audreyt
> Date: Sun Mar 11 14:17:24 2007
> New Revision: 14335
> Modified: doc/trunk/design/syn/S06.pod
> ==
> --- doc/trunk/design/syn/S06.pod
On 26 May 2002, Mike Lambert wrote:
> # New Ticket Created by Mike Lambert
> # Please include the string: [netlabs #626]
> # in the subject line of all future correspondence about this issue.
> # http://bugs6.perl.org/rt2/Ticket/Display.html?id=626 >
>
>
> Looksd like the logic for keeping trac
Now I attached all the files :)
I also added now the target disassemble, it will emit on stdout the
disassemble of a pbc, this output is (should be) ready to assemble.
(it might have some issues with strings).
Daniel Grunblatt.
On 27 May 2002, Daniel Grunblatt wrote:
> # New Ticket Crea
On Wed, 29 May 2002, Mike Lambert wrote:
> Hey all,
>
> After finding out that life.pasm only does maybe 1KB per collection, and
> Sean reminding me that there's more to GC than life, I decided to create
> some pasm files testing specific behaviors.
>
> Attached is what I've been using to test a
On 27 May 2002, Peter Gibbs wrote:
> # New Ticket Created by "Peter Gibbs"
> # Please include the string: [netlabs #628]
> # in the subject line of all future correspondence about this issue.
> # http://bugs6.perl.org/rt2/Ticket/Display.html?id=628 >
>
>
> Following patch adds dependencies ent
yed ops simply to set,
> as Jeff suggested, as well as documenting them (slightly). It also
> adjusts the tests accordingly. All tests still pass.
>
> Simon
Applied, thanks.
(with a perl -p -i -e 's/[gs]et_keyed/set/' *.t first)
Daniel Grunblatt.
On 1 Jun 2002, Simon Glover wrote:
> # New Ticket Created by Simon Glover
> # Please include the string: [netlabs #650]
> # in the subject line of all future correspondence about this issue.
> # http://bugs6.perl.org/rt2/Ticket/Display.html?id=650 >
>
>
>
> A few small fixes to the assembler
On 29 May 2002, Mike Lambert wrote:
> # New Ticket Created by Mike Lambert
> # Please include the string: [netlabs #634]
> # in the subject line of all future correspondence about this issue.
> # http://bugs6.perl.org/rt2/Ticket/Display.html?id=634 >
>
>
> Peter recently submitted a patch to RT
er files.
When I first saw all those warnings I couldn't understand why, thank you.
Daniel Grunblatt.
That was me, going to fix, sorry.
Daniel Grunblatt.
On Fri, 7 Jun 2002, Sebastian Bergmann wrote:
> jit.c(73) : error C2039: 'has_jit_op' : Ist kein Element von
> 'Parrot_jit_optimiz
> er_section'
> ./include\parrot/jit.h(50) : Siehe Deklaration von
&g
> --- start of forwarded message ---
> Date: 7 Jun 2002 21:36:26 -
> From: Joe Yates (via RT) <[EMAIL PROTECTED]>
> Cc: recipient list not shown: ;
> Subject: Re: [netlabs #590] Ticket Resolved
> Message-Id:
>
> Dear Daniel,
>
> I hope I'm no
On Wed, 12 Jun 2002, Jason Gloudon wrote:
>
> Could someone apply this ?
>
> - Forwarded message from Jason Gloudon <[EMAIL PROTECTED]> -
>
> Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
> Precedence: bulk
> Delivered-To: mailing list [EMAIL PROTECTED]
> Date: Mon, 10 Jun 2002 1
Can you let me know if the way I think about exceptions is ok?
Thanks,
Daniel Grunblatt.
set I0,0
set I8,10
try
# User exception
catch !WRONG_NUMBERS, PRINT_WRONG
# Trying to catch an exception that was already catched.
catch !NOT_SUCH_FILE, NEVER_MADE_IT
print
On Fri, 21 Jun 2002, Jerome Vouillon wrote:
> On Thu, Jun 20, 2002 at 12:26:11AM -0400, Melvin Smith wrote:
> > Given that it seems capturing and restoring a context is the most
> > expensive part, should we make default routines lightweight (execute
> > on caller stack rather than getting their
It would be cute if you change the debugger to load all the included files
as well.
Daniel Grunblatt.
On 21 Jun 2002, brian wheeler wrote:
> I've implemented a .include directive for the new assembler. It
> basically changes the preprocessor to shift through the source file, an
Err, Jeff just told me to see the -E flag.
Daniel Grunblatt.
On Sat, 22 Jun 2002, Daniel Grunblatt wrote:
> It would be cute if you change the debugger to load all the included files
> as well.
>
> Daniel Grunblatt.
>
>
> On 21 Jun 2002, brian wheeler wrote:
>
> &g
t don't
hardcode the address of the interpreter anywhere, and either way you will
need to dereference it, and that's slower, leaves us with 1 less cpu
register for the register allocation and requires a total redesing(what is
of course the less important thing).
Daniel Grunblatt.
I just changed 'kc' to be an integer constant, because it was the
simpliest way to make the warnings go away.
If kc should be a string and k too, tell me.
Daniel Grunblatt.
The assembler doesn't use the XS stuff anymore, just committed a patch
build from Jeff's code.
Let's hope to see some more tinderboxes green.
Daniel Grunblatt.
UE, but it does nothing.
well done microsoft...but it doesn't sound like a big deal. so calling the function
should be just fine.
-daniel
Index: io/io_win32.c
===
RCS file: /cvs/public/parrot/io/io_win32.c,v
retrieving revisi
On Wed, 17 Jul 2002, Andy Dougherty wrote:
> The following patch brings the MANIFEST file up-to-date with recent
> additions. I haven't committed this in case some other reorganization
> (e.g. moving stuff to a src/ or dev/ or doc/ directory) is underway.
>
> There are also a few minor shuffles
We have one vote for docs/dev.
Daniel Grunblatt.
On Wed, 17 Jul 2002, Melvin Smith wrote:
> At 06:14 PM 7/16/2002 -0700, John Porter wrote:
>
> >Melvin Smith wrote:
> > > I put it temporarily in the root dir, which I know is wrong.
> > > Where should .dev files
Applied.
Daniel Grunblatt.
On Wed, 17 Jul 2002, Sean O'Rourke wrote:
> # New Ticket Created by "Sean O'Rourke"
> # Please include the string: [perl #15009]
> # in the subject line of all future correspondence about this issue.
> # http://bugs6.perl.org/
Applied, thanks.
Daniel Grunblatt.
On Mon, 22 Jul 2002, Aldo Calpini wrote:
> # New Ticket Created by Aldo Calpini
> # Please include the string: [perl #15335]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.h
Applied, thanks.
Daniel Grunblatt.
On Tue, 23 Jul 2002, Andy Dougherty wrote:
> # New Ticket Created by Andy Dougherty
> # Please include the string: [perl #15401]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt2/Ticket/Display.h
On Mon, 29 Jul 2002, Nicholas Clark wrote:
> Here's a very minimal ARM jit framework. It does work (at least as far as
> passing all 10 t/op/basic.t subtests, and running mops.pbc)
Cool, I have also been playing with ARM but your approach is in better
shape. (I'll send you a copy of what I got h
I thing I forgot to tell is that I also have added a constant pool which
could be usefull for the ARM too, it's on my local tree,I don't know
exactly when I'm going to finish it.
Daniel Grunblatt.
hese, is there a common instruction set?
>
> * IA64 - reports of the IA64 instruction set tell that it combines
> the "elegance" of the IA32 CISCy instruction set with
> the "elegance" of the HPPA RISCy instruction set... :-)
>
> I intend to do nothing on these except raise gui^H^H^Hawareness :-)
Or give me an acount? ;)
Daniel Grunblatt.
Yes, we can do that, we can also try to go in and out from the computed
goto core if available.
Daniel Grunblatt.
On Tue, 30 Jul 2002, Dan Sugalski wrote:
> At 10:34 PM -0300 7/29/02, Daniel Grunblatt wrote:
> >On Mon, 29 Jul 2002, Nicholas Clark wrote:
> > > As you can
alks/
>
> FYI The conference went well and I'm sure Dan will get his slides up
> soon. BTW anyone want to work on getting Parrot to use less memory so
> it can run on palmtops? ;-)
>
I'm told it will take much more than just reducing the memory it uses.
Da
mops.c is only slightly faster the jit, i.e. 1%
> - perl6-jit, albeit still totally unoptimized, doesn't compare too bad
>to perl5
> - mops is a silly test ;-)
>
You didn't use -O3 while compiling mops.c, did you?
Daniel Grunblatt.
ting:
> because I need if_i_ic JITted but mops only needs backwards jumps (which are
> easy, and don't require me to write the fixup routine yet)
We can wait, no problem.
Daniel Grunblatt.
On Tue, 30 Jul 2002, Nicholas Clark wrote:
> On Tue, Jul 30, 2002 at 01:21:30PM -0400, Dan Sugalski wrote:
> > At 10:34 PM -0300 7/29/02, Daniel Grunblatt wrote:
> > >On Mon, 29 Jul 2002, Nicholas Clark wrote:
> > > > As you can see from the patch all it does is i
ut of work electrons, I think that
> it might be best to wait and see what we (*) learn from JITs on other
> platforms, then use that to design a third generation JIT that is capable of
> mapping parrot registers onto hardware CPU registers.
>
> * Er, "we" is probably just Dani
OK, now we have the JIT working on PPC.
More opcodes coming.
It's not currently using a constant pool but it should.
Thanks to Sean for the sync cache code and helping me.
Daniel Grunblatt.
ouring?)
> If so, imcc has already done some work about where slightly more JIT effort
> might pay off, so it seems a shame to throw that out.
Yes, that's why we are not going to do any kind of optimization that is
not required to be done at runtime, that means, we expect the most optimal
bytecode.
Daniel Grunblatt.
xes failing to assemble anything.
Probably I should have gone the other way and fix it.
Daniel Grunblatt.
e assembler I'd call a prototype. The regex engine? The
> GC? ...
>
The assembler is a bit outdated, it shouldn't be too difficult to bring it
up to date, I just don't have enough time latetly. But it did work fine
and is easy to extend it. Why do you think it should be thrown away?
Daniel Grunblatt.
On 12 Aug 2002, Simon Cozens wrote:
> [EMAIL PROTECTED] (Daniel Grunblatt) writes:
> > I moved it back to pure-Perl because there were something like half of the
> > tinderboxes failing to assemble anything.
>
> Ah, right. Yeah, the tinderboxes are good slaves but really ba
On 12 Aug 2002, Simon Cozens wrote:
> [EMAIL PROTECTED] (Daniel Grunblatt) writes:
> > The assembler is a bit outdated, it shouldn't be too difficult to bring it
> > up to date, I just don't have enough time latetly. But it did work fine
> > and is easy to extend
1 - 100 of 1122 matches
Mail list logo
