is trying to be object
oriented then export nothing. If it's just a collection of
functions then @EXPORT_OK anything but use @EXPORT with
caution.
Cheers.
--
William Wueppelmann
Electronic Systems Specialist
Canadian Institute for Historical Microreproductions (CIHM)
hough the stylesheet rules do seem to include a lot of 'or'
clauses in them. I don't know how complex your input files and
transformations are compared to mine, or how fast your computer is, but
96 seconds to process 1.5 MB does seem a little slow compared to what I
am getting.
I hope some of that helps.
--
William Wueppelmann
Electronic Systems Specialist
Canadian Institute for Historical Microreproductions (CIHM)
http://www.canadiana.org
2462708
bacon-new-1072751992
^D
or
echo "plato-cratylus-1072532262
plato-charmides-1072462708
bacon-new-1072751992" | foo.pl
Either that, or supply all data on the command line, and use the
backticks method as Michael suggests. Mixing the two conventions might
lead to confusion later o
py of card
numbers and guest ids, you might be able to see if you can reproduce the
bug using the older data set to see if it is, perhaps, the interaction
of a code bug with some new data.
--
William Wueppelmann
Electronic Systems Specialist
Canadian Institute for Historical Microreproductions (
ements, where each element is the
text inside the <> delimiters, you could do this:
# Get rid of everything up to and including the first "<"
$keyword =~ s/^.*?" to the end of the line
$keyword =~ s/>[^>]*$//;
# We now have fields delimited by "><",
t startup, it defaults to running in vi-compatible
mode, so another thing to check might be if you have a .vimrc file on
the system that displays the characters but lack one on the other.)
I don't know if this will solve the problem for you, but that's where I
would start looking.
Ch
