Re: Re: Module submission Text::MessageLibrary

[John Clyman]

The module's purpose is to let developers centralize text strings (which may contain placeholders to be filled in at run time) in one location instead of keeping them in string literals scattered throughout the code. So instead of the typical:

open FILE, $filename or die "Couldn't open..."

you could write something like:

open FILE, $filename or die $message->open_failed($filename)

brian, you suggested perhaps Class::* in a previous message, but that seems like emphasizing what is essentially syntactic sugar to make the calling interface friendly. (Really all the latter statement above is doing is something that in procedural code would read something like "construct_message('open_failed', $filename)".)

When I originally looked at CPAN to see if anything like this existed, I found myself gravitating to the String::* and Text::* sections. Thus my inclination to put it in one of those.

The "Library" suffix wasn't intended in the sense of "module", but in the sense of a set of text/string resources to draw upon. Perhaps "List" would have been a better choice. Or maybe I need to avoid nouns describing the data class encapsulates and find one that describes its function. String::Manager?

I could just be in a deep rut here and unable to think creatively about what to call this thing. I'm certainly open to alternative suggestions.

John Clyman

-----Original Message-----
From: _brian_d_foy [mailto:comdog@;panix.com]
Sent: Wednesday, October 30, 2002 5:04 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Module submission Text::MessageLibrary


In article <[EMAIL PROTECTED]>, Perl Authors Upload Server <[EMAIL PROTECTED]> wrote:

> The following module was proposed for inclusion in the Module List:
>
> modid: Text::MessageLibrary

why do you think this belongs in Text?

also, the "Library" is implied since it's a module.

--
brian d foy (one of many PAUSE admins), http://pause.perl.org
please send all messages back to [EMAIL PROTECTED]