Allison Randal ha scritto:
We do. Unfortunately we can't rely on Perl 5 for the configure system.
It may seem like an easy way to gain cross-compilation in the short
term, but in the long term it will hurt us.
Miniparrot is the right way to go. It certainly needs work, though. As
you're thinking of solutions think of what miniparrot would need to
become cross-compiler aware.
ok. I can't say that that I fully understand why, but I trust you.
> woot! I am _not_ going to become a pir programmer, sorry :-)
You'll be surprised at how easy it is to pick up, especially if you
have experience with dynamic languages. There are, of course, plenty
of Parrot tasks that don't require PIR skills, but don't give up
before you try it. You might like it.
please, don't get me wrong. I have absolutely nothing against PIR, is
just that I'm so damn fluent in Perl5 :-)
I follow Parrot from the day it was born, I even wrote some - crude, I
admit it - code in PASM something like 4 years ago
(http://dada.perl.it/shootout/parrot_allsrc.html). but when the first
IMCC appeared, I felt it was just too much. maybe PIR nowadays isn't as
complicated as it was when I left it, I don't know. I will certainly
give it a closer look.
That being the case, let's start you out submitting patches. It's
where everyone starts, and having a mentor to review patches at first
is a great way to pass along the knowledge of the experienced Parrot
hackers.
For a change this size, we generally start with a proposal, review it
as a group, and then dive into implementation. In this case, given the
nature of the problem and your experience with the codebase, go ahead
and start experimenting with code, but write up your plans as you go.
We'll do an architecture review before too long to see how well the
idea fits with the overall plans for Parrot.
I just sent a first patch today (which is small and mostly^W harmless),
commenting what will be my next step(s). I have no "big plan" yet, it's
just a configure-fix-patch-reconfigure cycle, so I try to approach
obstacles as they pop out. when I come to the point that I will need a
"stronger" patch, something that may impact the overall architecture, I
intend to sit down and think about it for a while, write it down and
submit it for your approval.
thank you for your attention and wise words :-)
cheers,
Aldo
