Brent,
Good stuff. Didn't you also send out a draft PDD about how types should be named and managed in parrot at one point? I, for one, would love to see a PDD that described C-level nanming and namespace management in general. --Josh At 3:11 on 07/14/2002 PDT, "Brent Dax" <[EMAIL PROTECTED]> wrote: > # 2. What does having a Parrot_ prefix signify, considering=20 > # both the opcodes and=20 > # the embed api use it? It's hard to distinguish between them. > > It signifies one of the following: > -This function is externally visible. > -This function belongs to Parrot at large, and not any particular > subsystem (e.g. Parrot_sprintf and friends). > -This function has an identical name to a C library function because it > emulates it for certain platforms (e.g. Parrot_dlopen (?)). > -This function is autogenerated, so we're going to be paranoid about > naming conflicts. > > For functions in the last category, I'd suggest we use > subsystem-specific names, e.g. Op_ for the opcodes. >
