(or was that X.500... which one was the funky LDAP-like ugly-as-sin
thing the Europeans (i.e. ISO) tried to pretend was better than
Internet-style addressing because it allowed you to route mail based on how
much fiber the recipient had in their diet?)
--
Aaron Sherman
[EMAIL PROTECTED] finger
On Fri, 2002-07-12 at 02:33, Sean O'Rourke wrote:
What's currently supported:
- if/elsif/else (even unless and the feared elsunless;)
When we talked about this last, I had been concerned about loops and
conditionals, but others had scoping concerns. Ok, perhaps there's no
way we can roll in
On Mon, 2002-07-22 at 04:36, [EMAIL PROTECTED] wrote:
Now, I ask for PMC programmers to take care implementing this! Notice
that, for example in arrays, arrays with the same length but different
elements should return different hash codes (or try). But for the same
elements MUST return
On Wed, 2002-07-24 at 12:34, Fisher Mark wrote:
But then sometimes you'd *want* hashing to be based on the
content.
OK, I'll bite -- when would you want this behavior? This behavior means
that once you change the contents, the hash value would become irretrievable
unless you restored
I had assumed Perl6 will have copy-on-write references, so that
$x = [1,2,3];
y = *$x;
would not require a copy. However, on thinking about it further, I
realized that that would get you in trouble here:
$x = [1,2,3];
%h{$x} = 1;
y = *x;
$x[0]++;
print %h{$x};
This
On Thu, 2002-07-25 at 03:12, [EMAIL PROTECTED] wrote:
Aaron Sherman [EMAIL PROTECTED] writes:
my @x is Hashed::ByValues = (1,2,3);
%h = (@x = 1);
@x[1] += 4;
Personally I don't like the C is Hashed::ByValues because it smacks
of spooky action at a distance; I much prefer
I just wrote this code in Perl5:
$stuff = (defined($1)?$1:$2) if /^\s*(?:(.*?)|(\S+))/;
This is a common practice for me when I parse configuration and data
files whose formats I define. It's nice to be able to quote fields that
have spaces, and this is an easy way to parse the result.
In
On Wed, 2002-08-28 at 03:23, Trey Harris wrote:
Note--no parens around $field. We're not capturing here, not in the
Perl 5 sense, anyway.
When a pattern consisting of only a named rule invokation (possibly
quantified) matches, it returns the result object, which in boolean
context
On Thu, 2002-08-29 at 08:05, Ken Fox wrote:
A question: Do rules matched in a { code } block set backtrack points for
the outer rule? For example, are these rules equivalent?
rule expr1 {
term { /operators/ or fail } term
}
rule expr2 {
term operators term
}
And a
On Thu, 2002-08-29 at 10:28, Ken Fox wrote:
Aaron Sherman wrote:
rule { term { /operators/.commit(1) or fail } term }
The hypothetical commit() method being one that would take a number and
That would only be useful if the outer rule can backtrack into the
inner /operators
[NOTE: BCCing off-list to protect private email addresses]
On Fri, 2002-08-30 at 09:07, Ken Fox wrote:
Does the following example backtrack into foo?
rule foo { b+ }
rule bar { a foo b }
This was the bit that got me on-board. I did not see the need for
backtracking into rules until
Is C\n going to be a rule (e.g. C eol ) or is it implicitly
translated to:
[\x0a\x0d...]+
If it's the latter, then what does this do?
\n?
Do I get
[[\x0a\x0d...]+]?
Or do I get
[\x0a\x0d...]+?
If the former (which I assume is the case), how do I get the
On Sat, 2002-08-31 at 07:07, Damian Conway wrote:
Aaron Sherman wrote:
Is C\n going to be a rule (e.g. C eol )
There might be an named rule like that. But C\n will certainly
still be available.
or is it implicitly translated to:
[\x0a\x0d...]+
No. It will be equivalent
I'm working on a library of rules and subroutines for dealing with UNIX
system files. This is really just a mental exercise to help me grasp the
new pattern stuff from A5.
I've hit a snag, though, on hypothetical variables. How would this code
work?
{
my $x = 2;
my $y =
On Mon, 2002-09-02 at 23:50, Trey Harris wrote:
No. $0{x} would be set to grass. $x would stay as 2. $x is in a
different scope from the hypothetical, so it doesn't get touched.
Ok, it's just taking some time for me to get my head around just what
C/.../ and Crule{...} are, but I'm getting
On Tue, 2002-09-03 at 11:35, Ken Fox wrote:
Peter Haworth wrote:
Also the different operators used (:= inside the rule, = inside the code)
seems a bit confusing to me; I can't see that they're really doing anything
different:
/ $x := (gr\w+) /vs/ (gr\w+) { let $x = $1 } /
On Wed, 2002-09-04 at 00:01, Sean O'Rourke wrote:
On Tue, 3 Sep 2002, Luke Palmer wrote:
On Tue, 3 Sep 2002, Brent Dax wrote:
Damian Conway:
# $roundor7 = rx /roundascii+[17]/
#
# That is: the union of the two character classes.
How can you be sure that
On Wed, 2002-09-04 at 00:22, Aaron Sherman wrote:
Then, why is there a C+? Why not make it C|?
$foo = rx/ a|b|[cde]|f /
This brings to mind a few big things that have been batting around in my
head about user-defined rules for a while now These things fall out
nicely from A5, I
On Wed, 2002-09-04 at 09:55, Markus Laire wrote:
On 4 Sep 2002 at 0:22, Aaron Sherman wrote:
On Wed, 2002-09-04 at 00:01, Sean O'Rourke wrote:
None, I think. Of course, if we ignore internals, there's no
difference bewteen that and rx /roundascii | 1 | 7/.
Then, why
On Wed, 2002-09-04 at 12:41, Luke Palmer wrote:
Aaron Sherman wrote:
So, for example here are some translations of existing operators:
+ ={.count 0}
* ={1}
*? ={1}?
8 ={.count == 8}# No optimization possible!
Could it be done this way
On Wed, 2002-09-04 at 14:38, Jonathan Scott Duff wrote:
my $x;
/ (\S*) { let $x = .pos } \s* foo /
After this pattern, $x will be set to the ending position of
$1--but only if the pattern succeeds. If it fails, $x is
restored to undef
On Wed, 2002-09-04 at 07:28, Damian Conway wrote:
Aaron Sherman wrote:
Hmm... I had not thought of the copy aspect. Certainly, the code version
is more flexible. You could define C$x above as anything. For example:
/ (gr\w+) {let $x = Gr_Thing.new($1)} /
The binding
Ok, so without knowing what the XS-replacement will look like and
without knowing what we're doing with filehandle-functions (is tell()
staying or does it get removed in favor of $fh.tell()) and a whole lot
of other stuff it's impossible to translate all of the Perl 5 functions
to Perl 6.
Oh, BTW: Lest anyone think I'm spamming p6l for no reason, I sent the
Builtins.p6m to p6l instead of p6i because I consider this a document,
not code. When some of the questions get ironed out about the language,
then I will talk to p6i about next steps.
On Thu, 2002-09-05 at 01:47, Brent Dax wrote:
Aaron Sherman:
# Ok, so without knowing what the XS-replacement will look like
# and without knowing what we're doing with
# filehandle-functions (is tell() staying or does it get
# removed in favor of $fh.tell()) and a whole lot of other
On Thu, 2002-09-05 at 01:47, Brent Dax wrote:
Aaron Sherman:
The one thing I notice all over the place is:
sub abs($num is int){ return $num=0 ?? $num :: -$num }
Another thing I'm not sure on... how do you force numeric, but not
integer typing on a parameter? Is that Cnum[ber]? $var
On Thu, 2002-09-05 at 03:18, Leopold Toetsch wrote:
Brent Dax wrote:
Aaron Sherman:
sub abs($num is int){ return $num=0 ?? $num :: -$num }
^
I believe that should be (int $num).
and there is a »abs« in core.ops.
I'll remove that then, and replace
On Wed, 2002-09-04 at 22:46, Ken Fox wrote:
rule iso_date { $year:=(\d{4}) -
$month:=(\d{2}) -
$day:=(\d{2}) }
You mean C \d4 , etc. I presume.
. I'm out of town for the
weekend, but will be back and catching up on mail Sunday night.
#
# The core built-ins for Perl 6.
#
# Written in 2002 by Aaron Sherman [EMAIL PROTECTED]
# This file can be distributed/modified under the same terms as Perl itself..
module CORE;
# So how are we doing
On Fri, 2002-09-06 at 09:29, Nicholas Clark wrote:
On Fri, Sep 06, 2002 at 01:34:56AM -0400, Aaron Sherman wrote:
# INTERNAL q, qq, qw
# XXX - how do I do quote-like operators? I know I saw someone say...
# Need to do: qr (NEVER(qr)) and qx
presumably the way the perl5 tokeniser does
of events.
--
Aaron Sherman [EMAIL PROTECTED]
http://www.ajs.com/~ajs
that
exports some of it's more commonly used rules. So you might say:
use Math::IEEE :rules;
while {
if / (ieee_float) / {
print Floater: $1\n;
}
}
Which is certainly a lot cleaner than a big hairy pattern hanging in the
middle of your code
--
Aaron
($mtime, $ctime, ...) {
# ...
return %statstruct but lexicals(%statstruct);
}
Now, the compiler can generate stomping warnings at compile-time instead
of just at run time.
--
Aaron Sherman [EMAIL PROTECTED]
http://www.ajs.com/~ajs
On Sat, 2002-09-07 at 14:22, Smylers wrote:
Aaron Sherman wrote:
sub chomp($string is rw){
[...]
} elsif $irs.length == 0 {
$string =~ s/ \n+ $ //;
Should that C+ be there? I would expect chomp only to remove a single
line-break.
Note
.
I'm making heavy use of Cgiven, in the assumption that it will make
the code easy to optimize.
--
Aaron Sherman [EMAIL PROTECTED]
http://www.ajs.com/~ajs
On Mon, 2002-09-09 at 17:52, Nicholas Clark wrote:
On Mon, Sep 09, 2002 at 05:36:42PM -0400, Aaron Sherman wrote:
Correct in as far as it goes. The more general answer is that one of the
goals of this re-write (as I was lead to believe) was that the Perl
internals would be maintainable
is that it does not require a user
to know the internals of Perl or Parrot in order to create linkage to
external programs.
Thoughts?
--
Aaron Sherman X137
[EMAIL PROTECTED]
We had some good machines, but they don't work no more.
-Faded Flowers / Shriekback
On Thu, 2002-09-12 at 20:09, David Whipp wrote:
Aaron Sherman [mailto:[EMAIL PROTECTED]] wrote:
I'm thinking XS thoughts because we're going to need a few external
things at SOME point It would be so nice if Perl 6's XS
was part of the language, rather than an external pre-processor
On Thu, 2002-09-12 at 21:10, Brent Dax wrote:
Aaron Sherman:
# I'm thinking XS thoughts
# Something like:
#
# module somesuch;
# use External (language=C);
# sub chdir(string $path //= $ENV{HOME}) is
# external(returns='int');
I prefer:
module System::FS
;
process($x);
That I guess the sub could expand to:
my Dog $i = @_[0]; # If it works, it works
$i.bark
@_[0] = $i;
But that could have very different semantics than the user expects
--
Aaron Sherman [EMAIL PROTECTED]
http://www.ajs.com/~ajs
not require a semicolon. Thus:
eval {...} / 2
would be an error in exactly the same way that
if 0 {...} / 2
would be, but the common
eval {...};
would be ok, even though it's got a null statement.
Remember, all's fair if you pre-declare.
--
Aaron Sherman [EMAIL
intended). I even come out of it with a smile at the
end.
Thanks again!
--
Aaron Sherman [EMAIL PROTECTED]
http://www.ajs.com/~ajs
has
a default prototype of:
sub($_//=$_){};
ne?
--
Aaron Sherman [EMAIL PROTECTED]
http://www.ajs.com/~ajs
) + 0;
--
Aaron Sherman [EMAIL PROTECTED]
this last example. Can you give a surrounding
context so I can see how that would be used?
--
Aaron Sherman [EMAIL PROTECTED]
On Fri, 2002-09-20 at 10:39, Larry Wall wrote:
On 20 Sep 2002, Aaron Sherman wrote:
: Is that any list as oppopsed to any array? Or is that arrayref in a
: numeric context the length of the array? In other words does this do
: what I think I think it does?
:
: $shouldbe3 = (1,2,3) + 0
]; # or is that ($a,$b,$c)?
my($x,$y,$z) = [1,2,3];
[1,2,3][1] == 2;
Thoughts?
--
Aaron Sherman [EMAIL PROTECTED]
, and get lost in over-simplified examples
like C+(0) which seem contrived and unimportant in a vacuum.
--
Aaron Sherman [EMAIL PROTECTED]
this make sense?
--
Aaron Sherman [EMAIL PROTECTED]
= @massive;
or
if @massive {...}
or the like. In both cases, your later concerns about long-lived
references go away.
--
Aaron Sherman [EMAIL PROTECTED]
these right, we're pretty much
doomed from the outset.
You have that upside-down. Because this is so fundamental, it's worth a
great deal of magic to make it seem right in as many contexts as
possible. This is what Perl has always done, no?
--
Aaron Sherman [EMAIL PROTECTED]
On Tue, 2002-09-24 at 01:46, Trey Harris wrote:
In a message dated 24 Sep 2002, Aaron Sherman writes:
This is because push is
almost certainly defined as:
sub push(@target, *@list) { ... }
That should be
sub push(@target is rw, *@list);
Well, yes, but that wasn't
On Tue, 2002-09-24 at 10:27, Peter Haworth wrote:
On 24 Sep 2002 05:21:37 -0400, Aaron Sherman wrote:
On Tue, 2002-09-24 at 01:46, Trey Harris wrote:
sub push(@target is rw, *@list);
Well, yes, but that wasn't the point. The C*@list will force array
flattening, thus
push
introduce the case where:
$x = (1,2,3);
@y = (1,2,3);
$z = [1,2,3];
push @a, $x, @y, $z, (1,2,3), [1,2,3];
Behaves in ways that will take hours to explain to newbies, and I assure
you it ain't WIM. Not even a little bit.
--
Aaron Sherman [EMAIL PROTECTED]
that Perl 6 is starting to take shape, I may go back and finish Sand
as a Parrot front-end (though it was ultimately aimed at being purely
compiled like C).
--
Aaron Sherman [EMAIL PROTECTED]
the following parameters:
=over 5
=item C$a
This parameter is an integer which must be positive.
=back
Walla! Self-documenting functions.
--
Aaron Sherman [EMAIL PROTECTED]
//=
--
Aaron Sherman [EMAIL PROTECTED]
This message (c) 2003 by Aaron Sherman,
and granted to the Public Domain in 2023.
Fight the DMCA and copyright extension!
the conversion.
You still need C{} vs. C[] for anonymous types, but I don't think
you NEED them for indexing. Now the question becomes, do you WANT them
for readability?
--
Aaron Sherman [EMAIL PROTECTED]
This message (c) 2003 by Aaron Sherman,
and granted to the Public Domain in 2023.
Fight the DMCA
.
Or did I miss something there?
--
Aaron Sherman [EMAIL PROTECTED]
This message (c) 2003 by Aaron Sherman,
and granted to the Public Domain in 2023.
Fight the DMCA and copyright extension!
On Tue, 2003-01-28 at 16:34, Dan Sugalski wrote:
At 4:17 PM -0500 1/28/03, Aaron Sherman wrote:
Now the question becomes, do you WANT them
for readability?
Given that Larry's answer has been a resounding yes all along,
I'm not sure that this specific case was brought up. I remember Larry
and arrays.
So, the most we can do is make them not work too differently.
--
Aaron Sherman [EMAIL PROTECTED]
This message (c) 2003 by Aaron Sherman,
and granted to the Public Domain in 2023.
Fight the DMCA and copyright extension!
,
but see above.
4. unshift. identical to push.
My point boils down to this: the semantics are fundamentally different no
matter how similar or different the syntax is.
Only if you want them to be.
--
Aaron Sherman [EMAIL PROTECTED]
This message (c) 2003 by Aaron Sherman,
and granted
array buckets are initialized to
--
Aaron Sherman [EMAIL PROTECTED]
This message (c) 2003 by Aaron Sherman,
and granted to the Public Domain in 2023.
Fight the DMCA and copyright extension!
:
$x[7] = 8;
That could auto-vivify an array ref or a hash ref, and choosing one or
the other is kind of scary. I think you could work around that, but it
would require a real dedication to the IDEA that Perl has a generic
container type.
--
Aaron Sherman [EMAIL PROTECTED]
This message
). This sort of logic deferral is
common to many uses of undefined values (or NULL) in databases, even
when columns have defaults that are non-null.
--
Aaron Sherman [EMAIL PROTECTED]
This message (c) 2003 by Aaron Sherman,
and granted to the Public Domain in 2023.
Fight the DMCA and copyright extension!
not so bad. undef
should still probably keep its old semantics when being converted to an
integer and go to zero, though.
--
Aaron Sherman [EMAIL PROTECTED]
This message (c) 2003 by Aaron Sherman,
and granted to the Public Domain in 2023.
Fight the DMCA and copyright extension!
to such an example?
--
Aaron Sherman [EMAIL PROTECTED]
This message (c) 2003 by Aaron Sherman,
and granted to the Public Domain in 2023.
Fight the DMCA and copyright extension!
On Wed, 2003-01-29 at 17:12, Dan Sugalski wrote:
At 12:40 PM -0500 1/29/03, Aaron Sherman wrote:
Elements of a has ARE ordered, just not the way you may expect.
Just to nip this one in the bud...
The bud was back that-a-way about 3 days
If people start assuming that there's *any
On Wed, 2003-01-29 at 17:50, Spider Boardman wrote:
On 29 Jan 2003 14:29:52 -0500, Aaron Sherman wrote (in part):
ajs As for the argument that testing for true non-existentness is a
ajs burden, check out the way Perl5 does this. Hint: there's a central
ajs sv_undef, and that's not what
of deconstructing *it*.
Hmm... why is it that Perl brings out the religious and social metaphors
for me? ;)
--
Aaron Sherman [EMAIL PROTECTED]
This message (c) 2003 by Aaron Sherman,
and granted to the Public Domain in 2023.
Fight the DMCA and copyright extension!
--
Aaron Sherman [EMAIL PROTECTED]
This message (c) 2003 by Aaron Sherman,
and granted to the Public Domain in 2023.
Fight the DMCA and copyright extension!
withdrawal. Since
there's not much I can do on the library front at this stage anyway, I'm
off to work on sand. Good luck all!
--
Aaron Sherman [EMAIL PROTECTED]
This message granted to the Public Domain in 2023.
Fight the DMCA and copyright extension!
just returns key/value pairs) and sortpairs' job is just
to compare the keys and return the resulting sorted values.
No Perl 6 here, move along ;-)
Perl 6 could contribute here by making it cheaper to construct/pass the
keys, but that's about it.
--
Aaron Sherman [EMAIL PROTECTED]
Senior
On Thu, 2004-02-12 at 08:43, Aaron Sherman wrote:
sub sortpairs(@) {
my $comp = shift;
my %pairs = @_;
return map {$pairs{$_}} sort {$comp-($a)} keys %pairs;
}
Doh... it's early for me. That's Csort {$comp-()} with no parameter.
The fact that $a and $b are dynamically scoped in Perl 5
interface other than the fact that traits appear to be more of a
run-time construct.
Java interfaces are actually a very nice compromise between multiple and
single inheritance.
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get me down
;
The second example really illustrates the point that you can swap the
direction of key order and mechanism to compare them at your whim.
Now, you just need to call sortpairs with any array of arrays of keys
(with trailing value).
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer
, we're doing the same work.
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get me down!' -Shriekback
On Thu, 2004-02-12 at 14:03, chromatic wrote:
On Thu, 2004-02-12 at 05:52, Aaron Sherman wrote:
Perhaps I'm slow, but I don't see the difference between a trait and a
Java interface other than the fact that traits appear to be more of a
run-time construct.
The easy answer
weight exception system
If Perl 6 contained only the above and nothing else, I would be a happy
camper, and my production code would be far less prone to errors and
structural shortcomings.
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite
(e.g. not as much reliance on blank lines), and
also a better implementation of X and L, but other than that I think POD
is a wonderful format and one of the strenghts of the Perl distribution.
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite
and wanting it for personal
reasons.
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get me down!' -Shriekback
? Does C.bar_attr call my method, and not the accessor, or is
there some other way to do that?
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get me down!' -Shriekback
signature.asc
Description: This is a digitally signed message
it is that there will be an A7 back-fill, I have no
idea, but A11 sounds like its going to be big enough to make all of us
forget about A7-10 anyway ;-)
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get me down!' -Shriekback
signature.asc
to NOT explode other than []? I can't think of any.
push @a, $b
Is it too non-obvious that if $b is an array ref, then this is going to
extend @a by $b.length elements?
Pardon my ignorance, but I thought this was the plan. Feel free to
correct me if I am wrong.
--
Aaron Sherman [EMAIL PROTECTED
?
What's more that could be:
for *%x{$y}{$z} - $i {...}
and I can't imagine it makes any sense to bind that * anywhere but:
for *(%x{$y}{$z}) - $i {...}
I like the division between @ and *, since the two meanings had somewhat
too much overlap in most code.
--
Aaron Sherman [EMAIL
). It would be
nice to have an un-lazying operator of some sort which could assert a
lack of side-effects as a side-effect.
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get me down!' -Shriekback
use 6;
stdout.print(Hello world\n); # not sure if the invocant will do it
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get me down!' -Shriekback
give you an error (you really deserve it) or it would
just switch back to Perl 6 mode... the problem arises when you ask,
what about anything that got parsed in between the two? Yech.
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get
on that.
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get me down!' -Shriekback
;
... anything else ...
use 6;
should be an error, and if you want to write your own support for My5
and My6 which don't give an error, CP6?PAN6?'s doors will be wide
open.
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get
:
#!/usr/bin/perl
use 6;
and add:
use 5;
to my existing Perl 5 programs that I don't have time to convert. That
doesn't mean it's the only way to do it.
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get me down
:
sub do_every(int $n, int $current, code $doit, code $elsedoit = undef) {
if $n % $current == 0 {
$doit();
} elsif defined $elsedoit {
$elsedoit();
}
}
--
Aaron Sherman [EMAIL PROTECTED
;-)
The last step above is what I would expect a B::Deparse-like thing for
Perl 6 to produce.
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get me down!' -Shriekback
worried about
interpolation, and rightly so.
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get me down!' -Shriekback
be further slowing down hash access
because it's special-cased in the default situation?
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get me down!' -Shriekback
not SETTING status, you're reading it,
but you are passing parameters to the read accessor. How do you do that
if parameters force a write?
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get me down!' -Shriekback
}
...
}
Then $$ is just a Process object, but behaves exactly as you always
expected it to.
$$.kill(ABRT)
then does what you might expect, as does:
say $$.cmdline;
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound
= $filehandlelikething.getline;
}
?
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get me down!' -Shriekback
::{$obj1.class} $obj2;
?
--
Aaron Sherman [EMAIL PROTECTED]
Senior Systems Engineer and Toolsmith
It's the sound of a satellite saying, 'get me down!' -Shriekback
that works than one that is complete. Plenty
of time to complete it later, but those who are thinking of taking on
large-scale development with it (e.g. converting over large CPAN modules
or implementing new Perl6ish libraries) just want something that runs :)
--
Aaron Sherman [EMAIL PROTECTED
101 - 200 of 537 matches
Mail list logo
