On 2003-02-11 at 17:44:08, Mark J. Reed wrote:
> pop @{[@a,@b,@c]}
>
> It creates an anonymous array, then removes the last element, leaving two
> elements in the array - which is irrelevant since the array is
> then discarded completely.
Minor correction: we don&
On 2003-02-11 at 16:52:36, Dave Whipp wrote:
> "Mark J. Reed" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> >
> > On 2003-02-11 at 17:44:08, Mark J. Reed wrote:
> > > pop @{[@a,@b,@c]}
> > >
On 2003-02-12 at 11:07:45, Joseph F. Ryan wrote:
> Meaning that "I think this should be possible, but I'm not
> sure if that syntax is correct, because it would mean that
> the arrayrefs would need to be their own class to allow
> a method to be called on it.
No, they wouldn't, unless I'm missing s
On 2003-03-10 at 18:03:12, Uri Guttman wrote:
> this confuses me. sometimes i want a simple pass by value param which i
> can modify locally in the sub. is this the same as the constant above?
No, that's the same as "is copy".
--
Mark REED| CNN Internet Technology
1 CNN Cente
On 2003-03-11 at 10:12:17, Damian Conway wrote:
> Austin Hastings wrote:
>
> >It is explicitly stated that "is rw" on a slurpy parameter distributes
> >across all the components.
> >
> >Is there some way of differentiating array of const vs. array of rw?
> >
> >That is, creating a hash or array t
On 2003-03-13 at 05:44:09, Damian Conway wrote:
> >2- Yeah! ... umm, are we *paying* you for this?
>
> Not any more. In fact, like Larry and several others on the design team,
> I'm now paying for the privilege of doing it. ;-)
If the TPF isn't supporting you folks anymore, what's the best
way fo
On 2003-06-16 at 17:48:58, Simon Cozens wrote:
> % grep printf cvs/modules/**/*pm | wc -l
> 15
> % grep -v printf cvs/modules/**/*pm | wc -l
> 15360
>
> Well, 0.1% agreed, anyway.
Now, now, that's hardly a fair comparison. Maybe if you grepped for lines
that contain "print" but not "pri
(in addition to whatever specific functionality it
needs) makes sense, IMHO.
.
--
Mark J. Reed
ft.
>
> @@ -246,6 +246,7 @@
> year
> month
> day
> + day-of-month
> day-of-week
> week
> week-year
>
>
--
Mark J. Reed
art, even if Perl 6 has chosen a convention.
>
> On the other hand, I won't complain about a "week-of-year" with a good
> definition of how it handles weeks 0/1, 52/53. End user can choose to
> use it or not. And I'm not too anxious to open up the whole calendar
> choice can of worms.
>
--
Mark J. Reed
wrote:
> On Thu, Jul 15, 2010 at 2:13 PM, Brandon S Allbery KF8NH
> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 7/15/10 12:21 , Mark J. Reed wrote:
>>> By analogy, I'd say week-of-year should work as well.
>>
>> Wasn&
able and then turn around
and talk about modifying them. How about just saying that "A new
C can also be based on an existing C object:" ?
--
Mark J. Reed
> @@ -198,6 +217,9 @@
> Monday of the week in which it occurs, and the time components are all
> set to 0.
>
> +For the convenience of method chaining, C and C return the
> +calling object.
> +
> =head1 Date
>
> C objects are immutable and represent a day without a time component.
> @@ -246,8 +268,6 @@
> $d + 3 # Date.new('2010-12-27')
> 3 + $d # Date.new('2010-12-27')
>
> -As temporal objects are immutable, += -= ... do not work.
> -
> =head1 Additions
>
> Please post errors and feedback to C. If you are making
>
>
--
Mark J. Reed
pecific
behavior, though perhaps it doesn't belong in core.
--
Mark J. Reed
On Wed, Jul 21, 2010 at 12:04 AM, Jon Lang 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
Ok, I find that surprising (and counter to current Rakudo behavior),
but thanks for the correction, and sorry about the misinformation.
On Wednesday, July 21, 2010, Larry Wall wrote:
> On Tue, Jul 20, 2010 at 11:53:27PM -0400, Mark J. Reed wrote:
> : In particular, consider that pi ~~ 0
Strike the "counter to current Rakudo behavior" bit; Rakudo is
behaving as specified in this instance. I must have been
hallucinating.
On Wed, Jul 21, 2010 at 7:33 AM, Mark J. Reed wrote:
> Ok, I find that surprising (and counter to current Rakudo behavior),
> but thanks for the
On Wed, Jul 21, 2010 at 3:55 PM, Darren Duncan wrote:
> Larry Wall wrote:
>>
>> On Tue, Jul 20, 2010 at 11:53:27PM -0400, Mark J. Reed wrote:
>> : In particular, consider that pi ~~ 0..4 is true,
>> : because pi is within the range; but pi ~~ 0...4 is false, becaus
CgkQIn7hlCsL25X2jACeIwN4EBe96dS4WEBm1Ik14dQW
> JNwAoJaASMvMGVickzIgdBDclNM2KhJq
> =9ej6
> -END PGP SIGNATURE-
>
--
Mark J. Reed
x.
Or at least I thought that was the case, but in current Rakudo I
notice that :13(54) is a Num while 69 is an Int.
--
Mark J. Reed
On Wednesday, July 28, 2010, Jon Lang wrote:
> Keep it simple, folks! There are enough corner cases in Perl 6 as
> things stand; we don't need to be introducing more of them if we can
> help it.
Can I get an Amen? Amen!
--
Mark J. Reed
On Wed, Jul 28, 2010 at 2:30 PM, Chris Fields wrote:
> On Jul 28, 2010, at 1:27 PM, Mark J. Reed wrote:
>> Can I get an Amen? Amen!
>> --
>> Mark J. Reed
>
> +1. I'm agnostic ;>
Militant? :) ( http://tinyurl.com/3xjgxnl )
Nothing inherently religious ab
x27;s a keyword [item in array] or specific method
[array.include? item] or function [in_array($item, $array)]...
--
Mark J. Reed
#x27;d tried that and it didn't work.
> Though more efficient would be:
>
>> my @x = 1,2,3; say ?...@x.first(2); say ?...@x.first(4);
> 1
> 0
Ah, perfect. Thanks!
> I still prefer the junction way though. :-)
I love junctions, but it feels like overkill to use them for this. :)
--
Mark J. Reed
> Version: GnuPG v2.0.10 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkxUOJsACgkQIn7hlCsL25WPlwCeJKwKQWDl+qaNbJMyAOcZ5UXf
> R2EAn1AQBqB5hZIFmqymcaqSSGJdx9GJ
> =cmZ6
> -END PGP SIGNATURE-
>
--
Mark J. Reed
ifferent way of specifying a condition
that isn't meant to be compared to the topic, and so doesn't invoke
smartmatching at all: it's just evaluated in Boolean context as-is. I
like the suggestion of "whenever" for that; it has the "no matter
what" sense that goes with ignoring the topic.
-Mark
--
Mark J. Reed
it's not universal, and there are alternatives. Of the ones you
mentioned, I would also probably pick "update" in the general case.
But if we're talking about implementing attribute assignments,
"assign" might be more logical.
Of alternatives you didn't mention, I like "put" - as pithy as "get"
and "set", with plenty of corresponding history (SmallTalk, POSIX,
HTTP,...).
-
Mark J. Reed
x27;t a problem to solve; it's one form
of solution to the problem of maximizing efficiency.
Continuations/fibers and asynchronous event loops are different
solutions to the same problem.
--
Mark J. Reed
But state changes are not undone, so the program can
still behave differently after the continuation is called.
--
Mark J. Reed
arry. Isn't the ":4<222>"
syntax sufficient? Unless you're manipulating a lot of bitstreams in
pairwise increments, I don't see the point. Orthogonality for its own
sake is not very Perlish...
--
Mark J. Reed
on where you place the zero, unless you first convert
> the Instant in a Duration (e.g. seconds since 1 jan 1970)
>
>
> Right. And therefore having to do the conversion explicitly is a good thing
> -- you immediately see which epoch was used.
>
> Cheers,
> Moritz
>
--
Mark J. Reed
either list is
empty. But the self-reference in the definition means it still has to be
computed lazily.
--
Mark J. Reed
xactly matches the output of my iterative Perl 6
> solution
> (http://rosettacode.org/mw/**index.php/Gray_code#Perl_6<http://rosettacode.org/mw/index.php/Gray_code#Perl_6>
> ):
>
> our multi sub infix: ( $x, $y ) { ( $x + $y ) % 2 };
>
Why did you need to define this yourself instead of just using +^ ?
--
Mark J. Reed
e added
> "=" character.
>
> This aids learnability as there's a relatively simple mnemonic, where nearly
> any given operator foo is non-mutating, but by adding an "=" to it you get a
> mutating variant, so people can look for the "=" to know if it would mutate.
> The comparison ops are the rare exception to the rule.
>
> -- Darren Duncan
>
--
Mark J. Reed
l things are spelled with
>> underscores, while we reserve the minus character for user-space code.
>> Try grepping the specs for identifiers of built-ins that have a minus in
>> it -- I didn't find any in a quick search.
>>
>>
>>> And why is this entire message written in questions?
>> Is it? I'm afraid I don't understand what you mean.
>>
>> See
>>
https://github.com/perl6/specs/commit/a7cfe02002f665c120cf4b735919779820194757
>> maybe it's a charset problem on your machine, or something.
>>
>> Cheers,
>> Moritz
>
--
Mark J. Reed
g adjectives to nouns,
> while hyphens separate distinct words. One could argue that is not
> inconsistent.
>
> On 8/23/11, Patrick R. Michaud wrote:
>> On Tue, Aug 23, 2011 at 05:36:27PM +0200, Damian Conway wrote:
>>> And I'd like there to be a more consistent approach than that
>>> (though I don't really care what it actually is).
>>
>> +1 to consistency.
>>
>> Pm
>>
>
--
Mark J. Reed
401 - 436 of 436 matches
Mail list logo
