Re: How to handle multiple return values?

[Allison Randal]

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 a language allows calling functions
from other languages, I can imagine obscure bugs appearing.


Whether a routine returns a null value under certain conditions is 
determined by the routine, not by a global setting. So, when CL routines 
are generated by the CL compiler, they'll always generate a default null 
return value (PMCNULL, or Undef, or a custom Nil).


Languages that don't have syntax for multiple return values will need 
wrappers for external libraries that send multiple return values, to 
wrap them in an aggregate data type (array or hash). PIR could provide 
some shortcuts store return values of a sub call in a specified 
aggregate, so the wrapping can be generated within the compiler.


Allison

[svn:parrot-pdd] r24580 - trunk/docs/pdds/draft

[allison]

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
==
--- trunk/docs/pdds/draft/pdd09_gc.pod  (original)
+++ trunk/docs/pdds/draft/pdd09_gc.pod  Sun Jan  6 01:40:35 2008
@@ -408,3 +408,5 @@
 =head1 REFERENCES
 
 "A unified theory of garbage collection" 

+
+"Scalable Locality-Conscious Multithreaded Memory Allocation" 
http://people.cs.vt.edu/~scschnei/papers/ismm06.pdf

[svn:parrot-pdd] r24581 - trunk/docs/pdds/draft

[allison]

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
==
--- trunk/docs/pdds/draft/pdd09_gc.pod  (original)
+++ trunk/docs/pdds/draft/pdd09_gc.pod  Sun Jan  6 01:45:47 2008
@@ -1,4 +1,4 @@
-# Copyright (C) 2001-2004, The Perl Foundation.
+# Copyright (C) 2001-2007, The Perl Foundation.
 # $Id$
 
 =head1 NAME
@@ -9,6 +9,11 @@
 
 This PDD describes how DOD/GC systems work, and what's required of PMC classes.
 
+=head1 VERSION
+
+$Revision$
+
+
 =head1 DESCRIPTION
 
 Doing DOD takes a bit of work--we need to make sure that everything is
@@ -354,59 +359,6 @@
 
 =head1 REFERENCES
 
-None.
-
-=head1 VERSION
-
-=head2 CURRENT
-
-Maintainer: Dan Sugalski
-Class: Internals
-PDD Number: 9
-Version: 1.2
-Status: Developing
-Last Modified: 26 August 2004
-PDD Format: 1
-Language: English
-
-=head2 HISTORY
-
-=over 4
-
-=item Version 1.2
-
-26 August 2004
-
-=item Version 1.1
-
-26 February 2002
-
-=item version 1
-
-None. First version
-
-=back
-
-=head1 CHANGES
-
-=over 4
-
-=item Version 1.2
-
-Removed old flags. Documented GC schemes and subsystem interface.
-
-=item Version 1.1
-
-Started documenting the internal routines
-
-=item Version 1.0
-
-None. First version
-
-=back
-
-=head1 REFERENCES
-
 "A unified theory of garbage collection" 

 
 "Scalable Locality-Conscious Multithreaded Memory Allocation" 
http://people.cs.vt.edu/~scschnei/papers/ismm06.pdf

Re: what should be the default extension?

[Juerd Waalboer]

Larry Wall skribis 2008-01-05 17:39 (-0800):
> Already specced.  (...)
> It should probably mention Unicode there as well, but the principle is
> already expressed in terms of case-sensitivity.

You're always a few steps ahead :)
-- 
Met vriendelijke groet,  Kind regards,  Korajn salutojn,

  Juerd Waalboer:  Perl hacker  <[EMAIL PROTECTED]>  
  Convolution: ICT solutions and consultancy <[EMAIL PROTECTED]>

Perl 6 new contributor day

[Andy Lester]

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 August, and doesn't discuss what we'll be focusing on.


And, once we have that up, I'd like to put up a graphic ad/link on the  
front of Perlbuzz that points to it, like the Frozen Perl ad that's up  
there now.  Anyone with mad graphix skillz wanna come up with something?


Thanks,
xoxo,
Andy

--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: Repeated Loopy Variable Width String Character Access is Slooooow-ish

[ajr]

>
>> > 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 possible, make sure they're not dangerous,
stuff them into closed, standard boxes, and only deal with the problems of
the boxes.

This is illustrated examples as diverse as disk-drives, (which went from
variable-length to fixed-sized blocks early in their development), to
container shipping.

> It's not insane to have the boundary near the outside of parrot.

Any system that doesn't assume input from the outside world to be toxic
until proven otherwise is being dangerously naive. However, paranoia's
expensive, so you want to concentrate it as much as possible.


--

Email and shopping with the feelgood factor!
55% of income to good causes. http://www.ippimail.com

Re: what should be the default extension?

[ajr]

>
> No, some people put .pl on the end of their "scripts" because they are
> running on broken operating systems.
>

> So, I imagine, for Perl6, I'll be making the same strong recommendation
> that Perl6 scripts, just like Perl5 and Perl4 scripts before them, have
*no*
> extension.
>
>Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777

Enthusiastically seconded! Why should we let the language of Mordor
corrupt our discourse?



--

Email and shopping with the feelgood factor!
55% of income to good causes. http://www.ippimail.com

[perl #43312] [TODO] config/auto/gmp.pm: Write unit tests

[James Keenan via RT]

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 up in the next 24 hours, I will resolve the
ticket.

Thank you very much.
kid51