On 22/06/07, brian d foy [EMAIL PROTECTED] wrote:
===Per class documentation, not per file documentation
Related to the one above, I'd like to have NAME, SYNOPSIS, etc. for
each class, not just per file. Well, what I really want is the
Smalltalk class and method browsers, but I know I'm not
round some of our interpolated values.
--
Piers Cawley [EMAIL PROTECTED]
http://www.bofh.org.uk/
...
--
Piers Cawley [EMAIL PROTECTED]
http://www.bofh.org.uk/
that is 'a slurpy list of arrays' or 'the rest
of the arguments, without flattening'. If I *really* want aggressive
flattening then I can call, say, @slurpy_param.flatten
--
Piers Cawley [EMAIL PROTECTED]
http://www.bofh.org.uk/
of calculus. So, we're
speaking of the same thing, just in different terms.
Umm... I think you have that relationship the wrong way around.
--
Piers Cawley [EMAIL PROTECTED]
http://www.bofh.org.uk/
. If people want me to be machine for cranking out quote
file fodder, I'll do my best. But I also care about my friends.
Larry
EOQ
--
Piers Cawley [EMAIL PROTECTED]
http://www.bofh.org.uk/
retooling of
the call stack if they are to work properly. And one shot continuations are the
next best thing to useless.
--
Piers Cawley [EMAIL PROTECTED]
http://www.bofh.org.uk/
are different, you have to be careful
about doing an explicit return in them because that returns to the caller of
the lexical scope in which they were defined (otherwise for ... - ... {...}
wouldn't work)
--
Piers Cawley [EMAIL PROTECTED]
http://www.bofh.org.uk/
been protected. it's the work of a
moment to write:
thing.send(:children, *args)
(Oh, and Ruby has first-class block. W00T!)
And continuations. But continuations are scary. Good scary, but still scary.
--
Piers Cawley [EMAIL PROTECTED]
http://www.bofh.org.uk/
Stevan Little [EMAIL PROTECTED] writes:
Piers,
On Oct 12, 2005, at 5:22 AM, Piers Cawley wrote:
We definitely have two instances of A since, B.isa(::A). We also have
a fragile implementation of count.
:)
Sorry, I purposefully made it a kludge as that is usually the way the example
Ovid [EMAIL PROTECTED] writes:
--- Piers Cawley [EMAIL PROTECTED] wrote:
How about:
my method SCALAR::attributes($self:) { $$self }
my method HASH::attributes(%self:) { %self.kv }
my method ARRAY::attributes(@self:) { [EMAIL PROTECTED] }
method _attributes($attrs) {
my
)
}
}
Where we're assuming that a class can find all its subclasses
--
Piers Cawley [EMAIL PROTECTED]
http://www.bofh.org.uk/
:) { $$self }
my method HASH::attributes(%self:) { %self.kv }
my method ARRAY::attributes(@self:) { [EMAIL PROTECTED] }
method _attributes($attrs) {
my @attributes = $attrs.attributes
return @attributes[0] if @attributes == 1;
...
}
Assuming it's legal.
--
Piers Cawley [EMAIL
Peter Haworth [EMAIL PROTECTED] writes:
On Wed, 5 Oct 2005 19:24:47 +0200, Yuval Kogman wrote:
On Wed, Oct 05, 2005 at 16:57:51 +0100, Peter Haworth wrote:
On Mon, 26 Sep 2005 20:17:05 +0200, TSa wrote:
Piers Cawley wrote:
Exactly which exception is continued?
The bottommost one
TSa [EMAIL PROTECTED] writes:
BTW, I would call *intentional* exceptions terrorism.
So that would be all exceptions then. They all get implemented somewhere, even
the ones that get thrown by builtins.
CATCH Exception { say Why do you hate freedom? }
--
Piers Cawley [EMAIL PROTECTED]
http
the send button before I have second thoughts.
The weird thing is that the syntax I rolled there is soon to be the topic of an
original thread, once I've got the thing written up a little more.
--
Piers Cawley [EMAIL PROTECTED]
http://www.bofh.org.uk/
is this:
while () {
if (@buffer MAX) {
push @buffer, $_;
next;
}
# ...
shift @buffer;
push @buffer, $_;
}
while {
if 0..MAX { push @buffer, $_; next }
end
--
Piers Cawley [EMAIL PROTECTED]
http://www.bofh.org.uk/
a new exception that delegates to the
original exception for lots of its behaviour. If, later, you want to explicitly
get at the exception thrown by the helper function, you could do something
like:
$!.inner
--
Piers Cawley [EMAIL PROTECTED]
http://www.bofh.org.uk/
TSa [EMAIL PROTECTED] writes:
HaloO,
Piers Cawley wrote:
Exactly which exception is continued?
The bottommost one. If you want to return to somewhere up its call chain, do:
$!.caller(n).continue(42)
Whow, how does a higher level exception catcher *in general* know
what type it should
Luke Palmer [EMAIL PROTECTED] writes:
On 7/26/05, Ingo Blechschmidt [EMAIL PROTECTED] wrote:
Hi,
are the following assumptions correct?
sub foo ([EMAIL PROTECTED]) { @args[0] }
say ~foo(a, b, c); # a
Yep.
my @array = a b c d;
say ~foo(@array);# a b c d (or
Luke Palmer [EMAIL PROTECTED] writes:
On 7/26/05, TSa (Thomas Sandlaß) [EMAIL PROTECTED] wrote:
Piers Cawley wrote:
I would like to be able to iterate over all the
objects in the live set.
My Idea actually is to embedd that into the namespace syntax.
The idea is that of looking up non
Autrijus Tang [EMAIL PROTECTED] writes:
On Fri, Jul 22, 2005 at 03:40:34PM -0700, Larry Wall wrote:
I dunno. I'm inclined to say that it should default to Item|Pair, and
let people say Any explicitly if they really want to suppress autothreading.
Otherwise conditionals and switches are going
TSa (Thomas Sandlaß) [EMAIL PROTECTED] writes:
Piers Cawley wrote:
Let's say I have a class, call it Foo which has a bunch of attributes, and
I've
created a few of them. Then, at runtime I do:
eval 'class Foo { has $.a_new_attribute is :default10 }';
Assuming I've got the syntax right
Let's say I have a class, call it Foo which has a bunch of attributes, and I've
created a few of them. Then, at runtime I do:
eval 'class Foo { has $.a_new_attribute is :default10 }';
Assuming I've got the syntax right for defaulting an attribute, and lets assume
I have, the Perl runtime
Sam Vilain [EMAIL PROTECTED] writes:
Larry Wall wrote:
Users of the class includes people subclassing the class, so to them
they need to be able to use $.month_0 and $.month, even though there
is no has $.month_0 declared in the Class implementation, only
has $.month.
We thought
Larry Wall [EMAIL PROTECTED] writes:
On Tue, Jul 12, 2005 at 08:48:41PM +0300, Gaal Yahas wrote:
: I propose to throw away the filesystem coupling, and map from a more
: general name of the bit of code we are requiring to a more general
: description of which instance of it we actually got.
Larry Wall [EMAIL PROTECTED] writes:
On Wed, Jul 06, 2005 at 11:47:47PM +0100, Piers Cawley wrote:
: Or you could use a global, but globals are bad...
Globals are bad only if you use them to hold non-global values.
In this case it seems as though you're just going through contortions
Yuval Kogman [EMAIL PROTECTED] writes:
On Fri, Jul 01, 2005 at 13:42:34 +1200, Sam Vilain wrote:
Yuval Kogman wrote:
As I understand it SMD is now not much more than a mechanism to
place a constraint on the MMD, saying that there can only be one
method or subroutine with the same short name.
So, I got to thinking about stuff. One of the more annoying things about
writing nicely decoupled objects and applications are those occasions where you
want an object to be able to create objects in another class. Say you've
provided a singleton interface to your logging system. The naive
BÁRTHÁZI András [EMAIL PROTECTED] writes:
Hi,
I'm wondering, if it's possible with Perl 6 or not?
class MyClass {
method mymethod($par) {
say mymethod called!;
}
}
class ExClass is MyClass {
mymethod(12);
}
# pugs myprog
mymethod called!
I
Brent 'Dax' Royal-Gordon [EMAIL PROTECTED] writes:
As I've said before, Perl supports `alias`--it's just spelled `:=`.
Here's a rubyish idiom:
my old_behaviour := function;
function := sub { try_some_stuff || old_behaviour }
Except, with binding it doesn't work like that, you end up with
Luke Palmer [EMAIL PROTECTED] writes:
On 6/20/05, chromatic [EMAIL PROTECTED] wrote:
On Mon, 2005-06-20 at 12:11 +0200, Juerd wrote:
I think there exists an even simpler way to avoid any mess involved.
Instead of letting AUTOLOAD receive and pass on arguments, and instead
of letting
Carl Franks [EMAIL PROTECTED] writes:
sub factorial (Int $n is topic) {
return 1 when 0;
return $n * factorial $n;
}
hmm, could we write...
sub foo (Class $self is topic: +$foo, +$bar) {
.method;
}
to avoid having to use ./
?
Yay!
So, I was about to write the following test for Pugs:
sub factorial (Int $n) {
my sub factn (Int $acc, $i) {
return $acc if $i $n;
factn( $acc * $i, $i+1);
}
factn(1, 1);
}
When I thought to check the apocalypses and exegeses and, what do you know, I
couldn't find
Luke Palmer [EMAIL PROTECTED] writes:
On 6/16/05, Piers Cawley [EMAIL PROTECTED] wrote:
So, I was about to write the following test for Pugs:
sub factorial (Int $n) {
my sub factn (Int $acc, $i) {
return $acc if $i $n;
factn( $acc * $i, $i+1);
}
factn(1, 1
Suppose I have a simple, single argument recursive function:
sub factorial (Int $n) {
return 1 if $n == 0;
return $n * factorial $n;
}
Can I write that as:
sub factorial (Int $n:) {
return 1 when 0;
return $n * factorial $n;
}
NB. Yes, I know it's a pathological
Following a conversation with Chip on IRC, is this
my @y := @foo[0..][1];
legal?
Luke Palmer [EMAIL PROTECTED] writes:
On 6/14/05, Piers Cawley [EMAIL PROTECTED] wrote:
Following a conversation with Chip on IRC, is this
my @y := @foo[0..][1];
legal?
Definitely not. But it sure would be nice if this:
my @y := @foo[0...][1];
were.
I think that's what I
Rob Kinyon [EMAIL PROTECTED] writes:
Piers Cawley said:
in other words, some way of declaring that a subroutine wants to hang onto
every lexical it can see in its lexical stack, not matter what static
analysis
may say.
I'm not arguing with the idea, in general. I just want to point out
Rod Adams [EMAIL PROTECTED] writes:
Piers Cawley wrote:
Chip and I have been having a discussion. I want to write:
sub foo { my $x = 1; return sub { eval $^codestring } }
say foo()($x);
I claim that that should print 1. Chip claims it should throw a warning about
because of timely
Chip and I have been having a discussion. I want to write:
sub foo { my $x = 1; return sub { eval $^codestring } }
say foo()($x);
I claim that that should print 1. Chip claims it should throw a warning about
because of timely destruction. My claim is that a closure should close over the
Luke Palmer [EMAIL PROTECTED] writes:
On 6/8/05, Piers Cawley [EMAIL PROTECTED] wrote:
In other words, it outputs:
Foo
Foo
# dies
Yep. My mistake.
If that works, then I think it means we can write:
sub call-with-current-continuation(Code $code) {
my $cc
Larry Wall [EMAIL PROTECTED] writes:
On Wed, Jun 08, 2005 at 10:51:34PM +, Luke Palmer wrote:
: Yeah, that's pretty. But that will bite people who don't understand
: continuations; it will bite people who don't understand return; it
: will even bite people who understand continuations,
So, the return in pointy sub thread got me thinking about useful uses of return
in pointy subs that involve being able to return multiple times. And this is
what I came up with, it's an implementation of 'choose':
my give_up = sub { fail Ran out of choices }
sub choose ([EMAIL
Luke Palmer [EMAIL PROTECTED] writes:
On 6/7/05, Matt Fowles [EMAIL PROTECTED] wrote:
On 6/7/05, Ingo Blechschmidt [EMAIL PROTECTED] wrote:
Hi,
sub foo (Code $code) {
my $return_to_caller = - $ret { return $ret };
$code($return_to_caller);
return 23;
}
sub
TSa (Thomas Sandlaß) [EMAIL PROTECTED] writes:
Piers Cawley wrote:
My preference is for:
Boo
Boo
Can't dereferene literal numeric literal 42 as a coderef.
How do you reach the second 'Boo'? Iff - does not create a Sub
but a Block instance then Luke's code can be interpreted
Piers Cawley [EMAIL PROTECTED] writes:
TSa (Thomas Sandlaß) [EMAIL PROTECTED] writes:
Piers Cawley wrote:
My preference is for:
Boo
Boo
Can't dereferene literal numeric literal 42 as a coderef.
How do you reach the second 'Boo'? Iff - does not create a Sub
but a Block
TSa (Thomas Sandlaß) [EMAIL PROTECTED] writes:
Piers Cawley wrote:
[..] then I think it means we can write:
sub call-with-current-continuation(Code $code) {
my $cc = - $retval { return $retval }
For the records: the return here is the essential ingredient, right?
Without
Ingo Blechschmidt [EMAIL PROTECTED] writes:
Hi,
sub foo (Code $code) {
my $return_to_caller = - $ret { return $ret };
$code($return_to_caller);
return 23;
}
sub bar (Code $return) { $return(42) }
say foo bar; # 42 or 23?
I think it should output
Stevan Little [EMAIL PROTECTED] writes:
On May 25, 2005, at 5:39 AM, Piers Cawley wrote:
One of the 'mental apps' that's been pushing some of the things I've been
asking for in Perl 6's introspection system is a combined
refactoring/debugging/editing environment for the language.
Maybe I
Luke Palmer [EMAIL PROTECTED] writes:
On 5/6/05, J Matisse Enzer [EMAIL PROTECTED] wrote:
I've become scared that if Perl is to continue to be viable for large,
complex, multi-developer projects that the tools need to serious
catch-up with what is available for Java, for example. Things like:
Aaron Sherman [EMAIL PROTECTED] writes:
On Wed, 2005-05-18 at 10:51, Luke Palmer wrote:
Except that mixins like this always treat things as virtual.
Whenever you mixin a role at runtime, Perl creates an empty, anonymous
subclass of the current class and mixes the role in that class. Since
David Storrs [EMAIL PROTECTED] writes:
I image we've all written logging code that looks something like this
(Perl5 syntax):
sub foo {
my ($x,$y) = @_;
note(Entering frobnitz(). params: '$x', '$y');
...
}
This, of course, throws an 'uninitialized value in
Larry Wall [EMAIL PROTECTED] writes:
On Tue, Apr 12, 2005 at 11:36:02AM +0100, Piers Cawley wrote:
: wolverian [EMAIL PROTECTED] writes:
:
: On Fri, Apr 08, 2005 at 12:18:45PM -0400, MrJoltCola wrote:
: I cannot say how much Perl6 will expose to the high level language
Darren Duncan [EMAIL PROTECTED] writes:
At 7:10 AM +0100 3/29/05, Piers Cawley wrote:
Doesn't that rather depend on the type of the attribute? Personally, if I get
an object back from accessor method then I expect that any modifications of
that object's state will be seen the next time I look
Larry Wall [EMAIL PROTECTED] writes:
I've been thinking about this in my sleep, and at the moment I think
I'd rather keep .foo meaning $_.foo, but break the automatic binding
of the invocant to $_. Instead of that, I'd like to see a really,
really short alias for $self. Suppose we pick o
Darren Duncan [EMAIL PROTECTED] writes:
At 11:26 PM -0700 3/16/05, Luke Palmer wrote:
For each of the above cases, is a copy of or a reference to the
attribute returned? For each, will the calling code be able to
modify $obj's attributes by modifying the return values, or not?
Well if
Aldo Calpini [EMAIL PROTECTED] writes:
Larry Wall wrote:
I suppose if I were Archimedes I'd have climbed
back out and shouted Eureka, but as far as I know Archimedes never
made it to Italy, so it didn't occur to me...
well, Archimedes *was* italian. for some meaning of italian, at least.
Aaron Sherman [EMAIL PROTECTED] writes:
On Thu, 2004-09-09 at 13:14, Larry Wall wrote:
So whereas Ruby's syntax actually tends to push you toward .each
iterators, Perl 6's syntax will be fairly neutral on the subject,
or maybe biased every so slightly away from method iteration by the
width
John Siracusa [EMAIL PROTECTED] writes:
On 9/3/04 6:45 PM, Damian Conway wrote:
John Siracusa wrote:
I don't see how we could prevent someone from clobbering the global
definitions of PRE and POST to be no-ops if they wanted to. Seems to
me that the whole point of putting the program in
Brent 'Dax' Royal-Gordon [EMAIL PROTECTED] writes:
Piers Cawley wrote:
Brent 'Dax' Royal-Gordon [EMAIL PROTECTED] writes:
Care to explain what those are, O great math teacher?
What's a math teacher?
It's the right^H^H^H^H^HAmerican way to say maths teacher.
You mean American and 'right
Brent 'Dax' Royal-Gordon [EMAIL PROTECTED] writes:
The Perl 6 Summarizer wrote:
The infinite thread
Pushing onto lazy lists continued to exercise the p6l crowd (or at
least, a subset of it). Larry said that if someone wanted to hack
surreal numbers into Perl 6.1 then that would
Larry Wall [EMAIL PROTECTED] writes:
On Tue, Jul 20, 2004 at 11:00:39PM -0700, chromatic wrote:
: On Tue, 2004-07-20 at 19:35, Luke Palmer wrote:
:
: The New Way (tm) to do that would probably be sticking a role onto the
: array object with which you're dealing:
:
: my @foo does
Damian Conway [EMAIL PROTECTED] writes:
I can't say I'm keen on making {...} special in strings. I felt that the
$(...) and @(...) were a much cleaner and more general solution. The
prospect of backslashing every opening brace in every interpolated
string is not one I relish.
Maybe we could
Austin Hastings [EMAIL PROTECTED] writes:
--- The Perl 6 Summarizer [EMAIL PROTECTED] wrote:
Okay, so the interview was on Tuesday 13th of July.
It went well; I'm going to be a maths teacher.
[...]
As we all know, time flies like an arrow, but fruit flies like a
banana. If you found this
Jonadab the Unsightly One [EMAIL PROTECTED] writes:
The Perl 6 Summarizer [EMAIL PROTECTED] writes:
Different OO models
Jonadab the Unsightly One had wondered about having objects
inheriting behaviour from objects rather than classes in Perl 6.
Urgle. I've completely failed to
For various annoying reasons involving a pernickety external drive and
a service centre that, after more than a week *still* hasn't taken a
look at my main machine, I find myself missing a tranche of messages to
perl6-internals and perl6-language. If some kind soul were to send me
mbox files
Piers Cawley [EMAIL PROTECTED] writes:
For various annoying reasons involving a pernickety external drive and
a service centre that, after more than a week *still* hasn't taken a
look at my main machine, I find myself missing a tranche of messages to
perl6-internals and perl6-language
chromatic [EMAIL PROTECTED] writes:
Perl.com has just made A12 available:
http://www.perl.com/pub/a/2004/04/16/a12.html
Warning -- 20 pages, the first of which is a table of contents.
But it's all excellent good stuff. Well done Larry and Co. Now, if you
could all just hold off with
Mark J. Reed [EMAIL PROTECTED] writes:
I think the ¥(yen) suggestion is great, especially since it does indeed
look like a zipper. Still, I would very much like an ASCII infix
alternative for zip().
I propose z as the ASCII alternative for the infix zip operator (either
broken bar or yen).
David Wheeler [EMAIL PROTECTED] writes:
On Mar 20, 2004, at 1:32 PM, Calle Dybedahl wrote:
You don't need Unicode display « and », just plain old ISO 8859-1.
True, but I'd like to get Unicode working for other projects, as well.
They're characters number 171 and 187 there. And AFAIK every
David Wheeler [EMAIL PROTECTED] writes:
On Mar 22, 2004, at 5:02 PM, Piers Cawley wrote:
Try this:
(cond
((eq window-system 'mac)
(when (string= default-directory /)
(setq default-directory ~/))
(setq mac-command-key-is-meta t
mac-reverse-ctrl-meta nil
process
Tom Christiansen [EMAIL PROTECTED] writes:
On Tue, Mar 02, 2004 at 10:01:11AM +1100, Damian Conway wrote:
: That's a *very* interesting idea. What do people think?
I think anyone who does full justification without proportional
spacing and hyphenation is severely lacking in empathy for the
Uri Guttman [EMAIL PROTECTED] writes:
LW == Larry Wall [EMAIL PROTECTED] writes:
LW This would be relatively straightforward for syntax highlighters,
LW I think. But Perl 6 will throw other curves at highlighters that
LW will be much more difficult to solve, such as the fact that any
Luke Palmer [EMAIL PROTECTED] writes:
michael.firestone writes:
Is there somewhere I can get the entire perl6-language archive in a
tarball?
I personally don't know, but there could be somewhere.
I am trying to work on turning the Apocalypses into story cards at
[EMAIL PROTECTED] (Peter Scott) writes:
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Austin Hastings) writes:
PS: While I'm somewhat sympathetic to the fact that eu guys are trying to
spin up 200 years worth of amendments and supreme court decisions at the
same time, it's still a ratf*ck.
Jonathan Lang [EMAIL PROTECTED] writes:
Luke Palmer wrote:
Renaming methods defeats the purpose of roles. Roles are like
interfaces inside-out. They guarantee a set of methods -- an interface
-- except they provide the implementation to (in terms of other,
required methods). Renaming the
Joe Gottman [EMAIL PROTECTED] writes:
- Original Message -
From: Luke Palmer [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 06, 2004 4:51 AM
Subject: [perl] Re: Roles and Mix-ins?
David Storrs writes:
On Sat, Dec 13, 2003 at 11:12:31AM -0800, Larry Wall wrote:
chromatic [EMAIL PROTECTED] writes:
On Tue, 2004-01-06 at 22:26, Austin Hastings wrote:
So on the grand balance of utility, what are the metrics that traits are
supposed to help improve?
Two big ones:
- naming collections of behavior that are too fine-grained to fit into
classes
Lars Balker Rasmussen [EMAIL PROTECTED] writes:
The Perl 6 Summarizer [EMAIL PROTECTED] writes:
Me? I think Perl 6's design 'in the large' will be pretty much
done once Apocalypse 12 and its corresponding Exegesis are
finished. Of course, the devil is in the details, but I don't
Melvin Smith [EMAIL PROTECTED] writes:
At 09:30 PM 1/5/2004 +, Piers Cawley wrote:
Melvin Smith [EMAIL PROTECTED] writes:
At 07:55 PM 1/5/2004 +0100, Lars Balker Rasmussen wrote:
The Perl 6 Summarizer [EMAIL PROTECTED] writes:
people's salaries will depend on Parrot. I confess I
Coo... you really can hear a pin drop in here.
Anyway, happy new year everyone.
--
Beware the Perl 6 early morning joggers -- Allison Randal
Michael Joyce [EMAIL PROTECTED] writes:
Thank you for a lovely Christmas Present.
Any time.
Larry Wall [EMAIL PROTECTED] writes:
On Fri, Dec 19, 2003 at 10:36:01AM -0600, Adam D. Lopresto wrote:
: I've been trying to follow the recent discussion on roles and
: properties and traits and such, but there's something that bugs
: me. If I understand correctly, adding a role at runtime
A. Pagaltzis [EMAIL PROTECTED] writes:
* The Perl 6 Summarizer [EMAIL PROTECTED] [2003-12-16 11:57]:
bear in mind that the authors of the paper use the term
'trait' for what we're calling a 'role' (We already have
traits you see).
Larry Wall [EMAIL PROTECTED] writes:
On Wed, Dec 17, 2003 at 12:11:59AM +, Piers Cawley wrote:
: When you say CHECK time, do you mean there'll be a CHECK phase for
: code that gets required at run time?
Dunno about that. When I say CHECK time I'm primarily referring
to the end
The Perl 6 Summarizer [EMAIL PROTECTED] writes:
Vocabulary
If you're even vaguely interested in the workings of Perl 6's object
system, you need to read the referenced post.
Luke Palmer, worrying about people using Object related vocabulary in
subtly inconsistent ways,
Larry Wall [EMAIL PROTECTED] writes:
On Tue, Dec 16, 2003 at 07:05:19AM -0700, Luke Palmer wrote:
: Michael Lazzaro writes:
:
: On Sunday, December 14, 2003, at 06:14 PM, Larry Wall wrote:
: But the agreement could be implied by silence. If, by the time the
: entire program is parsed,
Michael Lazzaro [EMAIL PROTECTED] writes:
On Tuesday, December 16, 2003, at 12:20 PM, Gordon Henriksen wrote:
finally by default? None for me; thanks, though.
I don't think so; we're just talking about whether you can extend a
class at _runtime_, not _compiletime_. Whether or not Perl can
Luke Palmer [EMAIL PROTECTED] writes:
Piers Cawley writes:
The Perl 6 Summarizer [EMAIL PROTECTED] writes:
http://groups.google.com/[EMAIL PROTECTED]
This should, of course, read:
http://groups.google.com/[EMAIL PROTECTED]
Or even:
http://groups.google.com/[EMAIL PROTECTED]
We
Jonathan Scott Duff [EMAIL PROTECTED] writes:
On Sat, Dec 13, 2003 at 01:44:34PM -0800, Larry Wall wrote:
On Sat, Dec 13, 2003 at 12:50:50PM -0500, Austin Hastings wrote:
: It seems to me there's an argument both ways --
:
: 1. Code written in the absence of a role won't anticipate the role
Michael Lazzaro [EMAIL PROTECTED] writes:
On Wednesday, November 26, 2003, at 12:29 PM, Larry Wall wrote:
If you contrast it with an explicit try block, sure, it looks
better. But
that's not what I compare it with. I compare it with Perl 5's:
$opus.write_to_file($file) or die Couldn't
Simon Cozens [EMAIL PROTECTED] writes:
Luke Palmer:
So modules that introduce new concepts into the language can add new
syntax for them without working with (ugh) a source filter. And some of
these new syntaxes in the core language will actually be in standard
modules, if they're not
Jonathan Scott Duff [EMAIL PROTECTED] writes:
On Wed, Nov 19, 2003 at 08:23:30PM +, Smylers wrote:
This, however, is irritating:
my @new = map { s:e/$pattern/$replacement/; $_ } @old;
I forget the C; $_ far more often than I like to admit and end up with
an array of integers
Mark J. Reed [EMAIL PROTECTED] writes:
On 2003-11-25 at 18:17:04, Piers Cawley wrote:
aString replace: aPattern with: aString.
aString replaceAll: aPattern with: aString.
Stop! Stop that at once! No small talk; we're here for
serious discussions!
:)
Except... the second
Smylers [EMAIL PROTECTED] writes:
Larry Wall writes:
And nested modifiers are still quite illegal in Standard Perl 6.
Right.
Anybody else get the feeling we should write that down somewhere, so we
don't have to have this conversation again in a few months?
It'll be in the summary.
Stéphane Payrard [EMAIL PROTECTED] writes:
s/// in string context should return the string after substituion.
It seems obvious to me but I mention it because I can't find it
in the apocalypses.
Surely it should return the string after substitution, but with an
appropriate 'but true' or
Joe Gottman [EMAIL PROTECTED] writes:
- Original Message -
From: Austin Hastings [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, November 18, 2003 3:04 PM
Subject: [perl] RE: s/// in string context should return the string
As a Bvalue where possible, so
Leopold Toetsch [EMAIL PROTECTED] writes:
Piers Cawley wrote:
newsub and implicit registers
[...] ops [...] that IMCC needed to
track. Leo has a patch in his tree that deals with the issue.
Sorry, my posting seems to have been misleading. The register tracking
code is in the CVS
The Perl 6 Summary of the week ending 20031109
Traditionally this paragraph concerns itself with a few words on what
I've been up to before finally settling down to get the summary written.
But despite the fact that it's nearly four o'clock, it's been one of
those days where I seem
1 - 100 of 470 matches
Mail list logo
