nally, but very importantly imo, what if there are 3 or more
alternatives?
love, raiph
citing for me. "What is Rakudo Star?
Well, it's..."
I would love to see this meme encouraged, the notion that we all get
to continuously (re)define just what Rakudo Star is.
--
love, raiph
2], and James et al had suggested using it to
declare units [3].
I've long been in Mark's camp about a lightweight and attractive
docstring syntax being likely to be helpful for encouraging habits
that would likely contribute to improved long term maintainability of
code with com
spects of macros, the existing unfinished POD6 spec, and
any other relevant existing bits I'm forgetting.
Did that make sense? Anyone interested? ;)
--
love, raiph
S26 this week-end. I very much hope that this
> new revision will satisfy The Overmeer Desiderata [1] too.
>
> Damian
>
>
> [1] Sounds like a Robert Ludlum novel, eh?
With this whiny man exchange ultimately having bourne supreme fruit,
the apocalypse watch for the post damian weekend begins...
--
love, raiph
an ugly/heavyweight/suboptimal approach.
Anyhoo, thanks for the time spent and great design skills that are so
evident in this new spec. :)
--
love, raiph
ry* good
> sandbox. Is that worth it?
>From the spec:
However, during parsing and initialization under K<-doc>, the
interpreter only executes those C, C, and
C blocks (and equivalents, such as C statements
and subroutine declarations) that are preceded by the special
prefix: C
--
love, raiph
s
use'd files, and merely parses but does not execute DOC blocks in the
file passed on the command line and files it use's.
--
love, raiph
declaration which has just been parsed, or which is just about to be
parsed, and that simply referencing these variables would be ok and
would save the need to create explicit named anchors.
--
love, raiph
s intended for
posts related to language design. (Which is why just about
the only traffic is the slow trickle of updates to the language
specification, which is relatively stable, and a very occasional
burst of discussion about some topic. It may get noisier in the
second half of this year when concurrency starts to get a work
through, but I think most of that will be on #perl6 too.)
Hth,
--
raiph
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:
>
>> O
oundation
will
be replaced by a "homotopical interpretation of type theory".
I have about zero understanding of what this stuff is or if it will have any
impact on programming language type systems, but thought I'd speak up. :)
--
raiph
e code
you recently published?
How confident are you that your all-in-one CS teaching platform concept
will be taken up by some educational institutions? What timeframe are
you thinking is involved here? Are you thinking P6 is already ready for it?
I don't think we're there yet but it seems
27;s going to be fascinating to see what happens in 2020s re Python vs Perl in
particular and Hindley Milner static typing vs nominal static/dynamic typing]
^3 http://news.perlfoundation.org/2012/12/the-first-twenty-five-years.html
love to all, raiph
14 matches
Mail list logo
