on PIRC

[kjstol]

hi there,

In a lost moment, I came across a parrotsketch log where people
wondered what's the deal with PIRC, and that it needs a champion. (for
the new people: I started PIRC) I'm happy to help people by answering
questions or guiding people through the code. However, I have too
little time to do more coding; mostly because it's been too long that
I've worked on it, which would take a lot of time to get back into it,
but also because I'm stuck, and I don't want to spend too much time on
doing things that doesn't help it further.

If there's anybody out there that feels like taking it on, please feel
free to ask as many questions as you can (can't guarantee I can answer
them all ;-). Also, I've been pondering on alternatives; I've come to
realize that PIRC itself has become quite a big program with
complexities of its own. Perhaps the alternative would be to have a
critical look at the PIR language itself. In the end, it's not PIR
that's going to be used much; it's just a notation for doing low-level
stuff. Ease and efficiency of parsing is more important than all sorts
of neat shorthands, IMHO. Also, PIRC could be seen as a prototype of
how to implement a PIR compiler; I've probably not made the best
decisions along the way. People who want to work on alternatives for
IMCC, I'm happy to help out by sharing experience.

Anyway, I have some expertise on parsing and processing PIR. I'm happy
to transfer knowledge.

cheers,
kjs