now very manageable. Concurrency is
bordering on trivial. My application libraries/APIs are now in reach without
much effort. The more I read/experiment, the better the story gets. Keep your
steam up and press on. Worth it!
Thanks,
Mark
-Original Message-
From: Steve Mynott [mailto:st
-
Regards,
MarkOv
----
Mark Overmeer MScMARKOV Solutions
m...@overmeer.net soluti...@overmeer.net
http://Mark.Overmeer.net http://solutions.overmeer.net
Hi Patrick, thank you for your thoughts. I needed a bit more time
for the response ;-)
* Patrick R. Michaud (pmich...@pobox.com) [151013 01:05]:
> On Tue, Oct 13, 2015 at 12:32:01AM +0200, Mark Overmeer wrote:
> > Yes, that what I started realizing when I saw all the pain Perl
gards,
MarkOv
----
Mark Overmeer MScMARKOV Solutions
m...@overmeer.net soluti...@overmeer.net
http://Mark.Overmeer.net http://solutions.overmeer.net
parameter", "undef
value means illegal value" (:D), "undef value is allowed". For my coding
style, the first case is usually true. I am not sure, but probably
Perl6 makes do difference between missing existence and undefinedness
of named parameters... where hashes and XM
is dull facts. Is that an old-fashioned, traditional idea
to be abandoned?
--
Regards,
MarkOv
Mark Overmeer MScMARKOV Solutions
m...@overmeer.net soluti...@overmeer.net
http://Mark.Overmeer.net http://solutions.overmeer.net
n course ;-)
> > . :D looks really ugly, don't you think? Try to explain to students
> > to add this smiley everywhere.
>
> It's not uglier than a 'die "Must be defined" unless defined $x'
Much too expensive in Perl5.
--
explain to students
to add this smiley everywhere.
Can someone explain this to me? (Or point me to the correct place)
--
Thanks in advance
MarkOv
Mark Overmeer MScMARKO
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
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
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
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
either list is
empty. But the self-reference in the definition means it still has to be
computed lazily.
--
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
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
But state changes are not undone, so the program can
still behave differently after the continuation is called.
--
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
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
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
> 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
#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
x27;s a keyword [item in array] or specific method
[array.include? item] or function [in_array($item, $array)]...
--
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
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
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
CgkQIn7hlCsL25X2jACeIwN4EBe96dS4WEBm1Ik14dQW
> JNwAoJaASMvMGVickzIgdBDclNM2KhJq
> =9ej6
> -END PGP SIGNATURE-
>
--
Mark J. Reed
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
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
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
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
pecific
behavior, though perhaps it doesn't belong in core.
--
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
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
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&
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
ft.
>
> @@ -246,6 +246,7 @@
> year
> month
> day
> + day-of-month
> day-of-week
> week
> week-year
>
>
--
Mark J. Reed
(in addition to whatever specific functionality it
needs) makes sense, IMHO.
.
--
Mark J. Reed
error reminding Perl 5 users to use dot instead. (The "pointy block"
use of C<< -> >> in Perl 5 requires preceding whitespace when the arrow
^
Shouldn't that read "in Perl 6"?
--
Mark J. Reed
r, but U+FEFF is
perfectly cromulent, if deprecated: it's the ZERO-WIDTH NON-BREAKING
SPACE (U+200C ZERO WIDTH NON-JOINER is the modern replacement). The
choice of byte-order mark protocol was well-considered: if U+FEFFis
interpreted as a character instead of a BOM, it's a pretty ha
letting CPAN/etc be the language, especially where complexity comes in.
>
> It also means that temporal modules can be bundled with Perl, but that is a
> choice made by the Perl packagers, not the Perl core, same as deciding what
> templating or networking or database or whatever modules to bundle.
>
>
>
--
Mark J. Reed
> propose it'd be about 365.25 Gregorian days (although I'd much prefer an
> international standard to my Indo-European ways :) ).
>
> Overall, I think you have a great idea. As long as the filters are
> implemented simply, I think it will prove to be the best option.
>
> --
> Don't Panic!
>
>
--
Mark J. Reed
plementations of methodicals in terms of other
> > language
> > > features. First, it is possible to treat methodicals as ordinary
> methods
> > > (monkey typing under the hood), but with generated names; the true name
> > is
> > > bound to the program name only within the correct scope. If possible,
> > the
> > > methods should be treated as anonymous, accessible only though an
> opaque
> > name
> > > object. Care must be taken to prevent incorrect exposure of private
> > fields and
> > > methods.
> > >
> > > Alternatively, a methodical can be desugared to a multi sub with the
> same
> > scope
> > > as the methodical itself, changing statically named method calls into
> > calls to
> > > the methodical. This gives reflection invisibility and privacy for
> free,
> > but
> > > may require more work to get the multi call semantics exactly right.
> > >
> > > Thoughts?
> > >
> > > -Stefan
> > >
> > > -BEGIN PGP SIGNATURE-
> > > Version: GnuPG v1.4.9 (GNU/Linux)
> > >
> > > iEYEARECAAYFAkvOpjcACgkQFBz7OZ2P+dKJ4wCfUpWUDv2/PqYUF1k0hsYaiAns
> > > HFAAn2K5SfcJnGq5xk1PIy0QG69LMrwR
> > > =uvrz
> > > -END PGP SIGNATURE-
> > >
> > >
> >
>
--
Mark J. Reed
se $date - $start_of_epoch to
> obtain a day count starting from a fix epoch
--
Mark J. Reed
efit of a Date object
over a DateTime object that simply has its time fields zeroed, which is
flexibility. The latter is still by implication tied to a specific swath of
spacetime (e.g. midnight to midnight in some time zone), whereas the former
is free to refer to whatever the human date designation can.
--
Mark J. Reed
"
On Friday, April 16, 2010, Mark J. Reed wrote:
> or at least, Date should have a method that returns it's value as
> pairs suitable for passing to DateTime.new.
Obviously that should be "its value". Thank you, iPhone, for thinking
you know better than I how to
etics on C objects, two more
> +methods are exposed:
> +
> + $d.daycount
> + Date.new-from-daycount(Int $daycount)
> +
> +The C method returns the difference of number of days between the
> +current object and an arbitrary start of epoch. This epoch is arbitrary and
> +implementation dependent, and is even allowed to change between invocations
> of
> +the same program. The C constructor creates a new C
> +object with a given daycount.
> +
> =head1 Additions
>
> Please post errors and feedback to C. If you are making
>
>
--
Mark J. Reed
, it may have both of those, with the
difference you indicated. It's all about choosing the right name. :)
Whatever you call it, it's a valuable function, I'm just arguing that it's
not "truncation" unless you're talking about a calendar where you number
Sunday-based weeks from a given epoch.
--
Mark J. Reed
creates a dynamic scope for an srand: e.g. "temp srand { ... };"
>
That seems like a reasonable solution.
--
Mark J. Reed
ccepts all of these as named arguments, allowing several values to be
> set at once:
>
> @@ -175,12 +175,12 @@
> values, and an exception is thrown if the result isn't a sensible date
> and time.
>
> -If you use the C public accessor to adjust the time zone, the
> +If you use the C public accessor to adjust the time zone, the
> local time zone is adjusted accordingly:
>
> my $dt = DateTime.new('2005-02-01T15:00:00+0900');
> say $dt.hour; # 15
> - $dt.time_zone = '+0600';
> + $dt.timezone = '+0600';
> say $dt.hour; # 12
>
> The C method allows you to "clear" a number of time values
>
>
--
Mark J. Reed
On Mon, Apr 12, 2010 at 6:38 AM, Mark J. Reed wrote:
> I think that having a standard, minimal API for this defined in core as a
>> Date role would be ideal.
>
>
> Agreed. In fact, I'd like to see DateTime be defined explicitly as a
> superset (subrole) of Date, wi
icitly as a
superset (subrole) of Date, with a method for extracting just the Date
portion built in to DateTime.
--
Mark J. Reed
antage of this scheme that I can think of.
> The disadvantages, which affect everyone, are many and bigger:
> search/replace headaches, novice confusion, adding to Perl's "syntax
> infamy," etc.
>
> (Besides, I'm sure you can Acme::-up something that implements this
> scheme in Perl 6 for your own devious purposes anyway… ;)
>
> -John
>
--
Mark J. Reed
antage of this scheme that I can think of.
> The disadvantages, which affect everyone, are many and bigger:
> search/replace headaches, novice confusion, adding to Perl's "syntax
> infamy," etc.
>
> (Besides, I'm sure you can Acme::-up something that implements this
> scheme in Perl 6 for your own devious purposes anyway… ;)
>
> -John
>
--
Mark J. Reed
ead of either supress it
> > or use an underscore...
>
> These nuances are exactly what will be lost on people who see classes
> that use both underscores and hyphens in their method names.
>
> -John
>
--
Mark J. Reed
d to an integer.
>
>The C method returns the C object
>
> (i.e. only C<.from_epoch()> actually uses underscore).
>
> Oh, and the optional C<:timezone> argument to C<.new()> should probably
> become C<:time-zone> for consistency with the C<.time-zone()> method
> (or, preferably, we should jut bite the bullet and go with C
> throughout).
>
> Damian
>
--
Mark J. Reed
sonal preferences; I greatly prefer dashes in
> almost all of the code I write. But I acknowledge that most of the
> programmers out there seem to expect underscores -- and also, the aim
> was to produce a small delta from CPAN's DateTime and not change
> around things ad lib.
>
> // Carl
>
--
Mark J. Reed
stead of May 31.
On Friday, April 9, 2010, Mark Biggar wrote:
> On 4/9/2010 4:53 AM, Moritz Lenz wrote:
>
> Am 09.04.2010 13:34, schrieb Mark J. Reed:
>
> The date still corresponds to an actual day. If I set it to Feb 31, I
> should get back Mar 2 or 3 depending on the year. Wh
On 4/9/2010 4:53 AM, Moritz Lenz wrote:
Am 09.04.2010 13:34, schrieb Mark J. Reed:
The date still corresponds to an actual day. If I set it to Feb 31, I
should get back Mar 2 or 3 depending on the year. While I'm having
trouble thinking of a good specific example, it's a capability
s, and such. I believe it's Python's datetime module that
has unchecked_* methods for the purpose.
Maybe in p6 the setters could do the correction if the exception is resumed?
On Friday, April 9, 2010, Carl Mäsak wrote:
> Mark (>):
>> I do think that an "unchecked&
ptime
> * DateTime::Duration
> * ops: $dt + $dur, $dt - $dur, $dt - $dt
>
> Expect these in the next few days or so.
>
> // Carl
>
--
Mark J. Reed
wouldn't mind making the change. Though maybe we
> should take a step backward and just remove :to altogether on
> the grounds that it doesn't belong, and is more confusing than useful.
> :)
>
> // Carl
>
--
Mark J. Reed
On Sat, Apr 3, 2010 at 2:18 PM, wrote:
> [P6 Spec] completely changed S32::Temporal
>
What motivated these changes?
> +Time is just a jumbled iTem.
>
iTem?
> +=item * 12hour
>
> +=item * 24hour
I don't like using strings for these. Feels like they should be symbols,
but they they can't s
Use <{...}>. as the string returned is reinterpreted as a regex, if it consists
of the single quoted string then it's a literal, but you must include the
single quotes in the result returned. E.g.,
<{ my $x = funct($a, $b, $c); "'$x'";}>
Mark
<@foo> / -- A list of ||-style alternations of things to be
> compiled into Regexes (unless they already are)
> / <{ ... }> / -- Result of capture is interpolated as a Regex,
> compiling if necessary
> / / -- Unchanged
> / { ... } / -- Capture is merely executed, but not interpolated.
> (Unchanged)
>
--
Mark J. Reed
ncements on p6l is about as relevant as having Perl 5 release
>> announcements on mailing lists for individual Perl modules, or DBI release
>> announcements on the DBIx-Class list, say. -- Darren Duncan
>>
>
> Darren -
>
> FYI, Copenhagen was a Rakudo release, not a parrot release.
>
> Regards.
>
> --
> Will "Coke" Coleda
>
--
Mark J. Reed
dered in place of discrete.
In CSland, I suspect "atomic" is too strongly associated with
operations to be applied to a data type that has nothing to do with
multithreading or transactional integrity.
--
Mark J. Reed
Oh, wow. I was just asking about the spec; didn't know this stuff
already worked. Rakudos to the team! :)
On Wed, Mar 10, 2010 at 9:18 AM, Carl Mäsak wrote:
> Mark (>):
>> Does the unpacking participate in dispatch? If a Hash comes in as $t
>> with no 'left
be impracticalities in just 'adding pattern matching'.
>
> Scala case classes: http://www.scala-lang.org/node/107 or
> http://programming-scala.labs.oreilly.com/ch06.html#CaseClasses
>
>
--
Mark J. Reed
| Because the Creator is, |
> | E-mail: wayl...@wayland.id.au | I am |
> -
>
> BEGIN GEEK CODE BLOCK
> Version 3.12
> GCS d+++ s+: a- C++$ U+++$ P+++$ L+++ E- W+ N+ w--- V- PE(+) Y+>++ PGP->+++
> R(+) !tv b++ DI D G+ e++> h! y-
> -END GEEK CODE BLOCK-
>
--
Mark J. Reed
-07#i_2073717
>
> I'm not sure what exactly the repercussions of doing attribute
> initialization with 'is ref' are apart from that. Brandon, if your
> oblique reference to Algol 68 meant something more than what I
> uncovered above, feel free to enrich the discussion by sharing what
> you know about the possible consequences of spec'ing things this way.
>
> Now if you'll excuse me, I'll go back to doing little to make the
> compiler writers' task easy. :-P
>
> // Carl
>
--
Mark J. Reed
On Wed, Mar 3, 2010 at 6:26 PM, Darren Duncan wrote:
> Mark J. Reed wrote:
>>
>> Doesn't unspace work for this?
>
> It would seem that S02 says otherwise:
>
> Although we say that the unspace hides the whitespace from the parser, it
> does not hide whit
d Perl 6 support someone wanting to write a numeric literal that is
> so long that they would want to split it over multiple source code lines,
> such as a very long integer that takes a few hundred or thousand characters
> to write, or an X/Y rational composed of 2 such integers, but the
On Wed, Feb 24, 2010 at 1:12 AM, Steve Allen wrote:
> Hello Mark Reed and Larry Wall
Brought back to the whole list; Larry and I were hardly the only two
folks involved in this discussion.
> On Feb 23, 6:35 am, markjr...@gmail.com ("Mark J. Reed") wrote:
>> OK, this
a count of atomic seconds,
great. That, however, is not TAI. UTC and TAI and the proposed
leap-second-free UTC-replacement "TI" all tick at the same rate and at
the same time, and you can devise any number of time scales that do
likewise, differing only in the labels.
--
Mark J. Reed
uts and outputs of Temporal are UTC, then Perl
is using UTC, not TAI. Is it TAI internally? Well if it's
manipulating years, months, days, hours, and minutes as their TAI
values, then yes, but if it's just working with an absolute count of
atomic seconds, then there's no reason to say that it's TAI vs. UTC,
because at that level, they completely agree with each other.
--
Mark J. Reed
above, the
labels will be UTC - which they pretty much have to be since that's
what humans use - then Perl6 is using UTC, not TAI. It's just using
*real* UTC, not POSIX's broken idea of it that claims 24 seconds out
of the past 40 years never happened.
--
Mark J. Reed
On Mon, Feb 22, 2010 at 1:13 PM, Daniel Ruoso wrote:
> Em Dom, 2010-02-21 às 21:28 -0800, Larry Wall escreveu:
>> On Sat, Feb 20, 2010 at 10:39:20AM -0500, Mark J. Reed wrote:
>> : I just want to know what Perl 6 time zero is.
>> Well, there's no such thing as time 0 in
On Mon, Feb 22, 2010 at 1:31 PM, Mark J. Reed wrote:
> Not according to S0, which says that an Instant will numify to the
^
S02.
> number of TAI seconds since "the TAI epoch". That's not opaque.
--
Mark J. Reed
lbery [solaris,freebsd,perl,pugs,haskell] allb...@kf8nh.com
> system administrator [openafs,heimdal,too many hats] allb...@ece.cmu.edu
> electrical and computer engineering, carnegie mellon university KF8NH
>
>
>
--
Mark J. Reed
ich was midnight UT on November 17, 1858 (the epoch of VMS
system time).
I note that Rakudo currently uses the time_t value directly. I think 1
Jan 1970 is a poor choice of epoch for TAI time; having time values so
close to but not the same as time_t values would create undue
confusion.
--
Mark J. Reed
On Wed, Feb 17, 2010 at 7:32 PM, Carl Mäsak
wrote:
> my @a = (4...^5); say @a.perl # should be 4 3 2 1 0 1 2 3 4, according to
> TimToady
That's 4 ... ^5, right? If so, I don't see how you get that. I'd
expect (4,0,1,2,3,4), without the countdown between 4 and 0.
--
Mark J. Reed
rmeer.net/oodoc/html/jump.cgi?OODoc_Parser_Markov&62
--
MarkOv
----
Mark Overmeer MScMARKOV Solutions
m...@overmeer.net soluti...@over
"it"s with different antecedents there. Might want to
toss in a noun or two.
--
Mark J. Reed
cribes tr/// in terms of the .trans function, a handsome but
> very different beast. Specifically, it doesn't seem to have a "scalar
> context", with which one could count things.
>
--
Mark J. Reed
(In Windows: perl -ple "$_=eval" )
>
> Enter the command `exit` to end the session.
>
>
> --
> Just my 0.0002 million dollars worth,
> Shawn
>
> Programming is as much about organization and communication
> as it is about coding.
>
> I like Perl; it's the only language where you can bless your
> thingy.
>
--
Mark J. Reed
takes us back to Jon's branch of the thread: it would be nice to
be able to declare such an override in a general way that will apply
to any such composition that doesn't otherwise override it locally.
But what should that declaration look like?
--
Mark J. Reed
re a "method space" for arbitrary combinations of roles,
a sort of meta-role. It's an odd duck, but it does sort of fall out
of the multiple-dispatch semantics, which already let you base
implementation chioce on arbitrary combinations of roles...
--
Mark J. Reed
bout other roles which aren't composed into the current role's
implementations.
Mark.
it is an error
> +Variables with native types do not support undefinedness, it is an error
> to assign an undefined value to them:
>
> my int $y = undef;# dies
>
>
--
Mark J. Reed
Duration objects.
> +The following attribute is declared:
>
> =over
>
> @@ -226,6 +227,20 @@
>
> =back
>
> +The following methods provide additional information
> +
> +=over
> +
> +=item week-of-year
> +
> +=item day-of-week
> +
> +=item week-of-month
> +
> +=item year-of-week
> +
> +=back
> +
> =head2 Gregorian::Duration
>
> The gregorian Duration declares the following attributes.
>
>
--
Mark J. Reed
I thought I recalled seeing that the new convention was .p6m, .p6l,
etc. I guess that idea was abandoned?
--
Mark J. Reed
t; $b?" is a common test, and so should be short. I'd rather require you
> to force it into list context if your goal is to test for set
> membership. In fact, that might be a clean way of handling its dual
> nature: in item context, it behaves as a Range object; in list
> context, it behaves as the RangeIterator. So:
>
> 2.5 ~~ 1..5 # true: equivalent to "2.5 ~~ 1 <= $_ <= 5".
> 2.5 ~~ @(1..5) # false: equivalent to "2.5 ~~ (1, 2, 3, 4, 5)".
>
> Incidently, this first example is why I think that Range is intimately
> related to the various order-related operators, and in particular
> before and after: its most common use outside of generating sequential
> lists is to provide a shorthand for "$min before $_ before $max" and
> similar range-testing expressions.
>
> --
> Jonathan "Dataweaver" Lang
>
--
Sent from my mobile device
Mark J. Reed
range.interval
>
> I'm new in town though, so I'll happily admit that I don't know the full
> implications of such a change. Having context-insensitive Ranges DWIM's
> better to me, but DWIMery, like beauty, is clearly in the eye of the
> beholder! :)
>
> Cheers,
> --
> smuj
>
--
Sent from my mobile device
Mark J. Reed
denominator. But for
>> floats I would only see the interval as reasonably clear. Even a step
>> of 1 is coming with some problems, because an increment of 1 does not
>> have any effect on floating point numbers like 1.03e300 or so.
> Yes. Exactly my point. By the way, do we
the rectangle formed by z1 and
z2, which is a viable (if nonlinear) definition of "between". You can
only get a Boolean answer, but it's a valid question.
That's just nitpicking, though. It's perfectly reasonable to fail()
if someone tries to construct a Range/Series/Interval out of Complex
numbers. We can use a different class for complex rectangles if we
need them.
--
Mark J. Reed
named
> args and proto-objects.
> (2009-08-19 12:05:29) jnthn: It passes the relevant bits to each BUILD.
> (2009-08-19 12:05:42) moritz_: jnthn: right now, yes. We were discussing
> possible enhancements
> (2009-08-19 12:06:09) __ash__: do i need anything else in the subject
> other than [PATCH]? and is it an attachment or the contents in the email?
> (2009-08-19 12:06:11) r0bby left the room (quit: Read error: 104
> (Connection reset by peer)).
> (2009-08-19 12:06:16) r0bby [n=wakaw...@guifications/user/r0bby] entered
> the room.
> (2009-08-19 12:06:30) masak: Kentrak: only the other day, I found out
> that you can easily create a new() multimethod which does delegation
> using callsame(|$args) or nextsame(|$args). that might be what you want.
> (2009-08-19 12:06:36) Kentrak: jnthn: yes, aware of that, looking for a
> way to not have to redefine multiple pieces to accomplish what I think
> should be a simple feat, defining an initializer with custom params
>
> --
>
> -Kevan Benson
> -A-1 Networks
>
--
Sent from my mobile device
Mark J. Reed
nternally. What we should have, though, is a standard way to
> represent the types in Perl so that users know how to deal with them.
> I think roles are the obvious choice: if the OS tells you that a file
> is HTML, then $file would do IO::Datatype::HTML, which means in turn
> it would also do IO::Datatype::Plaintext, and so on.
>
> Of course, if the OS tells you you've got a file that does
> IO::Datatype::Illudium-phosdex, and you want to *do* something with
> it, you'll need a module that knows what to do with that kind of
> file. Perl by itself knows only how to treat it as a string of raw
> bytes. Well, or as plain text. So you can treat your HTML file as
> plain text, or you can use HTML::Doc::Tree and treat it as something
> fancier.
>
>
> -David
>
>
--
Sent from my mobile device
Mark J. Reed
, then chdir(), then exec()
- but in Windows it may be trickier.
--
Mark J. Reed
:).
>
>
> -
> | Name: Tim Nelson | Because the Creator is,|
> | E-mail: wayl...@wayland.id.au| I am |
> -
>
> BEGIN GEEK CODE BLOCK
> Version 3.12
> GCS d+++ s+: a- C++$ U+++$ P+++$ L+++ E- W+ N+ w--- V-
> PE(+) Y+>++ PGP->+++ R(+) !tv b++ DI D G+ e++> h! y-
> -END GEEK CODE BLOCK-
>
>
--
Sent from my mobile device
Mark J. Reed
not exported by default, so
$ENV{UID} in Perl should be unset. Try your experiments without
exporting UID.
In any case, %ENV isn't readonly in Perl. But neither are the contents
of %ENV managed by Perl - just inherited from the parent process.
--
Mark J. Reed
1 - 100 of 767 matches
Mail list logo
