RFC: Automatic accessors for hash-based objects

2000-08-26 Thread James Mastros
It appears that the RFC Librarian doesn't work weekends, so I'm going to post this directly. Hopefuly, it doesn't have any glaringly obvious errors... =head1 TITLE Automatic accessors for hash-based objects =head1 VERSION Maintainer: James Mastros <[EMAIL PROTECTED]&g

Re: RFC: Automatic accessors for hash-based objects

2000-08-26 Thread James Mastros
On Sat, Aug 26, 2000 at 08:24:19PM -0500, Dave Rolsky wrote: > This is an interesting idea. I would think that ideally it would be > combined with pre-declared limited keyspace hashes (which we currently > have in a semi-crippled way with pseudohashes). This seems like a fairly orthagonal thing

Re: RFC: Automatic accessors for hash-based objects

2000-08-27 Thread James Mastros
iple levels and tried > to use ':access' on both of them, simply issue a "subroutine > DEFAULT_DIR() redefined at line..." warning. > > $self->{CONFIG}->{DEFAULT_DIR} : access, constant = '/usr/bin'; > $self->{STATE}->{DEFAULT_DIR

Re: RFC 171 (v1) my Dog $spot should call a constructor implicitly

2000-08-30 Thread James Mastros
has semi-magical properties. 2) We clearly define that basic types will always m/^[A-Z]+$/. This makes it such that we have to say my INT $n, but that's quite consistant with the rest of perl. (It also makes it so that all-uppercase module names without any colons might behave oddly. This is bad for CGI, but if it becomes WWW::CGI, then it's all OK...) -=- James Mastros