[25245] in Perl-Users-Digest
Perl-Users Digest, Issue: 7490 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Dec 7 09:05:42 2004
Date: Tue, 7 Dec 2004 06:05:07 -0800 (PST)
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, 7 Dec 2004 Volume: 10 Number: 7490
Today's topics:
Re: FAQ 2.15: Archives of comp.lang.perl.misc (Anno Siegel)
Re: How to handle a HTTP::Request with gzip, deflate he <leifwessman@hotmail.com>
HTML2JPEG (katja)
New comp.lang.perl.misc mirror site at lampforums.org <mcgucken@jollyroger.com>
Perl open(). Inserting data into a file dshan@web.de
Re: Perl open(). Inserting data into a file <jurgenex@hotmail.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Printing Data usinf Perl to an HTML does not work w <jurgenex@hotmail.com>
Re: Question on loops and return values (Anno Siegel)
Re: RegExp Help (Anno Siegel)
Re: Regular expression weirdness with upper and lower c <jurgenex@hotmail.com>
Re: vbscript or perl <chbarts+usenet@gmail.com>
Re: XML-Parser: dealing with predefined entities <ferragina@di.unipi.it>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 7 Dec 2004 08:32:01 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: FAQ 2.15: Archives of comp.lang.perl.misc
Message-Id: <cp3pq1$63q$1@mamenchi.zrz.TU-Berlin.DE>
brian d foy <comdog@panix.com> wrote in comp.lang.perl.misc:
> In article <2aj5r0hl3filtu40147b0hql5um1q5e75j@4ax.com>, Michele Dondi
> <bik.mido@tiscalinet.it> wrote:
>
> > On Sat, 4 Dec 2004 13:54:45 -0500, "Matt Garrish"
> > <matthew.garrish@sympatico.ca> wrote:
>
> > >Might do good to post this one in high rotation! (i.e., every day... : )
>
> > More seriously I *think* that the PerlFAQ Server's currently just
> > randomly selects the FAQ entry to post. I also think that in this
> > respect the selection algorithm should be made to work more on a
> > shuffling base,
>
> It could be. :)
>
> the source is in the perlfaq CVS repository if you care to take
> a crack at it.
>
> http://cvs.perl.org/viewcvs/cvs-public/perlfaq/
This has come up time and again...
I'm working on it, expect a patch soonish.
Anno
------------------------------
Date: 7 Dec 2004 03:44:18 -0800
From: "Leif Wessman" <leifwessman@hotmail.com>
Subject: Re: How to handle a HTTP::Request with gzip, deflate headers
Message-Id: <1102419858.478806.321100@c13g2000cwb.googlegroups.com>
Gisle Aas wrote:
> "Leif Wessman" <leifwessman@hotmail.com> writes:
>
> > $res->decoded_content now returns the decoded content for webpages
with
> > Content-Encoding: gzip. However, when Content-Encoding is 'deflate'
I
> > get empty content. The website I'm testing on is Amazon.fr (they
use
> > deflate) so I guess the problem is in my code. Should it work with
> > deflate automatically?
>
> Yes, the code is there, but I have not actually tried it on a site
> that use 'deflate' yet. Can you give my an URL to try?
>
> --
> Gisle Aas
Sure. I tried this page:
http://www.amazon.fr/exec/obidos/ASIN/0136609112/t/
------------------------------
Date: 7 Dec 2004 05:38:14 -0800
From: katja_zina@web.de (katja)
Subject: HTML2JPEG
Message-Id: <ea4aa88f.0412070538.26657e3d@posting.google.com>
How can I convert an Internet-page to a PDF/JPEG-file from a
Perl-script under Linux? (I would like to make a screenshot from a
command line).
Thank you
Katja
------------------------------
Date: Tue, 7 Dec 2004 04:32:54 -0500
From: astro <mcgucken@jollyroger.com>
Subject: New comp.lang.perl.misc mirror site at lampforums.org
Message-Id: <astro.1gw0x5@lampforums.org>
Hello all,
We have set up new linux, apache, mysql, python, perl, and php forums
at http://lampforums.org .
comp.lang.perl.misc is at: http://lampforums.org/forumdisplay.php?f=19
The interface allows your posts to appear immediately on the forums,
and also to private message other users.
Your posts will appear on the usenet too.
We've also started a number of forums devoted to popular LAMP
applications such as oscommerce, cafelog, postnuke, phpnuke, gallery,
coppermine, and more, for which there aren't any specific usenet
groups.
Please let us know if you'd like to see any more.
The LAMP forums include:
alt.apache.configuration
comp.lang.perl.misc
comp.lang.php
comp.lang.python
comp.os.linux.hardware
comp.os.linux.misc
comp.os.linux.networking
comp.os.linux.setup
mailing.database.mysql
The LAMP application forums include:
LAMP Open Source Portals
Drupal Geeklog Mambo Open Source PHP-Nuke phpWCMS phpWebS
Open Source LAMP Content Management Systems
CMS, Postnuke, PHPnuke, Drupal, Mambo
Open Source LAMP Ecommerce
Oscommerce, Zen Cart, CubeCart
Open Source LAMP Wiki
phpwiki, tikiwiki.org
LAMP Open Source Photo Management
Gallery, Coppermine
Open Source LAMP Mailing Lists
phplist
Open Source LAMP Blogs
b2evolution Nucleus pMachine Free WordPres
Open Source LAMP Forums / Bulletin Boards: phpBB2, SMF, phorum
phpBB2 SMF phorum
LAMP Open Source CMS Polls: Advanced Poll , phpESP, PHPSurveyor
Advanced Poll phpESP PHPSurveyor
Please let us know what other forums/features you would like to see at
http://lampforums.org .
mcgucken@authena.org
--
astro
------------------------------------------------------------------------
astro's Profile: http://lampforums.org/member.php?userid=1
View this thread: http://lampforums.org/showthread.php?t=92721
------------------------------
Date: 7 Dec 2004 05:39:19 -0800
From: dshan@web.de
Subject: Perl open(). Inserting data into a file
Message-Id: <1102426759.295717.264980@z14g2000cwz.googlegroups.com>
Hi all!
I'm a Perl newbie. My question is: how do I insert data contained in
$string at a certain position in a file? I tried to use
open(OUT,"+< $out") or die "Can't read/write $out: $!";
while(<OUT>) {
if($_ =~ /<add_here \/>/s) { print OUT $string; }
}
to insert new data into an XML file which looks like this:
<?xml version="1.0" encoding="Windows-1251"?>
<disc>
<info>Some Info</info>
<info>Some Info 2</info>
...
<add />
</disc>
but on update it prints the following:
<?xml version="1.0" encoding="Windows-1251"?>
<disc>
<info>Some Info</info>
<info>Some Info 2</info>
...
<add_here />
</disc>
<?xml version="1.0" encoding="Windows-1251"?>
<disc>
<info>Some Info 1</info>
<info>Some Info 2</info>
...
<add_here />
</disc>
<info>Some Info 3</info>
that is, it appends the preceding data and the new data ($string) at
the end of the file. Why? I just want to add new text at the <add_here>
position...
Regards,
dshan
------------------------------
Date: Tue, 07 Dec 2004 13:51:47 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: Perl open(). Inserting data into a file
Message-Id: <Tzitd.2782$wb7.305@trnddc03>
dshan@web.de wrote:
> I'm a Perl newbie. My question is: how do I insert data contained in
> $string at a certain position in a file? I tried to use [...]
Your Question is Asked Frequently, please see 'perldoc -q "insert a line"':
"How do I change one line in a file/delete a line in a file/insert a
line in the middle of a file/append to the beginning of a file?"
jue
------------------------------
Date: 07 Dec 2004 08:22:28 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <41b56843$0$27767$8b463f8a@news.nationwide.net>
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.5 $)
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://mail.augustmail.com/~tadmc/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
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_group_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 <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Tue, 07 Dec 2004 13:47:12 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: Printing Data usinf Perl to an HTML does not work with large amount of data
Message-Id: <Avitd.2758$wb7.2746@trnddc03>
islamabadi@yahoo.com wrote:
> have a perl code that is connecting to Oracle DB and retrieving data.
> I am currently experiencing the following issues:
>
> After data is reterieved if I try to output a HTML table by using the
> following code, the web browser displays data okay for say about 20
> records. But if I have more than twenty records the web browser almost
> never completes.
I am unclear about if you have a problem with your web browser or with the
Perl script.
Is the generated HTML code what you expect it to be? If yes, then you will
have to look outside of Perl.
If no, then please tell us what you expect it to be and what you actually
get and how the two are different.
> print "<table cellspacing=10>\n";
> while ( my @row = $sth->fetchrow_array() ) {
>
> print "<TR>";
> for ($i=0; $i <= $#row; $i++) {
> print "<TD>$row[$i]</TD>";
Gack! Why not a simple
for (@row) {
print "<TD>$_</TD>";
> }
> print "</TR>\n";
> }
>
> If I try to output just the data as follows:
>
> while ( my @row = $sth->fetchrow_array() ) {
> for ($i=0; $i <= $#row; $i++) {
> print "<TD>$row[$i]</TD>";
> }
> }
>
> It works faster but still does not return all the data. That is it
> outputs 50% of the data, and the web browser then keeps working but
> never retrieves more data.
You are mixing two problem domains. A web browser is not the right test tool
for Perl output. Get your problem space separated corrrectly. Does your Perl
program generate the desired output, i.e. does it generate the desired HTML
code? If yes, then obviously you don't have a Perl problem.
If no, then analyse your Perl program without all the additional obstacles
like CGI, HTTP, proxies, web browser, etc. by looking at the plain HTML
output.
> There is some buffer when Perl outputs to html.
Perl does not output to HMTL. It outputs to STDOUT or some other user
defined file handle.
jue
------------------------------
Date: 7 Dec 2004 12:29:44 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Question on loops and return values
Message-Id: <cp47no$d7l$2@mamenchi.zrz.TU-Berlin.DE>
Tad McClellan <tadmc@augustmail.com> wrote in comp.lang.perl.misc:
> delfuego <djcameron60616@yahoo.com> wrote:
[...]
> > $grate = eval { ($gvalue / $last) * 100 }; # growth rate percentage
>
>
> Can you tell us why you are using eval() there?
It's probably a misguided way of saying
$grate = ($gvalue / $last) * 100 if $last;
Anno
------------------------------
Date: 7 Dec 2004 11:57:08 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: RegExp Help
Message-Id: <cp45qk$d7l$1@mamenchi.zrz.TU-Berlin.DE>
BigDaDDY <ihatespam@hotmail.com> wrote in comp.lang.perl.misc:
> Andrew,
>
> My bad..I did want 25.010 to be converted to 25.01. Nice catch.
>
> How does this change the regexp you provided?
"I mis-stated my question, so I can't use your reply. Send another."
Have you even made an attempt to correct it yourself?
[TOFU snipped]
Anno
------------------------------
Date: Tue, 07 Dec 2004 13:35:10 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: Regular expression weirdness with upper and lower case
Message-Id: <ikitd.2697$wb7.2577@trnddc03>
wmreinemer@tns.net wrote:
> You are right, It is a regex issue.
>
> to search for a *.jpg and *.png try
>
> grep *.[jp][pn]g
Are you sure you want to include *.jng and *.ppg in your list of matching
file extensions, too?
> to include search for upper and lower case in the extension:
> grep *.[JjPp][PpNn][Gg]
I would rather use the /i option.
From "perldoc perlop":
Options are:
[...]
i Do case-insensitive pattern matching.
jue
------------------------------
Date: Tue, 07 Dec 2004 05:39:16 -0700
From: Chris Barts <chbarts+usenet@gmail.com>
Subject: Re: vbscript or perl
Message-Id: <W5udnYnv8tXrOSjcRVn-1w@onewest.net>
David wrote:
> Dear all,
>
> I have to port a moderately complicated unix shell script written for
> Solaris to Windows. I've never done Windows scripting before. Should I
>
> (a) learn VBScript and implement it in that;
> (b) install Active Perl on the target Windows box and rewrite the script in
> perl (which I am familiar with).
If you know Perl, write it in Perl. That much is a no-brainer. Trying to
learn a new language by porting a real program to it is usually not a
good way to write clean, maintainable code.
Installing Active Perl is trivial compared to learning a new language,
in both time and effort.
>
> The script in question most does database stuff e.g. calls stored procs,
> parses text files then loads new records with bcp.
In that case, Perl is the best way to go. Search through CPAN to find a
couple modules to help with the database and text processing.
------------------------------
Date: 7 Dec 2004 04:19:51 -0800
From: "pferrax" <ferragina@di.unipi.it>
Subject: Re: XML-Parser: dealing with predefined entities
Message-Id: <1102421991.143676.147240@c13g2000cwb.googlegroups.com>
Eric Bohlman wrote:
>It's *not* called when an entity
> *reference* is encountered in the document; those are expanded
> transparently (though the process involves a call to the ExternEnt
> handler if the entity was declared external).
Sorry, what about avoiding this expansion ? May I turn off the
"expander" and push the entity name to the default handler ?
I'd like to do not manage both internal and external
entities but treat them as normal text chars (via e.g. the Default
handler).
Many thanks, Paolo
------------------------------
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:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#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 V10 Issue 7490
***************************************
