't finish, yet
>
> --
> Will "Coke" Coleda
>
--
Mark J. Reed
't finish, yet
>
> --
> Will "Coke" Coleda
>
--
Mark J. Reed
.. vs ... stuff is going to be a continuous source of confusion, I fear.
On Friday, July 30, 2010, Patrick R. Michaud wrote:
> On Fri, Jul 30, 2010 at 01:22:02PM -0400, Mark J. Reed wrote:
>> What is assigning a Range to an array supposed to do? Give you an
>> array of one i
> 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
; Method 'foo' not found for invocant of class 'A'
>
> $ perl6 -e 'Any.foo'
> Method 'foo' not found for invocant of class 'Any'
>
> $ perl6 --version
> This is perl6 version 2011.09-35-g545638a built on parrot 3.8.0 revision
RELEASE_3_8_0-
> 120-gb7e7400
>
>
> closable with tests.
>
> --
> Will "Coke" Coleda
>
--
Mark J. Reed
501 - 516 of 516 matches
Mail list logo
