[32162] in Perl-Users-Digest
Perl-Users Digest, Issue: 3427 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Jun 28 09:09:25 2011
Date: Tue, 28 Jun 2011 06:09:06 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 28 Jun 2011 Volume: 11 Number: 3427
Today's topics:
Re: doing fiddly processing on repeated matches <hjp-usenet2@hjp.at>
Re: Module to check overlap? <ela@yantai.org>
Re: Module to check overlap? <tzz@lifelogs.com>
Re: open letter to Sherm Pendley about ShuX <sherm.pendley@gmail.com>
Re: open letter to Sherm Pendley about ShuX <blgl@stacken.kth.se>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: read small file, get array of hashes? [newbie] <jimsgibson@gmail.com>
Re: read small file, get array of hashes? [newbie] <tadmc@seesig.invalid>
Re: read small file, get array of hashes? [newbie] <jimsgibson@gmail.com>
Re: read small file, get array of hashes? [newbie] <jwkrahn@example.com>
utf-8 of a string <dn.perl@gmail.com>
Re: utf-8 of a string <hhr-m@web.de>
Re: WebOs - Perl Question <sherm.pendley@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 28 Jun 2011 11:18:00 +0200
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: doing fiddly processing on repeated matches
Message-Id: <slrnj0j728.hki.hjp-usenet2@hrunkner.hjp.at>
On 2011-06-27 21:14, Jürgen Exner <jurgenex@hotmail.com> wrote:
> bugbear <bugbear@trim_papermule.co.uk_trim> wrote:
>>I'm trying to come up with an elegant solution, but am falling foul of
>>my search terms being common.
>>
>>I am attempting to process some XML, in particular, I want to
>>manipulate each opening tag.
>
> Parse the XML, do your manipulation in the syntax tree, and write the
> XML back out.
>
>>I have the "obvious" match to apply to my large xml string:
>>
>> while($s =~ m@(<\s*[^\?][^>]+>)@gm) {
>> }
>
> "Obvious" as in simple-minded? REs are not powerful enough to parse a
> non-regular language like XML.
If you don't care about matching begin and end tags (and about stuff
that normally only occurs in DTDs, like element declarations) then it's
regular. Or in other words, you can build a SAX-like parser with only
REs and a loop, but not one which produces something like a DOM.
So for the purposes of the OP REs would be sufficient (he looks at each
start tag in isolation), but the RE is too simple. Writing an RE which
does it right is not trivial, so if this is production code (and not a
learning exercise) I agree that he should just use an existing XML
parser.
hp
------------------------------
Date: Tue, 28 Jun 2011 12:40:45 -0700
From: "ela" <ela@yantai.org>
Subject: Re: Module to check overlap?
Message-Id: <iubica$onk$1@ijustice.itsc.cuhk.edu.hk>
"Ted Zlatanov" <tzz@lifelogs.com> wrote in message
news:87sjqv85bd.fsf@lifelogs.com...
> OK, so your in-memory inversion list will be
>
> (1 1001 2000 3001 2500 3501 ...)
>
> Do you see the pattern? You're saying "from 1 to 1000 is yes, 1001 to
> 1999 is no, 2000 to 3000 is yes, 3001 to 2499 is no..."
>
> A million integers in memory should not be too bad, less than 20
> megabytes I'd guess. Perl lists don't have a big overhead. But you can
> pack the numbers in a more compact format if memory usage is a problem.
> Try it.
>
> e> Query file, 10k records
> e> 3\t2200
> e> 5000\t62344
> e> 77778\t132313
> e> ...
>
> Same pattern.
>
> So then the intersection of the two inversion lists (going with
> http://www.perlmonks.org/?node_id=908453 since it explains it well) is
> just the negation of the union of the individual negations.
>
> Negation, as that page explains, is easy: remove the leading 0 or add a
> leading 0 if there isn't one.
>
> Adding a new range to a list (to compute the union) is pretty simple
> too; let us know if you have trouble writing it.
>
> Ted
Your explanation and reference have helped me think and formulate my problem
systematically. Now I understand the difficulty of my problem...
1) Input data amount and heterogeneity
As shown in the above example, (1 1001 2000 3001 2500 3501 ...) makes
binary search fail as the range itself is overlapping. So the speed may
become slow. Second some "ranges" are points indeed, although we can make
them "range", e.g. 303 -> 303,303
2) Overlapping status
overlap can be complete and partial. It seems that inversion list
(including the unions and intersections) does not handle this scenario
3) Statistics and identity
I need to collect the set of those completely/partially overlapped items
and to retrieve the overlapping points etc. Then I can take some statistics
about the overlapps, e.g. number (though this is easy to do)
So my question is: "Have inversion lists already taken care of the above
problems?" If no, that means I have to develop on my own and for the sake of
this newsgroup, I'd better give up.
------------------------------
Date: Tue, 28 Jun 2011 06:36:30 -0500
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Module to check overlap?
Message-Id: <8739iuqjb5.fsf@lifelogs.com>
On Tue, 28 Jun 2011 12:40:45 -0700 "ela" <ela@yantai.org> wrote:
e> 1) Input data amount and heterogeneity
e> As shown in the above example, (1 1001 2000 3001 2500 3501 ...) makes
e> binary search fail as the range itself is overlapping. So the speed may
e> become slow.
I don't understand what will fail when the two lists are overlapping.
What, functionally, are you trying to do with the data?
By the way, binary searches don't work with inversion lists. You have
to search from the beginning. This actually is quite fast on modern
CPUs compared to a regular binary search, but it's algorithmically
slower so for large ranges you may want to search only rarely, when
needed.
e> Second some "ranges" are points indeed, although we can make them
e> "range", e.g. 303 -> 303,303
Sure. Inversion lists are inefficient for "checkerboard" patterns,
e.g. the set of all the odd numbers. They are efficient when your data
has long runs of adjacent numbers.
e> 2) Overlapping status
e> overlap can be complete and partial. It seems that inversion list
e> (including the unions and intersections) does not handle this
e> scenario
Inversion lists are data structures, they don't handle the overlap on
their own. You need to define what you want to happen when they
overlap: do you want to merge them, search them separately, exclude one
from the other? This is what I mean above by "functionally, what are
you trying to do?"
e> 3) Statistics and identity
e> I need to collect the set of those completely/partially overlapped items
e> and to retrieve the overlapping points etc. Then I can take some statistics
e> about the overlapps, e.g. number (though this is easy to do)
The set of "completely overlapping" points is the union of your two
inversion lists.
The set of "partially overlapping" points is the intersection of your
two inversion lists.
Think of your problem as a set problem, not as operations on ranges.
Your database ranges and the inversion lists we build from them are just
representations of the underlying truth. So in terms of sets and set
membership, what are you missing?
Ted
------------------------------
Date: Mon, 27 Jun 2011 22:40:05 -0400
From: Sherm Pendley <sherm.pendley@gmail.com>
Subject: Re: open letter to Sherm Pendley about ShuX
Message-Id: <m2mxh2el16.fsf@sherm.shermpendley.com>
jaialai.technology@gmail.com writes:
> First, I love he fact that I can use "ShuX" like I did 10+ years ago
> with MacPerl!
> My request: Back in the day when ShuX would open a small sound file
> would play. Some hickish voice saying "Awww Shucks!". I am feeling
> a bit of nostalgia here but could you bring that back?
It was never in ShuX - maybe you're thinking of the original Shuck that
came with MacPerl?
> Maybe leave it as an option (off by default?) for people
> with a bit of nostalgia?
It's an easy enough thing to add... I'll see if I can track down the
original sound file.
sherm--
------------------------------
Date: Tue, 28 Jun 2011 12:21:08 +0200
From: Bo Lindbergh <blgl@stacken.kth.se>
Subject: Re: open letter to Sherm Pendley about ShuX
Message-Id: <iuc9ui$tf1$1@speranza.aioe.org>
In article <m2mxh2el16.fsf@sherm.shermpendley.com>,
Sherm Pendley <sherm.pendley@gmail.com> wrote:
> It's an easy enough thing to add... I'll see if I can track down the
> original sound file.
I have it on hand here in case you can't find it.
/Bo Lindbergh
------------------------------
Date: Tue, 28 Jun 2011 02:16:55 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <sIydnXVsqf964pTTnZ2dnUVZ5hSdnZ2d@giganews.com>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
Date: Mon, 27 Jun 2011 15:43:39 -0700
From: Jim Gibson <jimsgibson@gmail.com>
Subject: Re: read small file, get array of hashes? [newbie]
Message-Id: <270620111543396733%jimsgibson@gmail.com>
In article
<ddbdc213-72f7-403f-9091-cb183dcaff4a@p31g2000vbs.googlegroups.com>,
gry <georgeryoung@gmail.com> wrote:
> [perl newbie] I need to read a small flat file like:
> #testname #dbname #duration(hours) #wipe_db
> #schema_dir
> backup_restore backup_restore 6 no
> vbr
> elastic_cluster elastic_cluster 48 no
> ElasticCluster
> create_delete_seq create_delete_seq 0.5 yes
> ddl_something
> ...
>
> and get some kind of data object so I can:
> 1) find the next test in sequence after a given test_name (or
> indication of end_of_tests)
> 2) get the dbname, duration, wipe, or schema for a given test_name
>
> I tried:
> use warnings;
> use strict;
> my $test_suites_file = $ENV{'TEST_SUITES_FILE'} || 'test_suites';
You are interspersing statements with subroutines. I always like to
collect all subroutines together, usually at the end, unless the
subroutines are short (1-3 lines).
> sub read_suites_file
> {
> die 'wrong number of args' if(@_ != 1);
> my @tests = ();
> my($file_name) = $_[0];
You have a list of variables on the left and a single scalar on the
right. Perl will figure it out, but it is better to assign lists/arrays
to arrays:
my( $file_name ) = @_;
It also makes it easier to add more arguments:
my( $file_name, $arg2 ) = @_;
instead of
my( $file_name, $arg2 ) = ( $_[0], $_[1] );
>
> open my $suites_file, "< $file_name" or die "Can't open stress
> suites file \"$file_name\": $!";
You are using the 2-argument version of open. It is better to use the
3-argument version (and I always use parentheses to make clear what
elements belong to open and what do not):
open( my $suites_file, '<', $file_name ) or
die "Can't open stress suites file \"$file_name\": $!";
> while(<$suites_file>) {
You are using the default variable. For complex code, you should use
and explicit variable:
while( my $line = <$suites_file>) {
> next if m"^\s*(#|$)";
You are unnecessarily using an alternate regexp delimiter. Others will
find that hard to read.
next if $line =~ /\s*(#|$)/;
> chomp;
> my ($test,$dbname,$duration,$wipe_db,$schema_dir) = split;
> push @tests, {test=>$test, dbname=>$dbname, duration=>$duration,
> wipe_db=>$wipe_db, schema_dir=>$schema_dir};
> }
> close($suites_file);
> return @tests
> }
>
> my @tests = read_suites_file($test_suites_file);
> my %test = $tests[1];
Rainer told you what your error here is. I would print results this way:
for my $hashref ( @tests ) {
my %test = %$hashref;
print "dbname is $test{dbname}\n";
}
> print 'dbname of tests[1]=', $test{'dbname'};
Double-quote interpolation is usually better than string concatenation.
You don't need the single-quotes in the hash key, as Perl will
interpret a bare-word hash key as a string.
--
Jim Gibson
------------------------------
Date: Mon, 27 Jun 2011 19:22:22 -0500
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: read small file, get array of hashes? [newbie]
Message-Id: <slrnj0i792.po8.tadmc@tadbox.sbcglobal.net>
Jim Gibson <jimsgibson@gmail.com> wrote:
> In article
><ddbdc213-72f7-403f-9091-cb183dcaff4a@p31g2000vbs.googlegroups.com>,
> gry <georgeryoung@gmail.com> wrote:
>> print 'dbname of tests[1]=', $test{'dbname'};
>
> Double-quote interpolation is usually better than string concatenation.
Yes it is, but there is no string concatenation there...
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
Date: Mon, 27 Jun 2011 17:34:22 -0700
From: Jim Gibson <jimsgibson@gmail.com>
Subject: Re: read small file, get array of hashes? [newbie]
Message-Id: <270620111734226512%jimsgibson@gmail.com>
In article <slrnj0i792.po8.tadmc@tadbox.sbcglobal.net>, Tad McClellan
<tadmc@seesig.invalid> wrote:
> Jim Gibson <jimsgibson@gmail.com> wrote:
> > In article
> ><ddbdc213-72f7-403f-9091-cb183dcaff4a@p31g2000vbs.googlegroups.com>,
> > gry <georgeryoung@gmail.com> wrote:
>
> >> print 'dbname of tests[1]=', $test{'dbname'};
> >
> > Double-quote interpolation is usually better than string concatenation.
>
>
> Yes it is, but there is no string concatenation there...
Ah, yes. I misread the comma as a period!
--
Jim Gibson
------------------------------
Date: Mon, 27 Jun 2011 23:58:23 -0700
From: "John W. Krahn" <jwkrahn@example.com>
Subject: Re: read small file, get array of hashes? [newbie]
Message-Id: <kYeOp.16423$xh5.11440@newsfe02.iad>
Tad McClellan wrote:
> Jim Gibson<jimsgibson@gmail.com> wrote:
>> In article
>> <ddbdc213-72f7-403f-9091-cb183dcaff4a@p31g2000vbs.googlegroups.com>,
>> gry<georgeryoung@gmail.com> wrote:
>
>>> print 'dbname of tests[1]=', $test{'dbname'};
>>
>> Double-quote interpolation is usually better than string concatenation.
>
>
> Yes it is, but there is no string concatenation there...
No _explicit_ string concatenation there...
Using print implies that the list will be concatenated together before
output to the default filehandle.
John
--
Any intelligent fool can make things bigger and
more complex... It takes a touch of genius -
and a lot of courage to move in the opposite
direction. -- Albert Einstein
------------------------------
Date: Tue, 28 Jun 2011 02:19:28 -0700 (PDT)
From: "dn.perl@gmail.com" <dn.perl@gmail.com>
Subject: utf-8 of a string
Message-Id: <9a507adc-048c-4c4b-a8f1-e109c7d97b32@h25g2000prf.googlegroups.com>
I am asking part one of my questions here because I do not know where
else to ask it.
I have been sent a string in some language whose alphabet
is not known to me. How can I find utf-8 representation
of this string?
Part two of my doubts is related to perl. But I haven't really got
around to grappling with it because right now, part one is an obstacle
to me.
The next step in part two would be to read a CLOB field in a database,
and grep it in a perl script to check whether the above string appears
in it. I can read this CLOB field and write it to an excel sheet, and
the excel sheet shows the CLOB data to me. I would like to check
whether this CLOB data contains the string which has been sent me.
Is there any forum-FAQ or code where I can find some answers/pointers
to my questions?
Please advise.
------------------------------
Date: Tue, 28 Jun 2011 11:41:04 +0200
From: Helmut Richter <hhr-m@web.de>
Subject: Re: utf-8 of a string
Message-Id: <alpine.LNX.2.00.1106281127350.5090@lxhri02.ws.lrz.de>
On Tue, 28 Jun 2011, dn.perl@gmail.com wrote:
> I am asking part one of my questions here because I do not know where
> else to ask it.
> I have been sent a string in some language whose alphabet
> is not known to me. How can I find utf-8 representation
> of this string?
This can hardly be answered without knowing what kind of alphabet or code
the data is. For converting, there are ready-made tools (e.g. recode), but
programming your own in perl using the module Encode is not difficult, and
is more adaptable to the ideosyncrasies of your data which may not exactly
adhere to one code. Before you can use Encode reasonably, you must have
understood the difference between characters and bytes in perl, which is
explained in perlunitut.
> Is there any forum-FAQ or code where I can find some answers/pointers
> to my questions?
> Please advise.
Formerly, there was comp.std.internat dealing, among other things, with
such issues. Due to very little traffic, the group has been closed down by
the usenet bigwigs, so there is no longer an appropriate group AFAIK.
Could you make one of your files publicly accessible (e.g. Web) and tell
here shortly what the problem is? It will be off-topic here, but if the
thread remains short it is less of a nuisance than longish discussions
where it should go.
--
Helmut Richter
------------------------------
Date: Mon, 27 Jun 2011 22:52:27 -0400
From: Sherm Pendley <sherm.pendley@gmail.com>
Subject: Re: WebOs - Perl Question
Message-Id: <m2iprqekgk.fsf@sherm.shermpendley.com>
"E.D.G." <edgrsprj@ix.netcom.com> writes:
> Questions: Can Perl programs using any of the ActiveState versions of
> Perl be written for use on the new HP TouchPad computer that runs the
> WebOs 3.0 operating system?
Seeing as how neither the TouchPad nor WebOS 3.0 has been released yet,
I'm guessing the answer is "no."
Seeing as how all of HP's advance marketing material speaks of HTML5
and other client-side "Web 2.0" technology, I'm guessing the answer will
still be "no" when it does ship. You *might* be able to pry off the lid
and get at the *nix stuff under the hood, but I suspect it won't be as
easy as using HP's preferred tools.
sherm--
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 3427
***************************************
