Re: Selective exporting of properties/methods

2002-05-15 Thread Chris Dutton
On Wednesday, May 15, 2002, at 10:17 AM, Aaron Sherman wrote: > On Sat, 2002-05-11 at 13:58, Chris Dutton wrote: > >> method world is public_to(Bar) { > > Might as well make that: > > method world is private(Bar) > > I tend to take any opportunity to recycle syntax, plus keywords with

Re: Selective exporting of properties/methods

2002-05-15 Thread Aaron Sherman
On Sat, 2002-05-11 at 13:58, Chris Dutton wrote: > method world is public_to(Bar) { Might as well make that: method world is private(Bar) I tend to take any opportunity to recycle syntax, plus keywords with underscores give me gas. ;)

RE: Selective exporting of properties/methods

2002-05-13 Thread Fisher Mark
Miko O'Sullivan writes: >What I've often wanted would be standard method that is called before every >subroutine call. If that method returns false then the method that was >called is not called. What you're describing is Aspect-Oriented Programming (I think). Take a look around CPAN for Aspect.

Re: PRE-POST methods [Was: Selective exporting of properties/methods]

2002-05-13 Thread Larry Wall
[EMAIL PROTECTED] writes: : ]- I can't remember but i think I read somewhere or it was discussed here (can't :remember), but I think it was mentioned that Perl6 will have PRE and POST method/sub :handlers probably specified as attribute, so that (syntax may be wrong): : : class XXX { : method

PRE-POST methods [Was: Selective exporting of properties/methods]

2002-05-13 Thread raptor
]- I can't remember but i think I read somewhere or it was discussed here (can't ]remember), but I think it was mentioned that Perl6 will have PRE and POST method/sub ]handlers probably specified as attribute, so that (syntax may be wrong): class XXX { method blah is PRE {} method blah {}

Re: Selective exporting of properties/methods

2002-05-12 Thread Chris Dutton
On Sunday, May 12, 2002, at 02:18 PM, Miko O'Sullivan wrote: >> While thinking Eiffel-ish thoughts the other day, I began to wonder if >> Perl6's classes could go beyond the simple private/public/protected >> scheme by optionally allowing for a property or method to only be >> accessed by a cert

Re: Selective exporting of properties/methods

2002-05-12 Thread Miko O'Sullivan
> While thinking Eiffel-ish thoughts the other day, I began to wonder if > Perl6's classes could go beyond the simple private/public/protected > scheme by optionally allowing for a property or method to only be > accessed by a certain set of classes. Many times when I've used OO languages I've wi

Selective exporting of properties/methods

2002-05-11 Thread Chris Dutton
While thinking Eiffel-ish thoughts the other day, I began to wonder if Perl6's classes could go beyond the simple private/public/protected scheme by optionally allowing for a property or method to only be accessed by a certain set of classes. For instance(as I understand Perl6 syntax): class