--- Simon Cozens <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 10, 2001 at 11:26:03AM -0700, Benjamin Stuhl
> wrote:
> > > It's not a prioirty, but it's so much easier to walk
> the
> > > correct path from the start. Since it's all Parrot,
> it's even easier.
> >
> > Hear, hear! I remember the pain in 5.005_5* of turning
> off
> > PERL_POLLUTE. I expect that there may still be CPAN
> modules
> > that won't build without manually defining it.
>
> You are, of course, correct; I back down. However, if you
> care that
> much, I'm going to make you prove it by implementing it.
> :)
On my personal todo list for this afternoon is to go
through each of the source files and enforce the coding
PDD. However, before I do this, I would like to bring up
the question of prefixes once again. Do we really need a 7
letter, mixed-case prefix (Parrot_)? If Apache can do ap_,
why can't we do par_ (and maybe parp_ for private stuff)?
Also, I am planning to go through the structs and prefix
them (STRING -> PAR_STRIN, for instance) and clean up the
subsystem naming. What do you think of par_gc_* for memory
management (yes, that means that uncollected memory is
gotten by par_gc_memalloc_nogc(), but if you really want
it, you deserve to type in all those letters) and par_io_*
for I/O?
-- BKS
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com
