The reason I think parrot-compilers would be useful, is that its
dedicated to helping people (like me) write compilers for parrot,
whereas (in my understanding), perl6-internals@ is really about the
development of the vm itself (I would subscribe to both). I see
parrot-compilers@ as opening up more questions from people struggling
with the current apis than perl6-internals@ - at least I'll post more. :)
Jeff Clites wrote:
> On Nov 17, 2003, at 11:22 AM, Melvin Smith wrote:
>> In the past couple of years we've seen several sub-projects pop-up
>> I propose creating 'parrot-compilers' as a general
> So I'll be one of the few nay-sayers. I'm not definitely against it, but
> 1) It's likely that we've seen very little traffic (at least recently)
> 2) Forking a list almost always leads to an increase of messages of the
> I doubt that the name of the current list is actually a big problem,
> Again, I'm not dead-set against it--I just don't think it would improve
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.