Dan Sugalski [EMAIL PROTECTED] writes:
At 04:21 PM 11/8/2001 -0800, John Rudd wrote:
So, does this mean my other heart's desire of operator overloading might
be coming forth? (I know, I know, here I am, a smalltalker, asking for
operator overloading ... but, what are the smalltalkers gonna do,
Nathan Wiger [EMAIL PROTECTED] writes:
I'm kind of curious to know what you think would happen with the
following. I've commented where I'm confident...
interface Number;
sub TIESCALAR;
sub STORE;
sub FETCH;
package integer implements Number; # I really
Simon Cozens [EMAIL PROTECTED] writes:
On Wed, Sep 27, 2000 at 05:25:28AM -, Perl6 RFC Librarian wrote:
Not an awful lot was said once this RFC was condensed down to "Everything
becomes an object". I believe some implementation and conceptual hurdles
exist which have discouraged more
Perl6 RFC Librarian [EMAIL PROTECTED] writes:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Transparently integrate Ctie
On the whole I think I'm liking this. But it needs work.
my packed $a; # just an assertion, RFC 218
$a =
Nathan Wiger [EMAIL PROTECTED] writes:
* The new Cinterface keyword would be unnecessary if *package
specifications* could take attributes:
interface Fetcher;
would then become:
package Fetcher : interface;
I'm not
Nathan Wiger [EMAIL PROTECTED] writes:
By specifying "use interface" explicitly, you can make sure that your
class follows the interface spec. Otherwise, you rely on other classes
in the hierarchy above you doing so, and then you indirectly inheriting
from that interface. So "use interface"
Michael G Schwern [EMAIL PROTECTED] writes:
On Mon, Sep 18, 2000 at 09:48:27AM +0100, Piers Cawley wrote:
Michael G Schwern [EMAIL PROTECTED] writes:
Nope. fields::new() basically just does Cbless
[\%{"$class\::FIELDS"}], $class, but the current pseudohash
implementati
Michael G Schwern [EMAIL PROTECTED] writes:
On Thu, Sep 14, 2000 at 02:19:38PM +0100, Piers Cawley wrote:
Michael G Schwern [EMAIL PROTECTED] writes:
package Dog;
use fields qw(this night up);
my Dog $ph = [];
$ph-{this} = "that";
That works? I t
Damian Conway [EMAIL PROTECTED] writes:
Piers wrote:
I'm kind of tempted to look at adding another pragma to go with 'use
base' along the lines of:
use implements 'Interface';
Which is almost entirely like Cuse base 'Interface' but with
'Interface'
Graham Barr [EMAIL PROTECTED] writes:
I would suggest that anyone want to contribute to this discussion should
first read the thread about the addition of this pragma to perl5 in
the perl5-porters archives
Perl6 RFC Librarian [EMAIL PROTECTED] writes:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Cmy Dog $spot is just an assertion
=head1 VERSION
Maintainer: Piers Cawley [EMAIL PROTECTED]
Date: 13th September 2000
Mailing List: [EMAIL
Nathan Torkington [EMAIL PROTECTED] writes:
Perl6 RFC Librarian writes:
I therefore propose that Cmy Dog $spot comes to mean that C$spot
is restricted to being either undefined or a reference to a CDog
object (or any subclasses of Dog). Simply having this implicit
assertion can be
Michael G Schwern [EMAIL PROTECTED] writes:
On Wed, Sep 13, 2000 at 08:43:43PM -, Perl6 RFC Librarian wrote:
The behaviour of the my Dog $spot syntax should simply be an
assertion of the invariant:
(!defined($spot) || (ref($spot) $spot-isa('Dog)))
What about the current
Damian Conway [EMAIL PROTECTED] writes:
Piers wrote:
The behaviour of the my Dog $spot syntax should simply be an
assertion of the invariant:
(!defined($spot) || (ref($spot) $spot-isa('Dog)))
(!defined($spot) || (ref($spot) $spot-isa('Dog')))
Hildo Biersma [EMAIL PROTECTED] writes:
Piers Cawley wrote:
=head1 ABSTRACT
Cmy Big::Long::Prefix::Class $object = Big::Long::Prefix::Class-Egtnew
is a pain in the bum to type. We should replace this with
use namespace 'Big::Long::Prefix';
my ::Class $object = ::Class
=head1 TITLE
Cmy Dog $spot is just an assertion
=head1 VERSION
Maintainer: Piers Cawley [EMAIL PROTECTED]
Date: 12th September 2000
Last Modified: 12th September 2000
Mailing List: [EMAIL PROTECTED]
Version: 0
Status: Draft
=head1 ABSTRACT
The behaviour of the my Dog $spot syntax
Michael G Schwern [EMAIL PROTECTED] writes:
On Mon, Sep 04, 2000 at 09:53:39PM -, Perl6 RFC Librarian wrote:
Objects : Core support for method delegation
I like it! One gripe (of course)...
The proposed delegation mechanism would work via a pragma:
use delegation
Perl6 RFC Librarian [EMAIL PROTECTED] writes:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Objects : Core support for method delegation
I *want* this. Delegation is cool. Delegation that gets set up at
compile time and is marked as such and can
Michael Fowler [EMAIL PROTECTED] writes:
On Fri, Sep 01, 2000 at 05:23:27PM +0200, Slaven Rezic wrote:
Often, there is the case that "my" is used before actually assigning a
value to it. For example:
my Foo $foo;
if ($cond1) {
$foo = new Foo 1, 2, 3;
} else {
"David E. Wheeler" [EMAIL PROTECTED] writes:
On 1 Sep 2000, Perl6 RFC Librarian wrote:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Objects : Private keys and methods
Here, here amen, Damian! This one gets my instant vote!
And
Perl6 RFC Librarian [EMAIL PROTECTED] writes:
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
my Dog $spot should call a constructor implicitly
Eeeeww. Most of the time I use 'my Dog $spot' is along the lines
of:
package Dog;
sub
Markus Peter [EMAIL PROTECTED] writes:
--On 22.08.2000 18:24 Uhr + David L. Nicol wrote:
Regardless of what its called, in a method called as a subroutine,
the variable could refer to the last instance of this kind of object
used by this thread.
Hmm Does that mean if I once
Perl6 RFC Librarian [EMAIL PROTECTED] writes:
=item *
Changes to the semantics of Cbless so that, after associating an
object with a class, the class's CINIT methods are automatically
called on the object. An additional trailing C@ parameter for
Cbless, to allow arguments to be passed to
23 matches
Mail list logo
