Author: tene
Date: 2010-07-20 20:35:35 +0200 (Tue, 20 Jul 2010)
New Revision: 31773
Modified:
docs/Perl6/Spec/S03-operators.pod
Log:
Fix minor typo
Modified: docs/Perl6/Spec/S03-operators.pod
===
---
Author: dolmen
Date: 2010-07-20 23:51:26 +0200 (Tue, 20 Jul 2010)
New Revision: 31776
Modified:
docs/Perl6/Spec/S32-setting-library/Temporal.pod
Log:
[S32/Temporal] Make DateTime immutable.
Modified: docs/Perl6/Spec/S32-setting-library/Temporal.pod
On Tue, Jul 20, 2010 at 5:51 PM, pugs-comm...@feather.perl6.nl wrote:
+CDateTime objects are immutables.
+
I think just the adjective works better here (are immutable)... but
more to the point:
+A CDateTime can also be created by modifying an existing object:
It's mildly confusing to say
Author: Kodi
Date: 2010-07-21 02:12:24 +0200 (Wed, 21 Jul 2010)
New Revision: 31777
Modified:
docs/Perl6/Spec/S32-setting-library/Temporal.pod
Log:
[S32/Temporal] Reverted DateTime back to being mutable. I think we ought to
make a big change like this only after reaching some kind of
pugs-comm...@feather.perl6.nl wrote:
Modified:
docs/Perl6/Spec/S32-setting-library/Temporal.pod
Log:
[S32/Temporal] Reverted DateTime back to being mutable. I think we ought to
make a big change like this only after reaching some kind of consensus to do
so, not least because I just
On Tue, Jul 20, 2010 at 7:31 PM, Aaron Sherman a...@ajs.com wrote:
2) We deny that a range whose LHS is larger than its RHS makes sense, but
we also don't provide an easy way to construct such ranges lazily otherwise.
This would be annoying only, but then we have declared that ranges are the
Solomon Foster wrote:
Ranges haven't been intended to be the right way to construct basic
loops for some time now. That's what the ... series operator is
for.
for 1e10 ... 1 - $i {
# whatever
}
is lazy by the spec, and in fact is lazy and fully functional in
Rakudo.
On Tue, Jul 20, 2010 at 10:00 PM, Jon Lang datawea...@gmail.com wrote:
Solomon Foster wrote:
Ranges haven't been intended to be the right way to construct basic
loops for some time now. That's what the ... series operator is
for.
for 1e10 ... 1 - $i {
# whatever
}
is lazy
Well, then, let's start building that consensus. I firmly believe
DateTimes should definitely be value types, immutable. Otherwise you
can't use them for hash keys, for one thing.
Note that timestamps in Perl have always been values; it's just that
they used to be specifically integers, whose
Side note: you could get around some of the problems, below, but in order to
do so, you would have to exhaustively express all of Unicode using the Str
builtin module's RANGES constant. In fact, as it is now, it defines ASCII
lowercase, but doesn't define Latin lowercase. Presumably because doing
Approaching this with the notion firmly in mind that infix:.. is
supposed to be used for matching ranges while infix:... should be
used to generate series:
Aaron Sherman wrote:
Walk with me a bit, and let's explore the concept of intuitive character
ranges? This was my suggestion, which seems
Aaron Sherman wrote:
So, what's the intention of the range operator, then? Is it just there to
offer backward compatibility with Perl 5? Is it a vestige that should be
removed so that we can Huffman ... down to ..?
I'm not trying to be difficult, here, I just never knew that ... could
Mark J. Reed wrote:
Perhaps the syllabic kana could be the integer analogs, and what you
get when you iterate over the range using ..., while the modifier kana
would not be generated by the series ア ... ヴ but would be considered
in the range ア .. ヴ? I wouldn't object to such script-specific
On Wed, Jul 21, 2010 at 12:04 AM, Jon Lang datawea...@gmail.com wrote:
Mark J. Reed wrote:
Perhaps the syllabic kana could be the integer analogs, and what you
get when you iterate over the range using ..., while the modifier kana
would not be generated by the series ア ... ヴ but would be
OK, there's a lot here and my head is swimming, so let me re-consolidate and
re-state (BTW: thanks Jon, you've really helped me understand, here).
1) The spec is somewhat vague, but the proposal that I made for single
characters is not an unreasonable interpretation of what's there. Thus, we
Aaron Sherman wrote:
2) The spec doesn't put this information anywhere near the definition of the
range operator. Perhaps we can make a note? This was a source of confusion
for me.
My impression is that a Range primarily defines an interval in terms of 2
endpoint values such that it defines a
Darren Duncan wrote:
specific, the generic eqv operator, or before etc would have to be
Correction, I meant to say cmp, not eqv, here. -- Darren Duncan
17 matches
Mail list logo
