Re: RFC 336 (v1) use strict 'objects': a new pragma for using Java-like objects in Perl
[email protected] (Jonathan Scott Duff) Thu, 28 Sep 2000 16:42:04 -0500
| Newsgroups | perl.perl6.language.objects |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Sep 28, 2000 at 09:05:52PM -0000, Perl6 RFC Librarian wrote: > =head1 TITLE > > use strict 'objects': a new pragma for using Java-like objects in Perl > =head2 protected > > Just take Conway's RFC 188 and do a s/private/protected/g :-) "protected" is a very loaded term. What you propose to call protected in Perl isn't the same as protected in C++. This will cause confusion. > =head2 private > > Like Conway's private operator defined in RFC 188, but accessing an > hash key or a method that has been marked as private from outside the > defining package should result in a fatal error. What does this buy us? What is the benefit? > =head2 static > Methods not marked as such should return a fatal error if called > directly on the class. Again, where's the benefit? -Scott -- Jonathan Scott Duff [email protected]