> >Here is an example, "re`sume`" takes 6 characters in Latin-1, but
> >could take 8 characters in Unicode. All Perl functions that directly
> >deal with character position and length will be sensitive to encoding.
> >I wonder how we should handle this case.
>
> My first inclination is to force n
Here's a mildly fixed up version of PDD 4. References to the NUM and INT
types have been reduced to generic concepts rather than data types of some
sort.
Cut Here--
=head1 TITLE
Perl's internal data types
=head1 VERSION
1.1
=head2 CURRENT
Maintainer: Dan Sugalski <
At 12:01 PM 3/5/2001 -0800, Hong Zhang wrote:
> >struct perl_string {
> > void *string_buffer;
> > UV length;
> > UV allocated;
> > UV flags;
> >}
> >
> > The low three bits of the flags field is reserved for the type of the
> > string. The various types are:
> >
> > =o
>struct perl_string {
> void *string_buffer;
> UV length;
> UV allocated;
> UV flags;
>}
>
> The low three bits of the flags field is reserved for the type of the
> string. The various types are:
>
> =over 4
>
> =item BINARY (0)
>
> =item ASCII (1)
>
> =item EBCDIC
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
