perl-unicode

Re: ANNOUNCE: Unicode::Collate::allkeys v 3.1.1.1

2003-05-16 19:30:06
Yes, when I coded this I made the module export a subroutine one could
call to get the file.  This builds the string using File::Spec->catfile.

I saw nothing in your code that forbids a subdirectory in the table
path.  In fact your code would allow things like ../../ to be passed,
but I don't think that is a problem.

The sample usage is now:
--
use Unicode::Collate::Standard::V3_1_1;
use Unicode::Collate;
 
my $col = Unicode::Collate->new(table => 3_1_1_COLLATION);
--

I have put the complete bundle at:
  http://www.limey.net/~fiji/perl/Unicode-Collate-Standard-V3_1_1-0.1.tar.gz

            -ben

On Sat, May 17, 2003 at 10:34:53AM +0900, SADAHIRO Tomoyuki wrote:

On Thu, 15 May 2003 20:19:09 -0400
Ben Bennett <fiji(_at_)ayup(_dot_)limey(_dot_)net> wrote:

Then the user of U::C can simply specify the dependency as
U::C::Data::v3_1_1 (or whatever version they need) and then they can
specify the file using the table parameter to U::C->new().

e.g.:

U::C->new(table => "Standard/v3_1_1.txt");

Then if this were part of an installable bundle they can require a
dependency on U::C::Standard/v3_1_1.

I think this is cleaner, we don't have to worry about what they have
done to the default allkeys.txt.

A path separator is not always '/', that depends on file system.
(cf. L<perlport/"files_and_filesystems"> and L<File::Spec>)
I hesitate to use a (relative) pathname instead of a filename
as a value for the 'table' key.
(So I say in POD that C< table => $filename, >)

SADAHIRO Tomoyuki