Oh, just pick a small section no one else bothers with. I'm setting up
again for working on complex.pmc(setting up, not working). I'm doing
amd64 jit even if it only works on FreeBSD(not enabled by default for a
reason). If you don't do anything/commit anything for a while, it's
still ok. There are things like mod_parrot that will be very useful
and dealing with potential issues will encourage good coding standards
for use with mod_parrot from the start(how many programs need to be
ported to mod_perl?). I also did GetOpts;Obj and even though it has
"issues" and could be adapted for various getopt styles(such as gnu,
bsd, and parrot), I haven't done it, and actually haven't heard much
about it. It was better than what there was at the time, and I haven't
really touched it since.
For another idea, perl has CPAN, and parrot has the potential for
multiple languages to use the same library, that can be optimized in
PIR. A common API for things like CGI across several languages, etc.
Maybe start on being able to embed parrot into a browser?
Parrot offers many little niches. Some benefit parrot's developers,
some benefit parrot, etc... Some are yet to be touched.
Personally I have noticed some of the issues regarding communication,
and have had my aggravations regarding certain areas, but I still
continue.
On Sep 18, 2007, at 3:57 PM, Andy Lester wrote:
I'm sorry to hear that. You're welcome back any time. All
contributions
are valuable, and isn't necessary to follow every detail of every
aspect
of the project to contribute.
Understood. It's just clear that I'm way out the loop on things, and I
don't have the time to talk about the things that I've been wanting to
talk about for a while anyway.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
