Another 2 or 3 pennies^1 worth of strawman proposing / bikeshedding /
flight of marketing fancy about naming etc:
Perl's Rapture
===
Imagine we officially embarked on a year+ long communal process in
which we (TPF and Perl community) sort out branding and marketing of
Perlish languages. A
Hi Damian,
The .kxxv method name is a placeholder.
The brief discussion that motivated introducing it is at:
http://irclog.perlgeek.de/perl6/2014-04-13#i_8582049
Larry has chimed in at:
http://irclog.perlgeek.de/perl6/2014-04-14#i_8582684
---
Another discussion that's unfolding rig
On Sun, Nov 17, 2013 at 5:43 PM, Andrew Suffield
wrote:
> While mathematics as a field has mostly settled on set theory as its
> basis,
type theory is equally expressive and is usually preferred in language
> design.
Aiui there is now optimism in some circles that the set theory foundation
will
Perhaps these help?
http://pugs.blogs.com/pugs/2005/02/day_28_609.html
https://www.google.com/#q=site:http%3A%2F%2Fpugs.blogs.com%2F+licensing
--
raiph
On Tue, Nov 5, 2013 at 9:36 AM, Moritz Lenz wrote:
> Hi,
>
>
> On 11/05/2013 03:16 PM, Jan Ingvoldstad wrote:
>
>> On Tue, Nov 5, 2013 at 3
On Mon, Mar 25, 2013 at 11:01 AM, wrote:
> I have created a file called SalesReport.mp6, which contains a grammar
>
> module SalesReport;
> grammar SalesExportGram is export {
Aiui you can now use this module to introduce SalesReport as
a module name and SalesExportGram as a grammar name
Damian:
> While I'm all in favour of other languages using Pod as a documentation
> format,
> I think that's unlikely. Pod says that anything of the form:
>
> =identfiier
>
> *anywhere* as the first non-whitespace of a line, is considered a Pod
> directive.
> I can't see man
> Nonetheless, DOC INIT { system "rm -rf ." } (or etc.) would be unfortunate.
Gotcha. Perhaps something like perl6 -DOC is needed to execute DOC
blocks in the file passed on the command line and files it use's,
whereas perl6 -doc only processes DOC blocks in the Setting or its
use'd files, and mer
> However it seems we have to pay a price: each act of rendering a Pod
> file actually means executing the program that's being documented (at
> least the BEGIN blocks and other stuff that happens at compile time),
> with all the security risks implied. So we'll need a *very* good
> sandbox. Is tha
On Sun, Aug 16, 2009 at 3:26 PM, Damian Conway wrote:
> It's Sunday evening and, as promised, here's the new draft of S26.
Thanks!
After an initial read thru the summary and spec my overall reaction to
the new pod is "whirled peas!". :)
> * Hence it must always parsed using full Perl 6 grammar:
> Excellent idea. But may I suggest you perhaps might like to hold off
> that discussion until next week?
>
> @Larry had some very fruitful discussions about the long-overdue Pod
> spec during YAPC::EU last week and, as a result, I plan to (finally!!!)
> release a new version of S26 this week-end.
On Thu, Aug 13, 2009 at 1:00 AM, Darren Duncan wrote:
> Timothy, you raise a good point...
> [discussion]
> I think this can be made to work without much fuss
I'm curious about these sorts of conversations, and the way the
community works in relation to them.
I'm also curious about this specific
> for the latest spec changes regarding this item, see
> http://perlcabal.org/svn/pugs/revision/?rev=27959.
>
> is everyone equally miserable now? ;)
> ~jerry
Ha! :)
I do indeed feel underwhelmed. I'll surely get over it but I may as
well post why, even though Larry's presumably trying to stop th
> Rakudo Zengi would be the most (in)appropriate, I think.
Why do I get the sense that some in the community are suffering siege
mentality? ;)
I had thought of things like Zen, Zero, Catalyst, etc.
But I love * | Star | Whatever. I love:
o The word Star, regardless of its connection with Perl
13 matches
Mail list logo
