S22-package-format.pod
Log Message:
---
Update S22 with our current thoughts about dependencies
/style.css
Log Message:
---
Match historical message style with that of auto-generated subpages
-routines.pod
Log Message:
---
Bring parameter semantics in line with reality.
Besides being what is implemented, these also allow for more/better
optimization (we already have optimizations that depend on them; if
we took the previous semantics, things like spesh would be unable to
rely
S32-setting-library/Basics.pod
Log Message:
---
fossil eval replaced with EVAL
S12-objects.pod
Log Message:
---
problems with grammar attributes and a solution
One could say one cannot _declare_ grammar attributes but rakudo barks only
when we use them.
For more context:
https://rt.perl.org/Ticket/Display.html?id=122253
http://irclog.perlgeek.de/perl6/2015-03
If this is about:
These may be cascaded:
with $s.index("a") { "Found a at $_" }
orwith $s.index("b") { "Found b at $_" }
orwith $s.index("c") { "Found c at $_" }
else { "Didn't find a, b or
Is there an error in the cascade? Shouldn't the indices be 'a', 'b',
'c'; not 'a','a','a' ?
On 08/10/2015 11:26 PM, yary wrote:
"with", "without" look awesome.
-y
On Sat, Aug 8, 2015 at 2:38 PM, GitHub &l
"with", "without" look awesome.
-y
On Sat, Aug 8, 2015 at 2:38 PM, GitHub wrote:
> Branch: refs/heads/master
> Home: https://github.com/perl6/specs
> Commit: 614b6f36e1cae4c787e378bc6ab2afa1f86de1f0
>
> https://github.com/perl6/specs/commit/614b6
-control.pod
Log Message:
---
doc with/without
-bits.pod
Log Message:
---
Fix a copy-paste that had left hash example with wrong brackets
-setting-library/Str.pod
Log Message:
---
Update S32::Str to align better with S15
This commit removes quite a bit of cruft from the pre-S15 days, and
additonally reformats the code blocks so that they stand out more in the
file, and for longer function signatures, makes them less
S03-operators.pod
Log Message:
---
S03: $() definition now consistant with S05
:
M S29-functions.pod
Log Message:
---
s/evalfile/EVALFILE/, for consistency with EVAL.
:
M S32-setting-library/Numeric.pod
Log Message:
---
Concur with implementation of Complex.roots
-setting-library/Containers.pod
Log Message:
---
Replace "uniq" fossil with "unique".
-setting-library/IO.pod
Log Message:
---
Format code-like string with C< >
Commit: 55b63455f0ae363d8b401d9e15dd040a5b881696
https://github.com/perl6/specs/commit/55b63455f0ae363d8b401d9e15dd040a5b881696
Author: Paul Cochrane
Date: 2015-02-14 (Sat, 14 Fe
-bits.pod
Log Message:
---
Explicitly spec sigiled form of adverb with twigil
-bits.pod
Log Message:
---
interaction of :{} with other adverbialoids
Hi Reini.
On 2014-10-15 16:21, Reini Urban wrote:
Current parrot behaviour for exhausted yields is dying with "Cannot
resume dead coroutine."
parrot coros are designed after lua, but lua does return nil and as
2nd return value announces also "cannot resume dead coroutine&quo
Current parrot behaviour for exhausted yields is dying with "Cannot
resume dead coroutine."
parrot coros are designed after lua, but lua does return nil and as
2nd return value announces also "cannot resume dead coroutine". most
lisp's also behave the same way.
As thir
:
M S17-concurrency.pod
Log Message:
---
Don't spec new stuff with _ anymore
Commit: a6e8af2b2a49e79afeaae94f1e6e3136415e8db5
https://github.com/perl6/specs/commit/a6e8af2b2a49e79afeaae94f1e6e3136415e8db5
Author: Elizabeth Mattijsen
Date: 2014-09-14 (Sun, 14 Sep
:
M S22-package-format.pod
Log Message:
---
Some more clarifications, especially with provides
:
M S22-package-format.pod
Log Message:
---
Tweaks, make examples more in line with each other
S11-modules.pod
Log Message:
---
"excludes" key formatting consistent with others
-regex.pod
Log Message:
---
bring in line with <:Cc>
On Dec 21, 2013, at 12:00 AM, Moritz Lenz wrote:
> On 12/20/2013 04:52 AM, Richard Hainsworth wrote:
>> OK x not xx.
>>
>> The doubling of operators is confusing.
>
> OTOH having a single operator which two different meanings is also confusing
> (and very un-perlish).
Sometimes, yeah. On a r
On 12/20/2013 04:52 AM, Richard Hainsworth wrote:
OK x not xx.
The doubling of operators is confusing.
OTOH having a single operator which two different meanings is also
confusing (and very un-perlish).
Cheers,
Moritz
lt on parrot 5.5.0 revision 0
>>> $ perl6
>>> > say '0' xx 4
>>> 0 0 0 0
>>
>> Are you sure you didn't want the x (string repetition) operator, instead
>> of xx (list repetition)?
>>
>>> > print '0' xx 4
>&g
built on parrot 5.5.0 revision 0
$ perl6
> say '0' xx 4
0 0 0 0
Are you sure you didn't want the x (string repetition) operator,
instead of xx (list repetition)?
> print '0' xx 4
> print 's' ~ ('0' xx 4)
s0 0 0 0>
I'm not sure why
he x (string repetition) operator, instead
of xx (list repetition)?
> print '0' xx 4
> print 's' ~ ('0' xx 4)
s0 0 0 0>
I'm not sure why the elements of the expansion are padded with a
trailing space in one context but not in another.
print calls
0 0>
I'm not sure why the elements of the expansion are padded with a
trailing space in one context but not in another.
I wasn't sure whether this is the specified behaviour. If it is how can
it be turned off?
Richard
) union, intersection and negation type connectives. You
can try it here http://www.cduce.org. It is also included in all major linux
distributions.
If you are more interested at the theory rather than the implementation,
then I suggest to start with the paper "A gentle introduction on sem
-concurrency.pod
Log Message:
---
close a channel with .close
ental to access arbitrary list
elements; the orderedness also makes working with these as I want to much much
simpler as its easy to identify the element that gives you context to interpret
the other elements. -- Darren Duncan
-concurrency.pod
Log Message:
---
remove sig collision with placeholders
Thanks a lot to Andrew, John, Raiph, and any later responders. What you've said
so far looks very useful to me, and I will follow up on the leads you gave. --
Darren Duncan
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
On 2013 Nov 17, at 17:10, Darren Duncan wrote:
I recall reading that at least in certain math/logic papers that a
programming language type system can be defined logically in terms
of pure sets, making it essentially self-defined without needing to
rely on external definitions of for example
heory is equally expressive and is
usually preferred in language design.
> Does Haskell at least conceptually work in terms like I described?
> I seem to recall reading that how it logically thinks about string
> values is towards that direction.
Haskell, like most vaguely modern langu
ll at least conceptually work in terms like I described? I seem to
recall reading that how it logically thinks about string values is towards that
direction.
Or to be more clear, what I *actually* am looking to design is a system with a
single concrete base type that can represent all pos
I ran into a problem at the weekend and reduced it to a fragment and
then looked at alternatives.
The problem is in snippet bug2_2 below. There is a type check that
fails, but the types appear to be the same. This may be an existing bug.
The problem is that when I put the return type in the su
:
M S32-setting-library/Containers.pod
Log Message:
---
Bring the spec of Range in sync with the implementation
-bits.pod
Log Message:
---
can't mix 'my Dog $x' with 'my $x of Dog'
-setting-library/Containers.pod
Log Message:
---
Revert "[S32/Containers] specify :with for .uniq/.squish"
This reverts commit ec1b7c619dec5b6d7b779c97bfefc4e2285e72f6.
Conflicts:
S32-setting-library/Containers.pod
-setting-library/Containers.pod
Log Message:
---
[S32/Containers] specify :with for .uniq/.squish
See http://irclog.perlgeek.de/perl6/2013-08-03#i_7407490 for
relevant spec discussion.
-glossary.pod
Log Message:
---
[S99] associativity's got nothing to do with it :)
Commit: 793babac4bf1316f787b2a08403bb7b1ca6b072c
https://github.com/perl6/specs/commit/793babac4bf1316f787b2a08403bb7b1ca6b072c
Author: Carl Masak
Date: 2013-07-01 (Mon, 01 Jul
:
M S10-packages.pod
Log Message:
---
Perl 5 now *does* allow packages with block scoping
:
M S02-bits.pod
Log Message:
---
Some clarifications on using adverbs with subscripts
Please consider this a draft, a discussion piece if you will. I simply
got inspired by http://irclog.perlgeek.de/perl6/2013-05-21#i_7098764
:
M S02-bits.pod
Log Message:
---
Added omitted square brackets example with parametric typing.
-operators.pod
Log Message:
---
set ops go with junctive and chaining ops
So I guess we have a rare failure of a spam filter. -- Darren Duncan
[1]Staffing.org - Weekly Research Update
[2]Home|[3]Store|[4]Products & Services|[5]Library
|[6]About Us
CFOS NOT ALIGNED WITH MARKETING Sept 20
[7]What is your staffing budget for 2012? More or less than last year? What are
you planning to ask for in 2013 and
recations
+ Moved dynpmc/os to pmc os. loadlib 'os' is not needed anymore.
- Platforms
+ Fixed for the FileHandle open method the append mode on Windows.
+ Fix compilation on Windows without working mt.exe
+ Detect GNU/Hurd as linux proper.
+ Fixed b
-regex.pod
Log Message:
---
relationship of :sigspace with %
The rules follow from the way sigspace is enabled by previous matcher.
fixes #22
-regex.pod
Log Message:
---
:p is incompatible with scanners
:p may not be used with :ex, :ov, :g, :nth, or :x modifiers.
fixes #16
-io.pod
M S32-setting-library/IO.pod
Log Message:
---
[IO] start IO refactoring with an overview over the new design
The rest of S32::IO still reeks of over-engineering
Commit: 1aa555e10811b3eddb24995abc6b3b916adac516
https://github.com/perl6/specs/commit
S16-io.pod
M S32-setting-library/IO.pod
Log Message:
---
[IO] start IO refactoring with an overview over the new design
The rest of S32::IO still reeks of over-engineering
Commit: 1aa555e10811b3eddb24995abc6b3b916adac516
https://github.com/perl6/specs/commit
On Mon, Jun 4, 2012 at 12:01 AM, Peter Scott wrote:
> We need multiple paths. The term "beginner" creates problems
I meant "beginner" with respect to Perl 6, but I think that Peter
basically paraphrased my arguments about the problem.
Although programming experience i
On Tue, 22 May 2012 19:35:34 -0400, Parrot Raiser wrote:
> The problem we have is to provide a path for learning 6, that presents a
> comprehensible but useful subset of the language to the average user as
> soon as possible, while leading the programmer with more complex needs,
>
On Wed, May 30, 2012 at 6:00 AM, Moritz Lenz wrote:
>
> I'd still start with simple script files, because that's what most
> programmers are most familiar with.
>
I'd do them in Huffman order; the interpreter involves the least
typing to start, and it's useful for
ting now on an "official" rewrite would be able
to do this, or whether it would reduce the (already low) number of people
working on the existing Perl 5 codebase
b) Personally, I'm not sure if it's worth it. What does it gain?
You still have all the warts of the Per
p requires
slightly more input, so that's the order I would introduce them.
I'd still start with simple script files, because that's what most
programmers are most familiar with.
When introducing a programming language, as opposed to teaching
programming from scratch, it should not
On Sat, May 26, 2012 at 6:34 PM, Nicholas Clark wrote:
> On Fri, May 25, 2012 at 08:44:30AM -0500, B. Estrade wrote:
>
>
> Realistically, that's not going to happen. The internals of the Perl 5
> interpreter are not flexible enough to implement a lot of the features
> that
> Perl 6 has that Perl
can't we write a brand new perl5 interpreter or a better one based on
> parrot VM if perl6's strength more than perl5 is just internals of the
> interpreter?
That's what Ponie is/was, right?
I think there is a major disconnect with providing a standard
interpreter versus providi
e
.". That allows the Perl maven to skip forward enlightened, and
the beginner to keep learning.
Learning's a process of building on previous foundations, and so is
programming. Somebody creating simple tabulations may never need the
techniques of the compiler writer, but the compiler c
On Sat, May 26, 2012 at 05:34:18AM +0530, Siddhant Saraf wrote:
> Rakud[o] is not _the_ reference implementation of Perl 6. Actually, there is
> no reference implementation for Perl 6. There never will be. Whoever wants
> to make a perl6 implementation is free to do so. Just follow the spec and
> y
the ease
of mixing html code with scripting language, and so on.
Personally, I would like to be able to write perl6 scripts (even if only
a subset of perl6 was available) that can be embedded in html files.
Since perl6 is just so much more elegant than javascript, it would
attract a lot of prog
e old projects using Perl 5 will retire.
But this will take a long time - much longer than the transition from
Perl 4. With Perl 4 to Perl 5, it was the same people releasing Perl 5 as
had worked on Perl 4, so all development stopped on Perl 4 when Perl 5 came
out. Not just "new features",
ion (OpenPerl?) and allowing the
> reference implementation (Rakudo) to take center stage.
All those people who propose a rebranding assume that a good name will
just be found with a bit of thought. So far I haven't heard a single
good one.
(OpenPerl? I don't think Perl 6 is more open
ree to do so. Just follow the spec and
you get to label your compiler as a Perl6 implementation. yay !
>For that matter, I also shouldn't have to be hit with the fact that
>it's built on Parrot. We don't have to get reminded that Java is based
>on a JVM each time it's m
Any contributions in that area are greatly appreciated.
>
> Am 23.05.2012 01:35, schrieb Parrot Raiser:
>
> >The problem we have is to provide a path for learning 6, that presents a
> >comprehensible but useful subset of the language to the average user
> >as soon as poss
of the language to the average user
as soon as possible, while leading the programmer with more complex needs,
(and greater abilities), to the features they need or will appreciate.
The Synopses are comprehensive. They define the language in great depth,
feature by feature, (some features bordering
ehensible but useful subset of the language to the average user
as soon as possible, while leading the programmer with more complex needs,
(and greater abilities), to the features they need or will appreciate.
The Synopses are comprehensive. They define the language in great depth,
feature by fea
-bits.pod
Log Message:
---
Bind of Nil with := is primitive
(But parameter binding is ::= semantics, which treats Nil as if no arg had been
passed.)
-control.pod
Log Message:
---
gather/take is lexotic with dynamic fallback
We have to allow for implementations and libraries to use gather/take
internally. To preserve the sanity of the user in such cases,
we need gather/take to behave lexotically, so that if you use take
in the
nore...@github.com wrote:
Commit: 17795925bc48affda10275bd2768e1f2d9ef6345
http://github.com/perl6/specs/commit/17795925bc48affda10275bd2768e1f2d9ef6345
Author: TimToady
Date: 2010-09-23 (Thu, 23 Sep 2010)
Log Message:
---
s/series/sequence/ to accord with math culture
To a
-regex.pod
M S09-data.pod
M S32-setting-library/Containers.pod
Log Message:
---
s/series/sequence/ to accord with math culture
To a mathematician, a series is the sum of a sequence. We don't want
to confuse the poor mathematicians any more than they already are.
/Containers.pod
Log Message:
---
copy-paste issues with new roll method
jkpeters_37++ points out a problem in the new specs for .roll, which
are now revised for (I hope) more clarity.
PLEASE from Intercal. :)
- --
brandon s. allbery [linux,solaris,freebsd,perl] allb...@kf8nh.com
system administrator [openafs,heimdal,too many hats] allb...@ece.cmu.edu
electrical and computer engineering, carnegie mellon university KF8NH
-BEGIN
code is compiled, on the
grounds that compiling the code is a way of saying, "I'm finished with this, it
all works and I don't expect to be changing it any more". Library modules will
presumably be compiled, so that would prevent warnings from code you didn't
even write. (
Author: lwall
Date: 2010-07-11 19:09:44 +0200 (Sun, 11 Jul 2010)
New Revision: 31626
Modified:
docs/Perl6/Spec/S12-objects.pod
Log:
[S12] discuss pessimizing optimizations with augment
Modified: docs/Perl6/Spec/S12-objects.pod
Author: lwall
Date: 2010-07-11 18:53:20 +0200 (Sun, 11 Jul 2010)
New Revision: 31624
Modified:
docs/Perl6/Spec/S05-regex.pod
Log:
[S05] redirect to new char class syntax with patch from cosimo++
Modified: docs/Perl6/Spec/S05-regex.pod
Author: lwall
Date: 2010-07-08 03:37:15 +0200 (Thu, 08 Jul 2010)
New Revision: 31573
Modified:
docs/Perl6/Spec/S32-setting-library/Str.pod
Log:
[Str] limits should default to Inf rather than * since that is (supposedly)
compatible with Int
Modified: docs/Perl6/Spec/S32-setting-library
Author: masak
Date: 2010-07-08 00:19:08 +0200 (Thu, 08 Jul 2010)
New Revision: 31570
Modified:
docs/Perl6/Spec/S32-setting-library/Str.pod
Log:
[S32/Str] saved a few words and lines with "is export"
Modified: docs/Perl6/Spec/S32-setting-libra
Author: sorear
Date: 2010-07-03 06:39:32 +0200 (Sat, 03 Jul 2010)
New Revision: 31532
Modified:
docs/Perl6/Spec/S04-control.pod
Log:
[S04] Clarify interaction of lexical classes and packages with members after
discussion with TimToady
Modified: docs/Perl6/Spec/S04-control.pod
Author: lwall
Date: 2010-06-19 20:04:32 +0200 (Sat, 19 Jun 2010)
New Revision: 31376
Modified:
docs/Perl6/Spec/S10-packages.pod
Log:
[S10] define how CANDO works with respect to lexically-scoped function name
searches
Modified: docs/Perl6/Spec/S10-packages.pod
Author: lwall
Date: 2010-06-19 04:55:36 +0200 (Sat, 19 Jun 2010)
New Revision: 31373
Modified:
docs/Perl6/Spec/S03-operators.pod
Log:
[S03] explain more about the relationship of hypers with lazy infinitude
Modified: docs/Perl6/Spec/S03-operators.pod
Author: lwall
Date: 2010-06-05 21:02:35 +0200 (Sat, 05 Jun 2010)
New Revision: 31128
Modified:
docs/Perl6/Spec/S05-regex.pod
Log:
[S05] posit that cursor lists may be returned to a regex with <.gather { take
... }>
Modified: docs/Perl6/Spec/S05-reg
«+» (1,2) ) ~~ (2,4,4) )
>> ok(( (1,2,3,4) «+« (1,2) ) ~~ (2,4) )
>> ok(( (1,2,3,4) »+» (1,2) ) ~~ (2,4,4,6) )
>> ok(( (1,2,3) »+» (1,2) ) ~~ (2,4,4,6) )
>> ok(( (1,2,3) »+» 1) ~~ (2,4,4,6) )
>>
>> I tested these all with Rakudo, and they all currently fai
(1,2) ) ~~ (2,4) )
> ok(( (1,2,3,4) »+» (1,2) ) ~~ (2,4,4,6) )
> ok(( (1,2,3) »+» (1,2) ) ~~ (2,4,4,6) )
> ok(( (1,2,3) »+» 1 ) ~~ (2,4,4,6) )
>
> I tested these all with Rakudo, and they all currently fail, though I guess
> that's not shocking.
~~ (2, 4, 4) (
) ) ~~ (2,4,4,6) )
ok(( (1,2,3) »+» 1 ) ~~ (2,4,4,6) )
I tested these all with Rakudo, and they all currently fail, though I guess
that's not shocking.
--
Aaron Sherman
Email or GTalk: a...@ajs.com
http://www.ajs.com/~ajs
Darren Duncan wrote:
> With the above addition, you have both Buf and Blob roles as well as Buf and
> Blob types.
>
> I think you need to make each of those just a role or a type, and then add
> another named entity which is the counterpart role or type.
>
> For example, as
Smylers wrote:
> pugs-comm...@feather.perl6.nl writes:
>
>> Author: lwall
>> Log:
>> [S03] refine hyper dwimminess to be more like APL, with modular semantics
>>
>> + (1,2,3) »+» 1 # 2,4,4,6 rhs dwims to (1 xx *).batch(3)
>
> I'd
pugs-comm...@feather.perl6.nl wrote:
Author: lwall
Date: 2010-06-02 19:30:34 +0200 (Wed, 02 Jun 2010)
New Revision: 31051
Modified:
docs/Perl6/Spec/S02-bits.pod
Log:
[S02] refine Blobs to simply be immutable Bufs, with similar generic
characteristics
Thank you for this change; it was
Author: lwall
Date: 2010-06-02 19:30:34 +0200 (Wed, 02 Jun 2010)
New Revision: 31051
Modified:
docs/Perl6/Spec/S02-bits.pod
Log:
[S02] refine Blobs to simply be immutable Bufs, with similar generic
characteristics
Modified: docs/Perl6/Spec/S02-bits.pod
pugs-comm...@feather.perl6.nl writes:
> Author: lwall
> Log:
> [S03] refine hyper dwimminess to be more like APL, with modular semantics
>
> +(1,2,3) »+» 1 # 2,4,4,6 rhs dwims to (1 xx *).batch(3)
I'd've expected the output to be 2,3,4; is the 2,4,4,6 c
Author: lwall
Date: 2010-06-02 18:51:06 +0200 (Wed, 02 Jun 2010)
New Revision: 31050
Modified:
docs/Perl6/Spec/S03-operators.pod
Log:
[S03] refine hyper dwimminess to be more like APL, with modular semantics
Modified: docs/Perl6/Spec/S03-operators.pod
Author: sorear
Date: 2010-05-28 02:10:37 +0200 (Fri, 28 May 2010)
New Revision: 30878
Modified:
docs/Perl6/Spec/S05-regex.pod
Log:
[S05] clarify :ratchet behavior with input from pmichaud++
Modified: docs/Perl6/Spec/S05-regex.pod
On 22/12/2009 10:22, Moritz Lenz wrote:
Carl MXXsak (via RT) wrote:
This be Rakudo 8dc189.
$ perl6 -e 'multi sub f($a) {}; multi sub f($a) {}; f(42)'
Ambiguous dispatch to multi 'f'. Ambiguous candidates had signatures:
:(Any $a)
:(Any $a)
The definition of two vari
Carl MXXsak (via RT) wrote:
> This be Rakudo 8dc189.
>
> $ perl6 -e 'multi sub f($a) {}; multi sub f($a) {}; f(42)'
> Ambiguous dispatch to multi 'f'. Ambiguous candidates had signatures:
> :(Any $a)
> :(Any $a)
>
> The definition of two variants wit
1 - 100 of 1133 matches
Mail list logo
