Bram Geron wrote:
The simplest thing I can imagine to create CL/Perl behavior is to
initialize $P0 with nil/undef. But it Doesn't Feel Right(tm) to me doing
this every time. What's your opinion?
Other question: what should compilers do for languages that don't
support multiple values? If such
Author: allison
Date: Sun Jan 6 01:40:35 2008
New Revision: 24580
Modified:
trunk/docs/pdds/draft/pdd09_gc.pod
Log:
[pdd] Adding a reference from chromatic to the GC PDD.
Modified: trunk/docs/pdds/draft/pdd09_gc.pod
Author: allison
Date: Sun Jan 6 01:45:47 2008
New Revision: 24581
Modified:
trunk/docs/pdds/draft/pdd09_gc.pod
Log:
[pdd] Formatting cleanup in the GC PDD.
Modified: trunk/docs/pdds/draft/pdd09_gc.pod
==
---
With the new contributor day coming up, I'd like to run an article on
Perlbuzz about it. Can anyone supply me some text? Or point me to a
preferred old text that I can adapt? I'm looking at http://www.oreillynet.com/onlamp/blog/2007/08/parrot_new_contributor_day_thi.html
which is from
Jarkko's view was that if he were doing Perl 5 Unicode again he would
opt for fixed width 32 bit rather than UTF-8,
It seems to be a general principle of system design that the best way to
process irregular and unpredictable things, is to grab them as close to
the outside of the system as
Thru a series of refactorings of runstep(), I was able to write more
testable internal subroutines and methods, and then write tests for them
t/configure/143-auto_gmp-01.t thru 03.t. I also dealt with the skimply
documentation by quoting from the GNU description of GMP.
Assuming no problems crop
