I'd much prefer ::Identify.
I'm starting to agree with your idea :-)
jac
--
Jose' Alves de Castro
First of all, thanks for your opinion :-)
If it's simple to remove the data for each language to a config and use identical
logic for all languages, that's usually the way to go.
The logic (at least initially) will be the same for each and every language.
There's also a combination of the
* [EMAIL PROTECTED] [EMAIL PROTECTED] [2004-02-26 17:29]:
I'm putting together some things I have and creating a module
named Lingua::Identification.
Just a comment on the name: personally, I'd much prefer
::Identify. It's half as long, says exactly the same thing, and
it feels less awkward to
Hi,
[EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
One possibility would be to force each known language to become a module
(Lingua:Identification::EN for English, etc)... the downside of this
solution is that once I have 50 languages, I'll have 51 modules... :-|
1 or 100, it doesn't
Hi, everybody.
I'm in need of advice here...
I'm putting together some things I have and creating a module named
Lingua::Identification. I won't go through details on why should this
module be created or anything else (unless someone asks me too) since
that has already been done (though not
On Thu, Feb 26, 2004 at 04:27:22PM +, [EMAIL PROTECTED] wrote:
One possibility would be to force each known language to become a module
(Lingua:Identification::EN for English, etc)... the downside of this
solution is that once I have 50 languages, I'll have 51 modules... :-|
Still, CPAN
