Re: Looking for help updating Perl 6 and Parrot part of Perl Myths talk

2009-09-25 Thread Tim Bunce
I gave the talk at OSSBarcamp in Dublin last weekend and it went well.
My sincere thanks to everyone who contributed.

The slides are available at:

http://www.slideshare.net/Tim.Bunce/perl-myths-200909

The graphs and stats charting the continuing growth of perl and the perl
community were surprising (and delighting) even to me.  

The presentation was even featured on the slideshare.net home page for a
while. Yeah!

I'll be giving the talk again at HighLoad++ in Moscow in a couple of
weeks time, and possibly again at IPW09 in Pisa later in October (though
it's not been scheduled yet). So I'd be grateful for any feedback on
the talk. Corrections, improvements, extra data etc.

Thanks again!

Tim.

p.s. I've already fixed the suprious reference to CPANTS.



r28403 - in docs/Perl6/Spec: . S32-setting-library

2009-09-25 Thread pugs-commits
Author: jimmy
Date: 2009-09-25 12:32:57 +0200 (Fri, 25 Sep 2009)
New Revision: 28403

Modified:
   docs/Perl6/Spec/S21-calling-foreign-code.pod
   docs/Perl6/Spec/S26-documentation.pod
   docs/Perl6/Spec/S28-special-names.pod
   docs/Perl6/Spec/S32-setting-library/Abstraction.pod
   docs/Perl6/Spec/S32-setting-library/Basics.pod
   docs/Perl6/Spec/S32-setting-library/Callable.pod
   docs/Perl6/Spec/S32-setting-library/Containers.pod
   docs/Perl6/Spec/S32-setting-library/Exception.pod
   docs/Perl6/Spec/S32-setting-library/IO.pod
   docs/Perl6/Spec/S32-setting-library/Numeric.pod
   docs/Perl6/Spec/S32-setting-library/Rules.pod
   docs/Perl6/Spec/S32-setting-library/Str.pod
   docs/Perl6/Spec/S32-setting-library/Temporal.pod
Log:
[Spec]use standard dialect 'Pod' 

Modified: docs/Perl6/Spec/S21-calling-foreign-code.pod
===
--- docs/Perl6/Spec/S21-calling-foreign-code.pod2009-09-25 07:38:32 UTC 
(rev 28402)
+++ docs/Perl6/Spec/S21-calling-foreign-code.pod2009-09-25 10:32:57 UTC 
(rev 28403)
@@ -19,7 +19,7 @@
 
 The document is a draft.
 
-If you read the HTML version, it is generated from the pod in the pugs
+If you read the HTML version, it is generated from the Pod in the pugs
 repository under /docs/Perl6/Spec/S21-calling-foreign-code.pod so edit it 
there in
 the SVN repository if you would like to make changes.
 

Modified: docs/Perl6/Spec/S26-documentation.pod
===
--- docs/Perl6/Spec/S26-documentation.pod   2009-09-25 07:38:32 UTC (rev 
28402)
+++ docs/Perl6/Spec/S26-documentation.pod   2009-09-25 10:32:57 UTC (rev 
28403)
@@ -26,7 +26,7 @@
 is known to be out of date and likely to undergo some substantial
 revision.  Until the document is updated, look at STD.pm
 (L) for the valid
-POD syntax.
+Pod syntax.
 
 =head1 Perldoc
 
@@ -43,7 +43,7 @@
 =head1 The Pod Dialect
 
 B is an evolution of Perl 5's L|doc:perlpod>
-(POD) markup. Compared to Perl 5 POD, Perldoc's Pod dialect is much more
+(Pod) markup. Compared to Perl 5 POD, Perldoc's Pod dialect is much more
 uniform, somewhat more compact, and considerably more expressive. The
 Pod dialect also differs in that it is a purely descriptive mark-up
 notation, with no presentational components.

Modified: docs/Perl6/Spec/S28-special-names.pod
===
--- docs/Perl6/Spec/S28-special-names.pod   2009-09-25 07:38:32 UTC (rev 
28402)
+++ docs/Perl6/Spec/S28-special-names.pod   2009-09-25 10:32:57 UTC (rev 
28403)
@@ -38,7 +38,7 @@
 
 $?foo   # Compiler constants (fixed at compile time)
 $*foo   # Context variable, default global (run time)
-$=foo   # File-scoped POD data
+$=foo   # File-scoped Pod data
 
 The various C<$?foo> variables are determined at compile time, and are
 not modifiable at run time.  This does not mean that the variable has the
@@ -59,7 +59,7 @@
 The C<$=foo> variables are related to the C<$?foo> variables
 insofar as the text of the program is known at compile time, so the
 values are static.  However, the different twigil indicates that the
-variable contains POD data, which is primarily under user control
+variable contains Pod data, which is primarily under user control
 rather than compiler control.  The structure of these variables will
 be fleshed out in S26.
 

Modified: docs/Perl6/Spec/S32-setting-library/Abstraction.pod
===
--- docs/Perl6/Spec/S32-setting-library/Abstraction.pod 2009-09-25 07:38:32 UTC 
(rev 28402)
+++ docs/Perl6/Spec/S32-setting-library/Abstraction.pod 2009-09-25 10:32:57 UTC 
(rev 28403)
@@ -19,7 +19,7 @@
 
 The document is a draft.
 
-If you read the HTML version, it is generated from the pod in the pugs
+If you read the HTML version, it is generated from the Pod in the pugs
 repository under /docs/Perl6/Spec/S32-setting-library/Abstraction.pod so edit 
it there in
 the SVN repository if you would like to make changes.
 

Modified: docs/Perl6/Spec/S32-setting-library/Basics.pod
===
--- docs/Perl6/Spec/S32-setting-library/Basics.pod  2009-09-25 07:38:32 UTC 
(rev 28402)
+++ docs/Perl6/Spec/S32-setting-library/Basics.pod  2009-09-25 10:32:57 UTC 
(rev 28403)
@@ -24,7 +24,7 @@
 
 The document is a draft.
 
-If you read the HTML version, it is generated from the pod in the pugs
+If you read the HTML version, it is generated from the Pod in the pugs
 repository under /docs/Perl6/Spec/S32-setting-library/Basics.pod so edit it 
there in
 the SVN repository if you would like to make changes.
 

Modified: docs/Perl6/Spec/S32-setting-library/Callable.pod
===
--- docs/Perl6/Spec/S32-setting-library/Callable.pod2009-09-25 07:38:32 UTC 
(rev 2

r28404 - docs/Perl6/Spec

2009-09-25 Thread pugs-commits
Author: jimmy
Date: 2009-09-25 14:32:52 +0200 (Fri, 25 Sep 2009)
New Revision: 28404

Modified:
   docs/Perl6/Spec/S02-bits.pod
Log:
[Spec/S02-bits.pod]use standard dialect 'Pod'

Modified: docs/Perl6/Spec/S02-bits.pod
===
--- docs/Perl6/Spec/S02-bits.pod2009-09-25 10:32:57 UTC (rev 28403)
+++ docs/Perl6/Spec/S02-bits.pod2009-09-25 12:32:52 UTC (rev 28404)
@@ -358,9 +358,9 @@
 
 $x\#`[   comment 1
 comment 2
-=begin podstuff
+=begin Podstuff
 whatever (Pod comments ignore current parser state)
-=end podstuff
+=end Podstuff
 comment 3
 ].++
 



Re: Looking for help updating Perl 6 and Parrot part of Perl Myths talk

2009-09-25 Thread Moritz Lenz
Moritz Lenz wrote:
> Carl Mäsak wrote:
>> Tim (>):
>>> Anything else I should add, change or remove? I'm especially interested
>>> in verifyable metrics showing effort, progress, or use. Ideally graphical.
>>> Any interesting nuggets that fit with the theme will be most welcome.
>> 
>> Moritz++ and I were talking about making a graph showing the increase
>> of Perl 6 projects lately. Proto's project.list contains all the
>> pertinent history, so half an hour with git-log and SVG::Plot ought to
>> be able to produce something nice. If no-one else takes that as a
>> hint, I might look at it soonish. :)
> 
> I know produced this plot, attached is a .png, the perl script that
> generates the data file and gnuplot file which turns that into a .png.

