Re: Module submission Readonly

2003-01-08 Thread Eric Roode

In article <[EMAIL PROTECTED]>, brian d foy wrote:
>> The following module was proposed for inclusion in the Module List:
>>
>>   modid:   Readonly
>
>>   similar:
>> constant
>
>i don't have a problem with this name, but should it be a pragma
>instead of a "normal" module?

I don't think so, because pragmas generally control the compilation
environment rather than the runtime environment, and one of the
features of Readonly is that you can make a variable read-only with a
value computed at runtime.  Pragmas also generally have a blanket
effect on the program ("use constant" is an exception), and don't
introduce functions as Readonly does.

I'm not closed to the idea; it just doesn't seem to me that a pragma
is a good fit for this.  I do plan to experiment with attributes,
something like "my $foo : Readonly ('somevalue');", but at this point
I don't have any idea whether that'll work well or not.

-- 
Eric J. Roode  [EMAIL PROTECTED]
Senior Software Engineer, Myxa Corporation
tr j, j ,j for @japh = (qw b lre h, uJ p, ekca tona, ts reh b, $/.r);
print scalar reverse sort @japh;



Re: Adopting Regexp-Common-time

2017-02-22 Thread Eric Roode
Done.
--Eric


On Mon, Feb 20, 2017 at 12:14 AM, Gabor Szabo  wrote:

> Hi there,
>
> Mohammad Anwar has agreed to continue the maintenance of this module.
> As I am only a co-maintainer I cannot give him any rights on PAUSE.
> Could you, please, make MANWAR co-maintainer as well?
>
> regards
>Gabor
>
>
> > On Wed, Nov 20, 2013 at 12:27 PM, brian d foy 
> wrote:
> >>
> >> Gabor is now a co-maintainer.
>


Module submission Constant::

2002-03-15 Thread Eric Roode


I wish to rescind the following namespace request.  It seemed like a
good idea, but when I tested under Windows, case-insensitive filenames 
got in the way. "use Constant" is equivalent to "use constant" under
Windows (and for all I know, some other platforms).

I have renamed the module to Readonly.pm, and will upload it under
that name, and will redo the namespace registration under that name.

I apologize for any trouble this has caused.

Eric J. Roode


Perl Authors Upload Server writes:
 > 
 > The following module was proposed for inclusion in the Module List:
 > 
 >   modid:   Constant::
 >   DSLIP:   bdprp
 >   description: Create read-only scalars, arrays, hashes.
 >   userid:  ROODE (Eric J. Roode)
 >   chapterid:2 (Perl_Core_Modules)
 >   communities:
 > RPI lily server
 > 
 >   similar:
 > "use constant" pragma
 > 
 >   rationale:
 > 
 > Perl's built-in pragma creates only scalars and lists, creates
 > variables that have no leading $ character, and which cannot be
 > interpolated into strings. Also, it works only at compile time.
 > 
 > Constant.pm, on the other hand, will work with global variables and
 > with lexical ("my") variables. It will create scalars, arrays, or
 > hashes, all of which look and work like normal, non-constant Perl
 > variables.
 > 
 > Constant.pm uses tied variables, so it has a performance penalty as
 > compared to "use constant", but I believe it makes a valuable
 > complement to the pragma.
 > 
 >   enteredby:   ROODE (Eric J. Roode)
 >   enteredon:   Thu Mar  7 20:03:19 2002 GMT
 > 
 > The resulting entry would be:
 > 
 > Constant::bdprp Create read-only scalars, arrays, hashes.ROODE



 --
 Eric J. Roode[EMAIL PROTECTED]
 Senior Software Engineer, Myxa Corporation
 perl -lpe "(($0 =~ '/' ? ($_ = $0 ) =~ s!\.?/!?$!:$@;~~@@~~~NO CARRIER



Re: Module submission Chess

2002-03-22 Thread Eric Roode


 > The following module was proposed for inclusion in the Module List:
 >  modid:   Chess
 >  DSLIP:   adpOg
 >  description: Manipulate and Validate a chess board
 >  userid:  BJR (Brian Richardson)
 >  chapterid:   23 (Miscellaneous_Modules)
 >  communities:
 >Perl-Chess mailing list @ Yahoo!Groups
 >
 >  similar:
 >Meta::Chess
 >
 >  rationale:
 >There are currently 3 people who are working on things chess
 >related. A mailing list has been opened, and further CPAN
 >development on things Chess is expected in the next while. Chess is
 >a large enough that it warrants its own namespace, especially since
 >there is already 3 levels of nesting (cf. Chess::Piece::Pawn), and
 >there is no existing namespace that really describes chess very
 >well.

1) Have you looked at Games::Chess?

2) I'd hate to see a new top-level for Chess, for Go, for Backgammon,
for Pente, for Poker, etc, etc, etc.  I recognize that you have a
fairly deep hierarchy, but you still should consider putting it under
the Games top-level, imho.

Just my two cents' worth...

 --
 Eric J. Roode[EMAIL PROTECTED]
 Senior Software Engineer, Myxa Corporation
 perl -lpe "(($0 =~ '/' ? ($_ = $0 ) =~ s!\.?/!?$!:$@;~~@@~~~NO CARRIER



Request for new author ID.

2001-03-01 Thread Eric Roode

Dear PAUSE maintainers,

I would like to register as a CPAN author. I have created three
modules that, imho, have some degree of usefulness to the wider perl
community.

The first is a tied hash module, Hash::Strict, that allows
programmers to restrict a hash's keys to a limited set of alowed
values. This is very useful for people who use a hash to represent a
database record or other encapsulated sort of object (a very common
use of hashes), where it is important not to accidentally refer to an
invalid field or member name simply because of a typo. (Perl, of
course, provides no validation of hash keys).

The second is a trivial tied hash module, Hash::Insensitive, to
allow the programmer to refer to a hash's keys in a case-insensitive
manner. $hash{FOO} is equivalent to $hash{foo}. Although it is trivial,
I have had need for such a module (for manipulating HTML attributes),
so why should anyone else have to reinvent the same wheel.

The third is a robust class for creating and manipulating HTML
tables.


I have found nothing on CPAN that resembles the first two modules.
The third, however, is redundant with the existing HTML::Table module.
I believe my module has a much more robust internal data representation,
and I like my interface better, but I am in contact with the maintainer
of HTML::Table.pm and am trying to decide whether it is better to roll
the two together or whether they make more sense as separate modules.


None of these three modules has been announced to the wider Perl
community. I have discussed them with the programming community on
RPI's 'lily' server, and at least a couple programmers have been using
one or more of these modules for a little while now.  I consider all
of these modules to be "beta" software for the time being.


Current versions of these modules may be found at:

Hash::Strict  http://employeeweb.myxa.com/eric/hs/
Hash::Insensitive http://employeeweb.myxa.com/eric/hi/
HTML::TableManip  http://employeeweb.myxa.com/eric/tm/


My name is Eric J. Roode.
My email address is [EMAIL PROTECTED]
I do not have a public homepage.
I would like a CPAN userid of 'roode'.
If 'roode' is not available, then 'e-roode'.

Here's the DSLI info for the modules:

Name  DSLI  Description  Info
-    -
Hash::Strict  bdpO  Create key-limited "strict hashes".  roode
Hash::Insensitive bdpO  Create hashes with case-insensitive keys.roode
HTML::TableManip  bdpO  Create and manipulate HTML tables.   roode


Thank you very much,

 --
 Eric J. Roode[EMAIL PROTECTED]
 Senior Software Engineer, Myxa Corporation