Glenn wrote:
> > Have I missed anything?
>
> Perhaps you've missed one thing.
>
>[snip]
>
> Perl 6 could provide a pragma to produce a warning on the first
> run-time auto-numerification (compile time would be really hard to
> do), together with a selection of diff
Aaron Sherman sent the following bits through the ether:
> It is not. That's exactly the point to AOP, to bring the two
May I suggest that all discussion move to the perl-aspects list
and that everyone take a look at the Aspect module on CPAN.
The language does not need to be changed to enable A
On Wed, Oct 24, 2001 at 11:50:05AM -0700, David Whipp wrote:
> > If Perl is going to have data hiding (I think I read that this was a
> > goal), then you cannot declare these relationships outside of the
> > class that defines the method. That would be like putting a "friend"
> > delcaration only
You have seen Aspect.pm haven't you? Aspect Oriented Programming for
Perl 5, built on top of Hook::LexWrap and very, very cool.
--
Piers
"It is a truth universally acknowledged that a language in
possession of a rich syntax must be in need of a rewrite."
-- Jane Austen?
Is it too late for RFCs? How does one get approved for submission these
days? Or, do we just mail them off to [EMAIL PROTECTED]?
=head1 TITLE
Anonymous classes
=head1 VERSION
Maintainer: Aaron Sherman <[EMAIL PROTECTED]>
Date: 24 October 2001
Version: 1
Mailing List: perl6-language
N
> If Perl is going to have data hiding (I think I read that this was a
> goal), then you cannot declare these relationships outside of the
> class that defines the method. That would be like putting a "friend"
> delcaration only on the foriegn class in C++. It simply should not
> work that way.
I
On Wed, Oct 24, 2001 at 10:42:09AM -0700, David Whipp wrote:
> Aaron Sherman wrote:
> > All of this is still coming into focus for me, and I want to spend
> > more time reading the articles later, but for now I just wanted
> > to see if anyone else has been thinking these thoughts
>
> I do li
Damian Conway wrote:
> Have I missed anything?
Perhaps you've missed one thing. It was kind of in a different branch of the
thread, about string numerification yielding NaN when given input that is "bad"
according to some definition of "badness". It was clear from discussion that
various contr
Aaron Sherman wrote:
> All of this is still coming into focus for me, and I want to spend
> more time reading the articles later, but for now I just wanted
> to see if anyone else has been thinking these thoughts
I do like the idea of AOP; but I think the mechanism you suggest
are too clumsy.
In reading the Oct'01 issue of Communications of the ACM, I find myself
intrigued by the concept of aspect oriented programming (AOP). The basic
idea is that some methods in an object tree have simillar concerns even
though they are in different objects. AOP is an attempt to make such
"crosscuttin
On Wed, Oct 24, 2001 at 09:06:14AM -0400, Aaron Sherman wrote:
> On Tue, Oct 23, 2001 at 02:53:19PM +0200, Nadim Khemir wrote:
>
> > > Don't we already have that in Perl 5?
> > >
> > > if ( /\G\s+/gc ) {# whitespaces }
> > >elsif ( /\G[*/+-]/gc ) { # operator }
> > >elsif (
On Tue, Oct 23, 2001 at 02:53:19PM +0200, Nadim Khemir wrote:
> > Don't we already have that in Perl 5?
> >
> > if ( /\G\s+/gc ) {# whitespaces }
> >elsif ( /\G[*/+-]/gc ) { # operator }
> >elsif ( /\G\d+/gc ) {# term }
> >elsif ( /\G.+/gc ) { # unrecognized
Hi, I found a thread which started with
A proposal for more powerful text processing to be built in to Perl: Flex
and Pushdown Expressions.
> One of the great strengths of Perl is that, more than any other
> language I know, it helps you cross between the "data" space and the
> "program" space:
13 matches
Mail list logo