Thanks to masak's contribution we now have a plot containing also the
earlier history of proto, and is daily updated on http://rakudo.de/

It is not completely accurate, but it's a enough for a broad trend line.

I know the talk is over now, but maybe somebody wants to hold such a
talk in the future, too.

Cheers,
Moritz


Should .^methods be curried with the invocant?

2009-09-25 Thread Moritz Lenz
Consider this case:

class A { method m { say 'OH HAI' } };
my $m = A.new.^methods(:local).[0];

How should I invoke $m?
In current Rakudo this works:
$m(A.new);  # supply the invocant as first argument

But shouldn't be just $m() (invocant magically curried) or may
$m(A.new:) (invocant not curried, but marked with a colon)?

Cheers,
Moritz


Re: Should .^methods be curried with the invocant?

2009-09-25 Thread Daniel Ruoso
Em Sex, 2009-09-25 às 18:28 +0200, Moritz Lenz escreveu:
> class A { method m { say 'OH HAI' } };
> my $m = A.new.^methods(:local).[0];
> How should I invoke $m?
> In current Rakudo this works:
> $m(A.new);# supply the invocant as first argument
> But shouldn't be just $m() (invocant magically curried) or may
> $m(A.new:) (invocant not curried, but marked with a colon)?

Methods are only methods when they are dispatched as methods, otherwise
they are regular subs. The invocant in the capture is just the first
positional argument, so $m(A.new) is what you want, although $m(A.new: )
should have the same effect.

daniel





Lenses?

2009-09-25 Thread Timothy S. Nelson
	I've been wondering about lenses recently.  The page at 
http://www.seas.upenn.edu/~harmony/ seems to give an overview, and I know that 
augeas also uses lenses.


	It seems to me that a grammar can be thought of as a one-way lens.  I 
was wondering whether the bi-directional idea might be interesting in this 
context.  It seems to me that, at the moment, when we want to do a format 
conversion, we:

-   Read the data in with a grammar
-   Output the data with something like Form.pm

	I'm wondering if there isn't some way that the whole thing can be 
turned into lenses.


	Anyway, I'm sort of half thinking out loud, and wondered if anyone had 
any relevant thoughts.



-
| Name: Tim Nelson | Because the Creator is,|
| E-mail: wayl...@wayland.id.au| I am   |
-

BEGIN GEEK CODE BLOCK
Version 3.12
GCS d+++ s+: a- C++$ U+++$ P+++$ L+++ E- W+ N+ w--- V- 
PE(+) Y+>++ PGP->+++ R(+) !tv b++ DI D G+ e++> h! y-

-END GEEK CODE BLOCK-