On Sat, Mar 10, 2001 at 12:29:43AM +0100, Paolo Molaro wrote:
> My understanding is that symbols with double underscore or underscore
> followed by an uppercase letter are reserved, while _something
> symbols are ok if they are not exported and that is actually
> what we are doing. I prefer _perl
On 03/03/01 Damien Neil wrote:
> > All the function names shall begin with the C prefix. The only exception
> > is function names that may be used only in the perl core: these names shall
> > begin with the C<_perl_> prefix. This will make it possible to export only
> > the perl_* functions from t
At 11:04 PM 3/4/2001 -0500, Stephen P. Potter wrote:
>Lightning flashed, thunder crashed and Damien Neil <[EMAIL PROTECTED]>
>whispered
>:
>| ISO/ANSI C reserves identifiers beginning with a _. I recommend using
>| "perl_" and "perl__" if you want to distinguish internal-only functions
>| from p
Lightning flashed, thunder crashed and Damien Neil <[EMAIL PROTECTED]> whispered
:
| ISO/ANSI C reserves identifiers beginning with a _. I recommend using
| "perl_" and "perl__" if you want to distinguish internal-only functions
| from public ones.
I'd be worried that "_" and "__" are too hard t
On Sat, Mar 03, 2001 at 07:57:54PM +0100, Paolo Molaro wrote:
> All the function names shall begin with the C prefix. The only exception
> is function names that may be used only in the perl core: these names shall
> begin with the C<_perl_> prefix. This will make it possible to export only
> the
