the parsing.
That's a good thing. It doesn't work so well with text-substitution,
though. Hence, I would argue it should be disallowed.
Rob
behalf, such as if when
> pair of classes is hidden behind a second pair of classes that
> mediate access to them.
>
> What are some best practices here that can be used by anyone faced by
> a similar problem?
>
> -- Darren Duncan
>
[snip]
In Perl5, I would think the easiest solution would be to "trick" the
base Document class into using the right Node class.
1) Load Node.
2) Rename Node to Node::Base
3) Create your Node, subclassing Node::Base
4) Load Document
5) Rename Document to Document::Base
6) Create your Document, subclassing Document::Base
Something along the lines of:
package Node::Mine;
use Node;
*Node::Base = *Node;
delete $main::{Node};
package Node;
use base 'Node::Base';
etc.
So, I figure that with packages being a lot simpler to work with in
P6, that should be a lot easier to handle. Especially given that
packages and modules are now first-class.
Rob
nrelated distros beneath it. And, Tree is
owned by someone else, but that person hasn't updated Tree in 6 years.
And, Tree::Binary is owned by the same guy who owns Tree::Simple.
How is that going to work in P6? (For the record, I still haven't
figured out what I'm going to do yet. Check Perlmonks for the SOPW in
a few minutes.)
Rob
e DFERRANCE namespace? What on
earth does the name DFERRANCE provide, except for an additional layer
of confusion.
> Anyways, I don't like the idea of people being able to upload
> identically named modules to CPAN. I think that's a very bad idea. See
> Rob Kinyon's message.
that if you want to truly clean off the cruft, you have
to approach with a completely open mind. That open mind is going to
piss off a lot of people and you will never do everything you were
hoping to do, but the end product will be better off for it. You'll
never reach the moon unless you shoot for the stars.
Rob
e other 90%" you refer to. They're not going to care one
way or the other. And, if they do, /usr/local/bin/perl won't suddenly
disappear like Cindarella at the ball, you know.
Rob
Personally, I plan on using every single Latin-1 operator I am
given access to. All the cool kids will ...
Rob
. Saying you cannot get a tool you need
loaded on your machine is, essentially, saying that you cannot play
corporate politics. I'm assuming you can, which means this is a straw
man.
Rob
editor cannot handle the charset? That's
like suggesting that operating systems should all be bootable from a
single floppy because not everyone has access to a CD drive.
Rob
ust clear some of the cobwebs and provide a truly
clean interface.
Rob
#x27;t 3am on Sunday when trying to fix a borked /etc ...
Huh!
Rob
Feh - I really need to get on gmail's case for providing a keystroke
for "Reply to All".
Rob
-- Forwarded message --
From: Nate Wiger <[EMAIL PROTECTED]>
Date: Oct 21, 2005 2:38 PM
Subject: Re: $1 change issues [was Re: syntax for accessing multiple
versions
Does TYE's Algorithm::Loops's mapcar() provide the basic functionality
of what you're looking for?
Rob
On 10/21/05, Mark Reed <[EMAIL PROTECTED]> wrote:
> Is there a CPAN module which provides the functionality of ¥/zip() for
> Perl5? I don't see anything ob
ognizes λ in literatures, but actually write "lambda" and
> "\" respectively
> in everyday coding.
Isn't this starting to be the question of why we have the Unicode
operators instead of just functions? Would it be possible to have a
function be infix?
Rob
would also be really
nice. DBI being native P6 would be good. DBD's being roles that a DBI
object does would be really nice.
Rob
On 10/24/05, Nate Wiger <[EMAIL PROTECTED]> wrote:
> Joshua Gatcomb wrote:
> > On 10/24/05, Juerd <[EMAIL PROTECTED]> wrote:
> >
> Feel free to add your own, or fears you heard about!
> >
> > FEAR: The Perl6 process is driving away too many good developers
> >
> > FEAR: Perl6 will not be as por
~= "!"; # "bar foo fopbar foo fop!"
> }
>
> Especially bare ++ would be useful, I think.
Did you post this specifically to anti-address the fear that P6 will
be more line-noise-ish than P5? :-p
Rob
o allowing
my class T := sometype();
So, what happens when stupid me names a class "class" through
symbol-table craziness?
Rob
p5
> >
> > paradox. Many people don't find perl5 inaccessible at all
>
> Who? Do you know anybody who hacks the regex engine?
japhy. Though, granted, he's on a whole new level of insanity.
Rob
(Unless, of course, it breaks the rules and
> does crazy stuff, in which case anything goes)
Is this better expressed as side-effect-free programming or loose
coupling/tight cohesion?
Rob
t indivisible thing there is, then the things
that go about being its definition are the quarks.
> Anyway, if my "class" turns into "type" or something else, maybe I
> can be persuaded to go with ^T instead of ¢T.
Q(T) ? :-)
Rob
scribe in the paper.
This might dovetail quite nicely into the discussion of how types are
now sets instead of junctions. Objects are now a junction of the
various kinds that were used to create it. Thus, boxed types are now
almost trivial to implement ... ?
Rob
all of this? I hope it's not
through repeated eigenclasses (or whatever they're called this week)
... that just sounds too heavy.
2) Isn't Dog|Cat kinda declaring a kind? Thus, can't you say "my
Dog|Cat $catdog;" and be talking about a kind? I would think that a
"named kind" is just a role ...
3) Aren't classes mutable and roles immutable by default only? Or has
this changed?
Rob
to create immutable
classes? Given that roles and classes now seem to differ only in their
mutability, I can't see a reason why I would use class as my default
object definer. I would prefer to use roles as they're closed by
default, leaving "class" to be my powertool, if I need the power.
Rob
On 10/26/05, chromatic <[EMAIL PROTECTED]> wrote:
> On Wed, 2005-10-26 at 20:29 -0400, Rob Kinyon wrote:
>
> > I would prefer to use roles as they're closed by default, leaving
> > "class" to be my powertool, if I need the power.
>
> I don't unde
n other words, it can cache all the method
lookups at compile-time. That's a substantial savings. If they're open
classes, the runtime has to throw out all the cached lookups the
moment any of the classes upstream are modified.
Plus, the argument is a straw man. Instead of:
class Some::Class is also {
}
you would do:
class My::Version {
does Some::Class;
}
Problem solved.
Rob
On 10/26/05, Larry Wall <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 26, 2005 at 07:35:05PM -0700, chromatic wrote:
> : On Wed, 2005-10-26 at 21:58 -0400, Rob Kinyon wrote:
> :
> : > Plus, the argument is a straw man. Instead of:
> : >
> : > class Some::Class is a
ou say something
"won't play in Peoria", you're saying that it's unlikely to be
accepted by the masses.
Rob
On 10/27/05, Larry Wall <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 27, 2005 at 05:37:13AM -0400, Rob Kinyon wrote:
> : Will I be able to do something like:
> :
> : package Foo;
>
> Hmm, you just started in Perl 5 mode.
>
> : $*VERSION = 1.3.2;
>
> Perl 5 would
> But IMHO the reduction in typing for this relatively minor issue is not
> really worth the surprise to newbies at seeing operandless operators.
AMEN!
Rob
vate concept that C++
has. (I don't agree with the protected concept, but private vs. public
is good.)
Doing it any other way leads to the following: if A does rA and B isa
A and B defines an attribute that conflicts with the one provided by
rA, how on earth is that supposed to be detected? Especially given
that the inheritance tree of a class can be modified at runtime.
Rob
d on the fact that classA does
roleAB means something in terms of the functionality that classA
provides to me. I don't want it to be a glorified can() check. That
does no-one any good.
Rob
ll be some sugar to allow #1 to be its own syntax, but it
should be viewed as a #2.
Rob
On 11/1/05, Jonathan Lang <[EMAIL PROTECTED]> wrote:
> Rob Kinyon wrote:
> > > 1. choose one of a set of available methods to call its own.
> > > 2. create a version of its own.
> > > 3. pass the buck.
> >
> > #1 and #2 are identical. Stevan and I h
is just a Perl-ism. The
PoLS doesn't apply.
Yes, from a consistency point of view, ALL operators should default to
$_ or some other sensible item ($*STDIN for <>, etc). However, the
PoLS does need to guide our decisions.
Rob
n, if you use a grammar extension, ALL bets are off within
that scope until you've read the documentation. Literally anything and
everything can happen, if the author deemed it so. It's a source
filter-like construct that doesn't suck because source filter-like
constructs are part of the spec.
Rob
should be able to freely
> disambiguate or override using anything it want's to. It need not be
> related at all to it's subroles.
To further expand on this, D's disambiguation of method foo() could be:
role D does C { method foo() { Completely::Unrelated::foo() } }
Rob
rl6 allows
assignment to be overloaded like Ruby does. If it does, then the two
expressions aren't guaranteed to be identical as they are now in
Perl5.
Rob
oo} = 3; The problem is with the
subroutines that aren't real methods with correct protection
mechanisms.
So, for a bit of extra complexity, I get peace of mind for myself and my users.
(Oh, and Ruby has first-class block. W00T!)
Rob
re the reasons that they should or shouldn't?
I say no. It goes back to does a role provide a list of function names
with possible default implementations or does it provide a behavior
that is supported by a set of related functions that one can override,
if desired. What you're proposing assumes that roles are nothing more
than jazzed up Java interfaces. I would hate to see that happen. So, I
say that it should be the latter.
Rob
perspective. Almost makes me wonder how much
trouble it would be to implement this in P5 ...
Rob
On 11/7/05, Michele Dondi <[EMAIL PROTECTED]> wrote:
> On Fri, 4 Nov 2005, Rob Kinyon wrote:
>
> > So, for a bit of extra complexity, I get peace of mind for myself and my
> > users.
>
> The point being, and I'm stressing it once again but no more than once,
&g
hing by slurping
everything, then poping the block off of the array?
Rob
-Original Message-
From: Rod Adams [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 31, 2003 12:56 PM
To: Perl 6 Language
Subject: Re: Perl 6's for() signature
At 10:05 AM 7/31/2003 -0600, Luke Palmer wrote:
>
s are.
I'm willing to do any testing needed to get and keep a Cygwin port
happy. If this is something the group wants to pursue, I'll post my
cygghc.
Rob
Gaal -
I pulled svn r2461 and it does compile on cygwin, yes. But, the
@INC problem is still there, preventing 'make test' from running
successfully. Do you want me to look at that?
Rob
On 5/2/05, Gaal Yahas <[EMAIL PROTECTED]> wrote:
> On Mon, May 02, 2005 at 09:06:42A
Will this change remove the need for pugscc to be cygpath'ed on
cygwin? Or, should I go ahead and work on this?
Rob
On 5/3/05, Autrijus Tang <[EMAIL PROTECTED]> wrote:
> Because I want to embed PGE in Pugs, I end up embedding the
> entire libparrot. :-)
>
> As of two ho
if you're thinking of using 3+ ASCII characters for an
operator that it should just become a keyword. For one thing, it's
more maintainable that way. I can remap ^K in vi to be 'perldoc -f"
instead of 'man' and it will work for keywords, but not for Unicode
operat
eans, because it's documented somewhere.
But, don't put it in the core. I thought the core was supposed to be
sparse with modules to add the richness.
Rob
On 5/4/05, Larry Wall <[EMAIL PROTECTED]> wrote:
> On Wed, May 04, 2005 at 08:59:04AM -0400, Rob Kinyon wrote:
> : Thi
What about the function compose() that would live in the module
"keyword", imported by the incantation "use keyword qw( compose );"?
(NB: My P6-fu sucks right now)
multimethod compose (@*List) {
return {
$_() for @List;
};
}
On 5/4/05, Michele Dondi <[EMAIL PROTECTED]> wrote:
> I
Did I
miss a change in focus over the past few months?
Rob
Would that mean that a filehandle opened readonly would throw an
exception if you attempted to either print or warn on it?
On 5/4/05, Juerd <[EMAIL PROTECTED]> wrote:
> Gaal Yahas skribis 2005-05-04 17:24 (+0300):
> > Ah yes, that's another thing I was wondering about: what does opening a
> > pipe
> Rob Kinyon skribis 2005-05-04 11:02 (-0400):
> > Would that mean that a filehandle opened readonly would throw an
> > exception if you attempted to either print or warn on it?
>
> I don't know what warning on a filehandle should be or do, but ignoring
> that bit, y
o use a
builtin feature. I don't understand why, but that's my experience
across 4 states. *shrugs*
*thinks for a minute*
[»+^=«] reminds me of a P5 regex that has a comment saying "This is
black magic. Don't touch!". --That's-- my complaint.
Rob
Can I put an operator in a variable and then use it in the []
reduce meta-operator? Something like:
$op = '+';
$x = [$op] @x;
Rob
because with those changes, I get to Pugs, but I
receive the following errors and I don't know enough about Pugs to get
it working. (This is with r2765, built about 2 hours ago.)
Rob
$ ./script/pugscc -e 'say 123'
be a good option. I can try to cygpath the filenames
before they get passed to hsc2hs, but I don't think that's best.
Rob
s potentially makes a difference in how P6 code
is read ...
Rob
hat it's
> &infix:, not &x.
Though, P6 mayl give us the ability to create circumfix operators (as
seen in the entire reduce thread). I think that syntax will also allow
for functions to be parsed as infix operators, right?
Rob
On 5/6/05, Larry Wall <[EMAIL PROTECTED]> wrote:
> On Fri, May 06, 2005 at 01:26:10PM -0400, Rob Kinyon wrote:
> : > : Does this mean that @{foo()} can be written as @ foo()?
> : >
> : > I would prefer not. Use foo()[] instead.
> :
> : Does this mean that s
c,
> we'd require "reduce" on the short ones instead of the long ones. :-)
I like this idea. It provides more huffman-coding for readability.
Rob
What's really odd is that document links to
http://en.wikipedia.org/wiki/Exclusive_disjunction which ends up
stating that chained xors are associative and commutative, meaning
that instead of acting as one(), it counts parity.
Rob
On 5/9/05, David Landgren <[EMAIL PROTECTED]> wrote:
# New Ticket Created by "Rob West"
# Please include the string: [perl #46473]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=46473 >
This patch should make it so that the NOTNULL macro will work as
expected f
I submitted these patches over a year ago...are they even relevant
anymore?
On Tue, 27 Jul 2010 18:51:12 -0700
"Will Coleda via RT" wrote:
> On Sat Jul 25 17:20:40 2009, hoelzro wrote:
> > See the patches' summaries for details.
>
> Sorry for the delay in responding, but these patches no longer
FWIW, 141 is SIGPIPE. (signal 13 + WIFSIGNALED flag (128))
So something's happening in your RUN script that's causing it to write to a
closed pipe. I hope this helps!
-Rob
On Mon, 27 Mar 2017 11:51:03 +0300
Gabor Szabo wrote:
> Putting
>
> CATCH { default { put
, manipulating global
variables in native code wasn't possible, but
maybe that's changed in the last year or so!
As I said above, the completions offered are pretty limited - if you would like
to extend the completions capabilities of the REPL,
you can change the Completions role in src/core/REPL
It's pretty modular already; only a little more work would be needed to have it
loaded as an external module.
On Tue, 30 May 2017 12:34:08 -0400
Parrot Raiser <1parr...@gmail.com> wrote:
> The REPL's almost an independent project.
>
> Can it be made modular, to reduce the coupling between it an
erl6', or if 'use v6' is found. This
can be improved.
* Speed improvement. I haven't put any time into optimization, and
this can likely be improved.
If you find any bugs, or better yet, if you have any improvements to
submit, please let me know!
-Rob
signature.asc
Description: PGP signature
all"), but the former is probably a little
harder to do.
-Rob
On 3/5/13 11:44 AM, Patrick R. Michaud wrote:
> On Tue, Mar 05, 2013 at 11:13:51AM +0100, Rob Hoelz wrote:
>> I already have my own package for Arch Linux for Rakudo Star, and I keep
>> the OS X homebrew package up-to-date as well. I'd like to create an RPM
>> spec f
I should also mention that while this form produces the bug:
regex foo { { say($) } }
This form does not:
$s ~~ / { say($) } }/
On Sun, 2 Mar 2014 02:02:36 -0800
"Tobias Leich via RT" wrote:
> Am Fr 21. Feb 2014, 17:20:53, r...@hoelz.ro schrieb:
> > I've attached a sample tarball of code; use ufo, make, and perl6
> > test.p6 to run it. A more real-world example is the URI module.
>
> The weird thing is that accessing th
6" is now deprecated:
https://github.com/perl6/specs/commit/b7196bd
-Rob
Yup, PERL6LIB. =)
On Mon, 30 Mar 2015 17:03:05 -0500
Tom Browder wrote:
> I would like an easy way to have a local search path for local Perl 6
> modules (those not installed via Panda).
>
> I'm used to using the environment variable PERL5LIB for Perl 5
> modules. Is there currently any equiva
ollowing people contributed to this release:
Elizabeth Mattijsen, Tobias Leich, Jonathan Worthington, Timo Paulssen,
Rob Hoelz, Christian Bartolomäus, Will "Coke" Coleda, Bart Wiegmans,
Larry Wall, Moritz Lenz, Justin DeVuyst, Steve Mynott, Carl Masak,
Solomon Foster, cygx, smls, Alexa
gt; regards
> Gabor
Hi Gabor,
I believe that http://testers.p6c.org/ is written in Perl 6
(https://github.com/perl6/cpandatesters.perl6.org)
Are you going to put your talk online? I'm sure a bunch of Perl 6ers
(myself included) would be happy to see it!
-Rob
the deprecated code incrementally. I think removing
about six a day should do the trick for the release on the 17th.
What does everyone think of this idea? We can perform the work in a
branch if we want to keep (nom&glr) backwards compatible until we
throw the switch.
-Rob
ld
technically depend on introspection of the signature returning Any in
this case, would we be hesitant to change the behavior?
Thanks,
Rob
treated as single entries in the command history.
Thanks!
-Rob
mboy64,
Moritz Lenz, Altai-man, Rob Hoelz, Zoffix Znet, Salvador Ortiz, Tom Browder,
Ahmad M. Zawawi, Xliff, Matt Oates, Nick Logan, Jonathan Stowe
If you would like to contribute or find out more information, visit
<http://perl6.org>, <http://rakudo.org/how-to-help>, ask on the
On Fri, 09 Sep 2016 16:30:28 -0700
Alex Elsayed wrote:
> On Wednesday, 7 September 2016 17:57:32 PDT Parrot Raiser wrote:
> > This isn't a request for a feature, merely a thought experiment.
> > We're still in the phase where it's more important to ensure that
> > existing features work properly
On 2017-05-01 01:38:14, c...@zoffix.com wrote:
> > On 23 Jun 2015, at 15:37, Rob Hoelz (via RT) > follo...@perl.org> wrote:
> > Unlinking a non-existent file should fail() rather than return True.
>
> The end-goal of .unlinking stuff is for the file to stop existing.
>
On Wed May 13 16:38:02 2015, rjbs wrote:
> A buf is supposed to be mutable, but I can't push to it. TimToday++
> said this
> was incorrect behavior and just NYI.
>
> ~$ perl6 -e 'my $b = Buf.new(1,2,3); $b.push(4)'
> Cannot call push(Buf: Int); none of these signatures match:
> (Any:U \SELF:
On Fri May 29 05:54:10 2015, r...@hoelz.ro wrote:
> On Wed May 13 16:38:02 2015, rjbs wrote:
> > A buf is supposed to be mutable, but I can't push to it. TimToday++
> > said this
> > was incorrect behavior and just NYI.
> >
> > ~$ perl6 -e 'my $b = Buf.new(1,2,3); $b.push(4)'
> > Cannot call push
On Fri May 29 06:23:54 2015, r...@hoelz.ro wrote:
> On Fri May 29 05:54:10 2015, r...@hoelz.ro wrote:
> > On Wed May 13 16:38:02 2015, rjbs wrote:
> > > A buf is supposed to be mutable, but I can't push to it. TimToday++
> > > said this
> > > was incorrect behavior and just NYI.
> > >
> > > ~$ pe
101 - 184 of 184 matches
Mail list logo
