Two quick questions, what hackish things in pir are you refering to,
and how much more do you think it would take to get bytecode working?
Also, consider that file size alone is not the best indicator of how
well something is programmed, as sometimes a bigger object file is
faster than a
hi,
I noticed that some tests in languages/PIR are failing. I did not touch
the project for some time, and last time I worked on it, everything was
just fine.
Below some of the output I get. My guess it has something to do with the
test framework (wasn't that being refactored?)
Also, tests
Hi,
Joshua Isom wrote:
Two quick questions, what hackish things in pir are you refering to,
and how much more do you think it would take to get bytecode working?
First of all, my words might have been to harsh. It is certainly not my
goal to step any toes and criticize IMCC. So my apologies if
# New Ticket Created by Jonathan Worthington
# Please include the string: [perl #41956]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=41956
In a discussion with Allison, it was agreed that PMETHOD and PMINVOKE
Void functions can't try to return anything. I haven't checked if this
patch is right or not. The documentation for Parrot_set_attrib_by_num()
claims it returns a PMC *, but the source code uses 'void' and doesn't
actually return anything. I don't know what the intended behavior
actually
On Wed, Mar 21, 2007 at 11:04:29PM -0400, Jesse Vincent wrote:
I'm pleased to announce the inaugural Perl 6 Microgrants program.
Best Practical Solutions (my company) has donated USD5,000 to The
Perl Foundation to help support Perl 6 Development. Leon Brocard,
representing The Perl
After applying the various build patches I posted earlier today, I tried
running make test. Unforutnately, it appears to hang in
t/examples/shootout_1.pir. It ran for about 15 hours before I finally
killed it. Curiously, it hadn't racked up much CPU time at all -- ps
showed '0:00'. A perl
On Fri Mar 09 09:27:22 2007, [EMAIL PROTECTED] wrote:
I noticed that if you cloned an iterator that you had already
shifted, the clone started at the beginning, rather than at the
original's current location.
Applied in r17691 with one change: C89 specifies that all variable declarations
have
On Thursday 22 March 2007 01:48, [EMAIL PROTECTED] wrote:
+#INVERSE_CONDITIONED_LINE(win32):$config{ALL_PARROT_LIBS} =
@libparrot_ldflags@ $config{C_LIBS}; $config{ABS_PARROTDIR} =
Cwd::realpath(
File::Spec-rel2abs( $config{PARROTDIR} )
); $config{LDDLFLAGS}
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.
--
Matt Diephouse
On Thu, 22 Mar 2007 08:59:05 -0400 (EDT), Andy Dougherty
[EMAIL PROTECTED] wrote:
Please avoid //-style comments. Older compilers don't understand
them.
Not only 'older' compilers, also 'stricter' compilers.
One of my pet-peeves. Sorry. // comments are bad style.
my $a = 1 // This is comment
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #41975]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=41975
I had to fix lib/Parrot/Pmc2c/PMETHODS.pm in order to get parrot to
compile.
Klaas-Jan Stol (via RT) wrote:
as requested by particle to send this to the list, attached a patch of
an implementation of PIR in C. Instead of using a bottom-up parser
(using Yacc), this is a pure-C top-down approach.
This is quite cool! Keep us updated as you continue working on it.
I'm
I am very interested in this. I've done a little bit of work like this in the
past, for projects like Java::Swing which is a thin Inline::Java facade for
coding swing UI front ends in what appears to be pure Perl.
But, your plan is more intense. In particular it is more intense than $500.
On Wed, Mar 21, 2007 at 06:39:51PM -0700, Allison Randal wrote:
Agreed. And we don't work from the installation paths because the
installation paths are broken. Can we break out of this cycle with some
automated tests for the installed Parrot?
That would be pretty slick. :-)
Steve
--
On Wed, Mar 21, 2007 at 03:13:55PM -0700, Allison Randal wrote:
Steven Pritchard wrote:
I spent some more time getting a package built for Fedora. It
probably goes without saying, but this is still a bit difficult. If
anyone is interested, here's my current package:
Thanks, Steve. Have
Hi all,
I am recently working on the QT4/KDE4 bindings for p5.
First cpp headers are parsed by a grammar based on Parse::RecDescent,
The production of latest dev release Parse-QTEDI-0.02_01 is quite stable,
presenting all related interface information of cpp .h.
I will continue to make it
17 matches
Mail list logo
