oar.so
> /data/data/com.termux/files/usr/share/perl6/runtime/dynext
> ./perl6-m tools/build/upgrade-repository.pl
> /data/data/com.termux/files/usr/share/perl6
> ./perl6-m tools/build/upgrade-repository.pl
> /data/data/com.termux/files/usr/share/perl6/vendor
> ./perl6-m tools/build/upgrade-repository.pl
> /data/data/com.termux/files/usr/share/perl6/site
> ./perl6-m tools/build/install-core-dist.pl
> /data/data/com.termux/files/usr/share/perl6
> ^Cmake: *** [Makefile:635: m-install] Interrupt
--
Matt Zand
https://coding-bootcamps.com/
https://myhsts.org/
https://dcwebmakers.com/
Confirmed bug still appears in Rakudo 2017.04 Mac OS X .dmg install.
None of the examples given in the p6doc command help actually work.
Given that a dmg install is the first thing a newbie would try, this is
important to growing the Perl 6 community.
Based on a clean install on a new 2016 MacBo
I'm referring:
http://strangeloop2010.com/talk/presentation_file/14299/GuySteele-parallel.pdf
~Matt
08
Sorry,
Matt Follett
On Sep 24, 2010, at 2:46 PM, perl6 via RT wrote:
> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
> "Two things that seem like bugs",
> a summary of which appears be
o tomorrow's release, they can
> handle it. Otherwise, I'll look at it later in the week.
Ah, OK. Thanks for the explanation.
--
Matt
skips the Subversion-specific
> > tests only when run in a Subversion working copy. The attached patch
> > fixes both problems.
> >
>
> Perhaps because I'm usually working in a Subversion working copy, I
> haven't experienced this error. So I did not test out
On Sun Mar 16 10:57:07 2008, [EMAIL PROTECTED] wrote:
> Matt, chromatic:
>
> This test is still in TODO status as of r26404. Can you provide us with
> an update as to the ticket's status?
>
> Thank you very much.
> kid51
Sure. I investigated the issue a while ba
ld handle all
> > versions of Test::Builder, but I've only tested it with version 0.32.
>
> Patch applied in r26315. I'm using Test::Builder 0.72 and it worked for me.
Thanks for applying it.
--
Matt
On Sun Mar 09 19:32:32 2008, [EMAIL PROTECTED] wrote:
> Matt Kraai's contributions appear to have resolved the problem.
> t/perl/Parrot_Test.t has been passing for me and for reliable
> smoke-testers for the past week. So I am resolving this ticket.
The final test in t/perl/Parro
causing the
> problem you're seeing.
Again, I believe this is what Bob was saying: it's not possible to be
faithful to the original p5 source without creating a separate
subroutine for every loop body. And there are reasons why that's a bad
idea (even if that's what they are in Perl 6):
- It introduces extra overhead in terms of the compiled code
- It's extra work for the compiler – introducing an extra pass for
lexical analysis
The alternative (which Bob is suggesting) is to reintroduce
push_pad/pop_pad so you can create new lexical scopes without using
subroutines for loop bodies.
His suggestion seems reasonable to me. We won't run into this
particular problem with Tcl, but I think most languages will.
--
Matt Diephouse
http://matt.diephouse.com
allocator definitely looks like it's O(n^2). There were some problems
with the older allocator on large subroutines, so it was disabled.
--
Matt Diephouse
http://matt.diephouse.com
On 7/31/07, Nicholas Clark <[EMAIL PROTECTED]> wrote:
> On Mon, Jul 30, 2007 at 09:20:27PM -0700, Matt Diephouse wrote:
> > On 7/30/07, chromatic <[EMAIL PROTECTED]> wrote:
> > > On Monday 30 July 2007 00:21:09 [EMAIL PROTECTED] wrote:
> > > > Author: md
ved it because down later in the source, the strlen of sig *is* checked:
const size_t len = strlen(sig);
if (len > 8) {
real_exception(interp, NULL, 1, "too many arguments in
runops_args");
}
The string is only copied after this check is made.
--
Matt Diephouse
http://matt.diephouse.com
tclint.c:864: failed assertion `my_enum_class_0 != enum_class_default'
> make: *** [runtime/tcllib.pbc] Abort trap
Fixed in r20257.
The pmc2c code was to blame. It looks like the code has been
refactored heavily; but somewhere along the way someone didn't
translate the code accurately. :-/
--
Matt Diephouse
http://matt.diephouse.com
Fixed in r19073.
--
Matt Diephouse
PObj_get_FLAGS(string) |= flags |
PObj_is_string_FLAG | PObj_is_COWable_FLAG | PObj_live_FLAG;
Adding the live flag fixed the problem (r18855).
Good work! This has been the cause of a number of Perl 6 GC errors. I
spent some time trying to track it down before but never made it a
ingify an object using the get_string vtable
function, it gets something other than the string it should have
gotten.
--
Matt Diephouse
http://matt.diephouse.com
talking about overriding vtable functions in a
class?
The latter. It seems like there should be a way to override them
without using eval -- particularly since there's nothing preventing it
technically.
--
Matt Diephouse
http://matt.diephouse.com
that fixes a related bug in Tcl on certain platforms. How does
it fare for you?
I committed this patch to trunk in r18377.
--
Matt Diephouse
http://matt.diephouse.com
Applied in r18355. Thanks!
--
Matt Diephouse
function. Object inherits whatever default isa implementation is
provided. I'm not sure where that code is (it's a little harder to
find), but I'm guessing it just does a string comparison on the PMC
names without testing if the PMC is a class.
--
Matt Diephouse
http://matt.diephouse.com
n a const value because the
> value should be free'd later on.
>
> Also, here's an example PIR file to demonstrate.
Looks good. Applied in r18343. Thanks!
--
Matt Diephouse
without the
closure, I'd think that the lexical environment would have destroyed.
I'm not sure how intentional this is. The PDD isn't clear (to me) about what
:outer means in
the absence of "newclosure". I'd definitely be interested in seeing why this
would be a useful
feature. More detail in the PDD would be nice.
Thanks for the interesting patch.
--
Matt Diephouse
On Mon Apr 23 13:39:40 2007, [EMAIL PROTECTED] wrote:
> Gracias. I attached one more small patch that gets rid of two
> seemingly unnecessary lines in smop_init() - they're easy to miss when
> one's looking at the big picture.
Applied in r18321. Thanks!
--
Matt Diephouse
chromatic <[EMAIL PROTECTED]> wrote:
On Sunday 22 April 2007 17:38, Matt Diephouse wrote:
> The attached patch completely reworks Parrot_process_args. The changes
> are extensive and I think they make the code much clearer. Rather than
> just check it in, I thought I'd try
If there's a leak, memory would climb higher and
higher; if there's not, it should level out.
--
Matt Diephouse
http://matt.diephouse.com
db). There is usually someone around on
irc.perl.org#parrot who could help you debug if you need it.
Best of luck!
--
Matt Diephouse
http://matt.diephouse.com
re to try again? :)
--
Matt Diephouse
http://matt.diephouse.com
ings in and leave further improvements for
another time.
--
Matt Diephouse
http://matt.diephouse.com
arg-handling.patch
Description: Binary data
n config file
+ extended support for gcc, icc, and other compilers
+ extended support for Solaris and other platforms
Thanks to all our contributors for making this possible, and our
sponsors for supporting this project.
Enjoy!
--
Matt Diephouse
documentation are welcome, as always.
Thanks!
--
Matt Diephouse
http://matt.diephouse.com
Speaking of patches, we should also get through as many of these
(accept or reject) as possible.
http://www.parrotcode.org/openpatches.html
Thanks!
--
Matt Diephouse
Andy Dougherty <[EMAIL PROTECTED]> wrote:
Please avoid //-style comments. Older compilers don't understand
them.
Thanks. We have a test for //-style comments, but evidently it doesn't catch
all of our generated code. I've changed it to a C-style comment in r17692.
-
ll variable declarations
have to be at the
beginning of a block, so I had to move one of the lines so that this was the
case. Please watch
for this in the future.
Thanks!
--
Matt Diephouse
es) in
all languages (PIR, C, Perl). It's a fairly long list, but I think we can
get all the issues resolved in the next month.
Let the patching begin!
--
Matt Diephouse
http://matt.diephouse.com
Applied in r17484 with updated tests and a test for the get_namespace() method.
curious.
There's some of both, I think. I recently had to change a test to expect the
long name of a Sub because there was no way to get the short name.
--
Matt Diephouse
http://matt.diephouse.com
Thanks! I couldn't get patch to apply the patch, so I applied it by hand.
Committed in r17411.
missed the obvious solution: just invoking the sub, rather than entering
a new
runloop. This has the benefits of not creating a new runloop and of handling
parameters and
return values properly. It may even make invoke work with :multi (it might need
a bit more
work for that).
Fixed in r1
rrot_run_meth_fromc_args(interp, sub,
pmc, meth, "??", next);
return next;
}
I've tested it and it works with the original code that Richard gave. The
only thing left to do is handle return values; I'm still working on that. If
I can get return values working properly, I'll check in a fix.
--
Matt Diephouse
http://matt.diephouse.com
y thought out -- some of the logic in
Sub.invoke() should be elsewhere.
--
Matt Diephouse
http://matt.diephouse.com
nly one? Does providing an init function for a
subclass of a PMC override both of the parent's init functions?
--
Matt Diephouse
http://matt.diephouse.com
ms. And yes, I would be willing to take a shot at it (realizing that I
may or may not be successful).
AFAICT, we're limited not just by volunteer labor, but also by the boxes
that are available to those volunteers.
--
Matt Diephouse
http://matt.diephouse.com
en a lot of it, so I appreciate the little things. :)
--
Matt Diephouse
http://matt.diephouse.com
. After these fixes, it worked.
Okay, I just changed the occurrences of PMCNULL to NULL. Things should work
now.
Hope this helps you further.
regards,
klaas-jan
It was very helpful, thanks!
--
Matt Diephouse
http://matt.diephouse.com
This was fixed a few minutes ago in r16458. You'll need to re-up and
re-configure. Sorry for
the inconvenience.
--
Matt Diephouse
st returns 0 on success (and -1 on failure). I'd
like to change bind to return the port it's bound to on success. The
patch below adds this code for the unix sockets code. The windows code
looks like it'd be the same, but I can't test it so I'd have to find
someone to
Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
On Fri, Dec 08, 2006 at 05:05:00PM -0500, Matt Diephouse wrote:
> Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> >Does anyone have any suggestions about what sort of PIR
> >code and/or PMCs we need to be able to do make t
$P3 = $P3[4]
morph $P3, .Undef
assign $P3, $P2
If you're only assigning your own PMCs, you can drop the morph (which
isn't technically safe anyway).
--
Matt Diephouse
http://matt.diephouse.com
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Am Dienstag, 5. Dezember 2006 20:39 schrieb Matt Diephouse:
> The portion of the assertion that
> fails is
>
> !(((s)->obj.flags) & b_PObj_on_free_list_FLAG
>
> which means that this string has been garbage collec
s were
PIR-level).
So the underlying problem is that constant strings are getting
collected when they shouldn't. The easy fix is to not collect *any*
constant PObj headers (see patch below). Is this correct? Or is there
a case when they should get collected? If it's th
Fixed in r15971. The MMD code checks that the sub is a Sub PMC so it can get
the signature. I
expanded the check to work with Closure PMCs as well.
Matt Diephouse <[EMAIL PROTECTED]> wrote:
We've basically run into the fact that there's no spec for MMD. I'll
see if I can provide a patch that just makes "_" match native types,
but I think it'll be somewhat more involved than this one.
It ended up being
Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
On Wed, Nov 29, 2006 at 04:43:59PM -0500, Matt Diephouse wrote:
> Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> >Am Mittwoch, 29. November 2006 05:50 schrieb Matt Diephouse:
> >> It also means that "string",
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Am Mittwoch, 29. November 2006 05:50 schrieb Matt Diephouse:
> It also means that "string", "int", and "float" no longer work as MMD
> types -- you can't distinguish between native types and PMCs. I think
d to be updated. Replacing PerlInt with
Integer makes it work:
new P0, .Integer
set P0, 123
new P1, .Integer
set P1, 321
add P1, P1, P0
print P1
print "\n"
end
--
Matt Diephouse
http://matt.diephouse.com
I could argue it either way, but with the
other uses remaining tied to the namespace where they were defined,
let's default to your fix (consistency is good).
I was hoping you'd say that. :-)
Then for exporting (and other dynamic tricks), let's look into a feature
that allows you to change the namespace a compilation unit uses for
default lookups, after it's compiled.
That seems like a good idea.
--
Matt Diephouse
http://matt.diephouse.com
Still, I'm curious to see what reasons there are for not attaching a
namespace to an :anon sub when (1) it seems convenient and (2) all of
Parrot's tests still pass. Does this break anything? Or did this just
signal to you that there may a problem here that needs its own
solution?
--
Matt Diephouse
http://matt.diephouse.com
make transparent references
possible, but they weren't really specced out or desisign
ed properly. As such, they're a little broken and we'd like to remove them.
--
Matt Diephouse
http://matt.diephouse.com
Allison Randal <[EMAIL PROTECTED]> wrote:
Matt Diephouse wrote:
> Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
>> On Thu, Oct 19, 2006 at 10:01:29PM -0400, Matt Diephouse wrote:
>> > This is unspecced. ATM, all classes go into the 'parrot' HLL. This is
Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
On Thu, Oct 19, 2006 at 10:01:29PM -0400, Matt Diephouse wrote:
> This is unspecced. ATM, all classes go into the 'parrot' HLL. This is
> a relic of the past and I think it needs to change. I'm pretty sure
> that HL
to any changes yet as Chip has
been kidnapped by his Real Life (tm).
I think the object model needs a thorough going over in general -- for
the reasons above and because it's an unproven system. I'm not
convinced that it will handle all of Perl 6's needs as is. No serious
OO language has been implemented yet on Parrot; everything up to this
point has been either procedural or functional.
--
Matt Diephouse
http://matt.diephouse.com
n.wikipedia.org/wiki/Partial_ordering
Matt
--
"Computer Science is merely the post-Turing Decline of Formal Systems Theory."
-Stan Kelly-Bootle, The Devil's DP Dictionary
we handle subroutines? That is, why don't we
have a find_method opcode that returns a bound method? That simplifies
parsing for IMCC and makes PIR a little simpler.
obj.'abc'() # call 'abc' method of obj
obj.abc() # same as above
$P0 = find_method obj, ab
Bob Rogers <[EMAIL PROTECTED]> wrote:
From: "Matt Diephouse" <[EMAIL PROTECTED]>
Date: Sat, 23 Sep 2006 20:21:32 -0400
Bob Rogers <[EMAIL PROTECTED]> wrote:
> Try the attached patch . . .
That *does* work. I haven't applied it because it&#
?
That *does* work. I haven't applied it because it's not
necessarily urgent that Tcl work in trunk. I'm okay with
waiting a couple days to see if an actual fix can be found - instead
of merely using a workaround. You can feel free to apply it yourself,
of course.
t the problem
was, but none of my guesses of what's causing it were correct. I hope
I've given you enough information to fix it. If I haven't, let me know
what else I can provide.
Thanks,
--
Matt Diephouse
http://matt.diephouse.com
) You can't use :slurpy, :optional, or :named arguments. Even if
there's support under the hood, there's no way to write a PMC with
these arguments.
--
Matt Diephouse
http://matt.diephouse.com
Joshua Juran <[EMAIL PROTECTED]> wrote:
On Aug 28, 2006, at 12:18 PM, Matt Diephouse wrote:
> I would like to add some sort methods as well: quicksort(),
> mergesort(), etc. But as methods, there is potential for these to end
> up in a user-visible space.
>
> Say for
ted to use these as the basis for
their array classes. Would these each need to be split into 2 classes
as well? If so, we'd want to make multiple inheritance really work
with PMCs.
Any thoughts?
--
Matt Diephouse
http://matt.diephouse.com
g for
Strings (and soon for other types as well).
So if anyone ever finds himself or herself in the same position, a
look at TclList's (languages/tcl/src/pmc/tcllist.pmc) assign_pmc
method would probably be in order.
--
Matt Diephouse
http://matt.diephouse.com
ax in both cases,
and there's probably some wins there.
Except this only works when the user is in the root HLL namespace or
when the user is executing code in the current namespace. That doesn't
mean it's not a valid option; just that it's not always valid.
--
Matt Diephouse
http://matt.diephouse.com
IMO, if it's doable. But it's a little out of
my reach as far as C goes, unfortunately. Otherwise I'd have fixed it
already. :-)
Thanks for taking a look at this.
--
Matt Diephouse
http://matt.diephouse.com
IMHO, this isn't a matter of either-or, but of concurrent development along
2 related tracks:
You're right, it doesn't have to be either-or.
[snip]
It would be good to have (1) ASAP.
There's no reason that people who are interested in (2) have to be
interested in (1) or vice versa.
I agree
I'll be honest, I was willing to put in some effort for something
substantial and original, but I'm not too keen on just remaking or
porting an old solution.
M.T.
ial part of the typed interface?
--
Matt Diephouse
http://matt.diephouse.com
ork with Tcl and let them grow
organically.
Does this sound good? (Chip? Allison?)
--
Matt Diephouse
http://matt.diephouse.com
chromatic <[EMAIL PROTECTED]> wrote:
On Tuesday 18 July 2006 19:43, Matt Diephouse wrote:
> I know I'm a little late to the game here, but in the future it would
> be useful to mention this sort of info in a comment in the source. :-)
> And a comment might be a nice additio
ned being more clear in the svn log, but a comment would
really be the most useful.)
--
Matt Diephouse
http://matt.diephouse.com
Projects/parrot mdiep$
FYI, changing C< $P0 = shift iter > to C< $S0 = shift iter > makes this example
work
corrrectly (of course, you also have to remove C< $S0 = $P0 >).
--
Matt Diephouse
Vishal Soni <[EMAIL PROTECTED]> wrote:
Hi Matt,
This patch is because the number of .constant decls in IMCC is limited
to 4096. This is a todo to make this dynamic. The evil code seems to
have about 4200 .constant decls being generated.
Here is the patch to fix it. For now I bumped
ay technically.
>
> I've suggested that get_namespace follow exactly the same pattern, but
> so far she hasn't commented on that suggestion at all.
I really like both of these suggestions. We also noted on #parrot that
get_hll_global would really simplify things for the Tcl folks, which
currently go through a macro to achieve the same effect.
You mean get_abs_global, actually. The proposed get_hll_global opcode
mirrors the existing find_global exactly. :-)
--
matt diephouse
http://matt.diephouse.com
icates that most of the code belongs in that namespace, so it's
> likely that most of the variables do too. (There are variations, but
> that's at least the common case.)
Works for me. And that is the current meaning of two-parameter find_global,
so it's not a stretch.
Works for me too. I'm not sure that I like the rename (I can't
decide), but the name itself doesn't matter much. The new opcodes (the
presence of get_cur_global) may actually make things easier for Tcl if
we ever compile to 100% inlined PIR.
This is a different route than I was trying to take us, but it should
be almost functionally equivalent, so I'm happy with it.
--
matt diephouse
http://matt.diephouse.com
rst, I think C< [] > *is* a name.
Second, any solution which involves giving the HLL namespace a
different name will have to either (a) add new opcodes, (b) add more
code for all the other cases by making all referencing originate at
the root, or (c) add a special syntax, none of which is simple.
--
matt diephouse
http://matt.diephouse.com
I'd
prefer to have C< .namespace [] > so that we could also have the
matching C< find_global [], 'foo' >. Otherwise find_global becomes a
two step operation for finding globals in the root HLL namespace.
Oh, and I've committed some more failing tests. :-)
--
matt diephouse
http://matt.diephouse.com
)
$S0 = join "::", $P0
print $S0
print "\n"
end
.end
mini:~/Projects/parrot mdiep$ parrot test.pir
parrot
mini:~/Projects/parrot mdiep$
--
matt diephouse
http://matt.diephouse.com
able to get a namespace at runtime... which translates to the easiest
way for Tcl to use namespaces.
--
matt diephouse
http://matt.diephouse.com
Chip Salzenberg <[EMAIL PROTECTED]> wrote:
On Wed, Jun 28, 2006 at 11:40:28PM -0700, Matt Diephouse wrote:
> The get_namespace opcode gets namespaces from the root namespace.
> Should it get namespaces from the HLL namespace instead? The PDD isn't
> explicit either way [.
x27;t add find_global variants
that lookup globals in HLL's? Right now we have find_global_p_p_s.
Adding find_global_p_s_p_s would let me reach into Tcl's private very
easily instead of having to crawl the namespaces myself.
$P0 = find_global '_tcl', ['Foo'; 'Bar'], "baz"
Thanks,
--
matt diephouse
http://matt.diephouse.com
via RT Matt Diephouse <[EMAIL PROTECTED]> wrote:
# New Ticket Created by Matt Diephouse
# Please include the string: [perl #39597]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39597 >
The following code in line
;;depth]
unless_null lexpad, got_lexpad
# try again
inc depth
goto get_lexpad
got_lexpad:
variable = lexpad[variable_name]
.return(variable)
.end
Of course, that doesn't mean that I wouldn't like an opcode to do it for me. :-)
--
matt diephouse
http://matt.diephouse.com
A simple, if naive fix could be to make the logo a phonetic
representation (or whatever it's called). Just a simple
pseudo-solution.
M.T.
I really like these. I think you're on to something. I'm definitely in
favor of Momi Wiki, or just Momi.
Maybe we can even be very corny and call it 'Aloha Wiki'... Hmm.
Yes, Bikini Wiki sounds sexy. I like how they both 'lie' in the
pacific ocean... as opposed to being worn... ;)
M.T.
I'll be honest and say that I'm not too concerned with the
prize/grant, so that may be the reason I want to go beyond that
minimal ideal. I'm specifically concerned with a poorly designed (or
at least slightly clumsy to upgrade) wiki, all in for the sake of
speed, minimal functionality, and money.
1) Understood. I've been disconnected from Perl for a while, and this
is really the first time I've been participating in the Perl
community. Thanks for the heads-up. :)
2) I agree that it is both important and pertinent to get the general
requirements down for the project, but I do see a need an
[Sorry Michael, I didn't mean to send it you twice. :) ]
I like the RFC idea. I will read up on them and see, if it is a
particular format, how to simplify it. But, most definitely, the
community must have dialog about the requests. For each request
really.
On the architecture note, I've written
Honestly, I'm not familiar with the Perl way of doing things, but I'm
open to learn especially because I see the Perl community going
through a (much-needed) reform. Thusly, I'm not familiar with the RFCs
(Request For Change?) but I do see the merit for something similar.
However, as far as the j
I was just reading the AES referenced above and I can say now that I'm
really happy about some changes to Regexes, and that a grammar may
well be what we're looking for. However, even with this great tool, we
still have to handle the implementation. Though I can see the benefit
of using the gramma
I would recommend using a templating system as opposed to having calls
to include files in numerous pages. Even though it's minimal, it's
still duplication, and it can get rather messy.
I know that some people don't know about or don't like it, but I would
recommend setting things up in a Model-V
Juerd,
My mistake: I misunderstood what you were saying (probably due to haste).
But really, then, there are alternatives to using tables, such as
DIVs, as well as simply modifying the parsing step to also parse for
this special case in addition to Textile or what-have-you.
I guess if I said an
1 - 100 of 558 matches
Mail list logo
