At 02:50 AM 2/19/2001 +, Simon Cozens wrote:
>On Sun, Feb 18, 2001 at 09:34:46PM -0500, Dan Sugalski wrote:
> > At 01:13 AM 2/19/2001 +, Alan Burlison wrote:
> > >Dan Sugalski wrote:
> > >
> > > > Grab one via a utility function. getPMC() or something of the sort.
> > >
> > >newPMC() ? ;-)
On Sun, Feb 18, 2001 at 09:34:46PM -0500, Dan Sugalski wrote:
> At 01:13 AM 2/19/2001 +, Alan Burlison wrote:
> >Dan Sugalski wrote:
> >
> > > Grab one via a utility function. getPMC() or something of the sort.
> >
> >newPMC() ? ;-)
>
> Works for me.
Slight that-sucks alert: So, if I have to
At 01:13 AM 2/19/2001 +, Alan Burlison wrote:
>Dan Sugalski wrote:
>
> > Grab one via a utility function. getPMC() or something of the sort.
>
>newPMC() ? ;-)
Works for me. Though for some reason it brings up visions of the Village
People, and that's generally a Bad Thing... :)
Dan Sugalski wrote:
> Grab one via a utility function. getPMC() or something of the sort.
newPMC() ? ;-)
Alan Burlison
Simon Cozens wrote:
> Larry has guaranteed that Perl 6 will be built "out of the same source tree"
> as Perl 5.
Whatever that means... i.e. not much.
> This is a major win for us in two areas. Firstly, we can reuse the
> information determined by Perl 5's Configure process to help make Perl 6
>
At 12:45 AM 2/19/2001 +, Alan Burlison wrote:
>Dan Sugalski wrote:
>
> > >If PMC is a pointer to a structure, "new" will need to allocate memory
> for a
> > >new structure, and hence the value of mypmc will have to change.
> >
> > Nope. PMC structures will be parcelled out from arenas and not
Dan Sugalski wrote:
> >If PMC is a pointer to a structure, "new" will need to allocate memory for a
> >new structure, and hence the value of mypmc will have to change.
>
> Nope. PMC structures will be parcelled out from arenas and not malloc'd,
> and they won't be freed and re-malloced much. If
On the subject of Unicode string processing...
I'm not a perl internals hacker and more of a passive reader of these
lists than an active contributor.
With that caveat, may I humbly point out a design document for
what I think is a clean C library supporting the use of mixed
encoding forms. I
