[23035] in Perl-Users-Digest
Perl-Users Digest, Issue: 5255 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Jul 22 06:05:50 2003
Date: Tue, 22 Jul 2003 03:05:07 -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, 22 Jul 2003 Volume: 10 Number: 5255
Today's topics:
cwd with Net::SFTP (Inna)
Re: How to match all characters in a Character Class <jimbo@soundmiges.co.uk>
Re: Larry W... out of work ?? Impossible... or... <REMOVEsdnCAPS@comcast.net>
Re: lookaround (debraj)
Re: Multiple object types in a single .pm? <REMOVEsdnCAPS@comcast.net>
Re: Multiple object types in a single .pm? (trwww)
Re: perlio problem? redhat 9, perl 5.8.0 <Use-Author-Address-Header@[127.1]>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: recompile Perl, with new function names ? news@roaima.freeserve.co.uk
SELECT mit Parametern: Problem <ERadermacher@skynet.be>
Re: SELECT with parameters: a bug ?? <ERadermacher@skynet.be>
Re: Using SMTP through a proxy server news@roaima.freeserve.co.uk
Re: Why is 'last' not allowed here <abigail@abigail.nl>
Re: <bwalton@rochester.rr.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 22 Jul 2003 00:34:08 -0700
From: innaga@amdocs.com (Inna)
Subject: cwd with Net::SFTP
Message-Id: <31f98008.0307212334.1cfdaaf4@posting.google.com>
There is an option to use 'cwd' with the Net::FTP. How can I perform
this action with the SFTP (I didn't find it in the info pages of
Net::SFTP)?
Thanks
------------------------------
Date: Tue, 22 Jul 2003 09:44:12 +0100
From: jimbo <jimbo@soundmiges.co.uk>
Subject: Re: How to match all characters in a Character Class
Message-Id: <1058863461.425761@ananke.eclipse.net.uk>
Eric Schwartz wrote:
> Er, no, 'them' is the entries in the character classes, not the
> classes themselves.
The program below should do what you want.
jimbo
;-)
#!/usr/bin/perl
use strict;
use warnings;
my $pat = '[aeiou\s\W]'; # looking for consonants
my $text = join "", <DATA>;
$text = "$text";
my @class_members = map { split //; }
split /$pat/i, $text;
# The 'i' modifier makes the split case insensitive
print join ":", @class_members;
__END__
The row over the death of Dr David Kelly has focused on how the
scientist's name came to be made public during the dispute over Iraqi
weapons which ultimately led to his death.
Defence Secretary Geoff Hoon was accused by several newspapers on
Tuesday of allowing Dr Kelly to be named as a "mole".
The Financial Times said Mr Hoon had approved a media strategy whereby
the Ministry of Defence would confirm Dr Kelly's name to journalists
if they suggested it.
------------------------------
Date: Tue, 22 Jul 2003 04:54:11 -0500
From: "Eric J. Roode" <REMOVEsdnCAPS@comcast.net>
Subject: Re: Larry W... out of work ?? Impossible... or...
Message-Id: <Xns93C03C06BCEEEsdn.comcast@206.127.4.25>
-----BEGIN xxx SIGNED MESSAGE-----
Hash: SHA1
stuseven@hotmail.com (stu7) wrote in
news:d7dd90b0.0307211916.2feb9d1b@posting.google.com:
> +
> ...or is it ?
You expect a serious answer, when you flamed the hell out of me for trying
to be helpful? Ha.
- --
Eric
$_ = reverse sort qw p ekca lre Js reh ts
p, $/.r, map $_.$", qw e p h tona e; print
-----BEGIN xxx SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBPx0Jt2PeouIeTNHoEQJ+6ACgvjPLXIojFkkyNUdYzzMKkIzeza0AoKNF
nLuSiu+QEkPO8A/+yhdBfT8F
=xnF+
-----END PGP SIGNATURE-----
------------------------------
Date: 22 Jul 2003 02:05:35 -0700
From: debhatta@hotmail.com (debraj)
Subject: Re: lookaround
Message-Id: <f9f243e.0307220105.5d51c098@posting.google.com>
Hi
Thanx I have got it ...Installed perl 5.8.0 and things are fine
tadmc@augustmail.com (Tad McClellan) wrote in message news:<slrnbggba0.g09.tadmc@magna.augustmail.com>...
> debraj <debhatta@hotmail.com> wrote:
>
> > I am new to perl
>
>
> You should use the docs that _came with_ your version of perl,
> else what you see may not work with the version that you
> actually have available to you.
>
>
> > /the (\S+)(?{ $color = $^N }) (\S+)(?{ $animal = $^N })/i;
>
>
> > Sequence (?{...) not recognized at.....
> >
> > I took it from this link :
> >
> > http://www.perldoc.com/perl5.8.0/pod/perlre.html
> ^^^^^
> ^^^^^
>
> Do you _have_ perl version 5.8.0?
>
> If you use the docs that came with your perl, then you will see
> only those features that you can use with your perl.
------------------------------
Date: Tue, 22 Jul 2003 04:52:27 -0500
From: "Eric J. Roode" <REMOVEsdnCAPS@comcast.net>
Subject: Re: Multiple object types in a single .pm?
Message-Id: <Xns93C03BBBF33E9sdn.comcast@206.127.4.25>
-----BEGIN xxx SIGNED MESSAGE-----
Hash: SHA1
Bernie Cosell <bernie@fantasyfarm.com> wrote in
news:o97phvs6ev0bdjh4sk4uvr8ci60sgdmset@library.airnews.net:
> I have two very closely related classes that I'd like to implement in
> a single .pm. I realize that the usual setup is that if you're going
> to do "use Type", that the file better be called "Type.pm" and you
> need to have "package Type" in there... I looked through our
> site_perl and toot, but I didn't see anything that quite addressed
> this.
>
> The thing is that the two classes are related [and will, indeed, share
> some "cross class variables"] and I think it'd be cleaner to have both
> in a single .pm file, but I'm not sure on the right syntax [much less
> idioms] to get new, import, Exporter, etc... to all work.
>
> I can do it brute force, and maybe that's the best I can do:
>
> Class1.pm:
> package Class1
> sub import { Class1a::import();
> Class1b::import();
> }
If they are object classes, why do you need Exporter? Why do you need an
import subroutine?
To answer your other question, yes you can have two or more object
classes in a single file, and the way you laid it out is pretty much how
to do it.
- --
Eric
$_ = reverse sort qw p ekca lre Js reh ts
p, $/.r, map $_.$", qw e p h tona e; print
-----BEGIN xxx SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBPx0JUWPeouIeTNHoEQK8KgCgipdwadwJogLnJytIhDoDenX1pukAoP3G
xeNdr2BJe9ikf15c2qXk4Xl5
=MNUw
-----END PGP SIGNATURE-----
------------------------------
Date: 22 Jul 2003 02:58:06 -0700
From: toddrw69@excite.com (trwww)
Subject: Re: Multiple object types in a single .pm?
Message-Id: <d81ecffa.0307220158.13677ce7@posting.google.com>
Bernie Cosell <bernie@fantasyfarm.com> wrote in message news:<o97phvs6ev0bdjh4sk4uvr8ci60sgdmset@library.airnews.net>...
> I have two very closely related classes that I'd like to implement in a
> single .pm. I realize that the usual setup is that if you're going to do
> "use Type", that the file better be called "Type.pm" and you need to have
> "package Type" in there... I looked through our site_perl and toot, but I
> didn't see anything that quite addressed this.
>
> The thing is that the two classes are related [and will, indeed, share some
> "cross class variables"] and I think it'd be cleaner to have both in a
> single .pm file, but I'm not sure on the right syntax [much less idioms] to
> get new, import, Exporter, etc... to all work.
>
> I can do it brute force, and maybe that's the best I can do:
>
> Class1.pm:
> package Class1
> sub import { Class1a::import();
> Class1b::import();
> }
>
It pretty much works like one ( or at least I ) would expect. You are
right about the first part. The use() basically changes the ::'s to /
and adds .pm to its argument, and looks for that file in @INC. But the
packages defined therein do not have to correspond to the filename in
any way:
[trwww@waveright perl]$ cat > MyClasses.pm
package MyClass::TypeA;
sub new {
my($class) = shift();
return( bless( { }, $class ) );
}
package MyClass::TypeB;
sub new {
my($class) = shift();
return( bless( { }, $class ) );
}
1;
Ctrl-D
[trwww@waveright perl]$ perl
use MyClasses;
my($objA) = MyClass::TypeA->new();
my($objB) = MyClass::TypeB->new();
print( ref( $objA ), "\n" );
print( ref( $objB ), "\n" );
Ctrl-D
MyClass::TypeA
MyClass::TypeB
HTH,
Todd W.
------------------------------
Date: Tue, 22 Jul 2003 02:45:59 -0700
From: Muttley <Use-Author-Address-Header@[127.1]>
Subject: Re: perlio problem? redhat 9, perl 5.8.0
Message-Id: <200307220945.h6M9jxEV015999@www.aarg.net>
In article <2369e2ad.0306240806.142022a9@posting.google.com>
gordon@ockham.be (gordon) wrote:
>
>
> I'm having some problems running a bit of legacy perl code on a newly
> installed redhat 9. With the perl 5.8.0 that comes with redhat 9, the
> match against the string literal works, the match against the same
> string read from a file fails.
Gordon,
I think you have saved me from possible insanity!
I've been trying to isolate a problem with an INN News Server running
on Redhat9. There is a reporting tool called innreport that fails on
my system as the line read is not caught by a regex. If I define it
as a string literal, then the line is processed quite correctly.
This is on an out-of-the-box installation.
It seems that Redhat 9 certainly does have a fairly serious bug.
------------------------------
Date: Tue, 22 Jul 2003 02:22:48 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <85KdnW54XfPVe4GiXTWJkw@august.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.4 $)
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.
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
"Jeopardy" (because the answer comes before the question), or
"TOFU".
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, 22 Jul 2003 09:38:10 +0100
From: news@roaima.freeserve.co.uk
Subject: Re: recompile Perl, with new function names ?
Message-Id: <io9vu-cf4.ln1@moldev.cmagroup.co.uk>
stu7 <stuseven@hotmail.com> wrote:
> Is there a way to recomplile Perl with new names
> for functions ? (...or better, probably, including the
> regular names with the replacement names... so original
> functions are still there to make old scripts work :)
Why recompile? Take a look at the prototyping examples from "perldoc
perlsub".
Chris
--
@s=split(//,"Je,\nhn ersloak rcet thuarP");$k=$l=@s;for(;$k;$k--){$i=($i+1)%$l
until$s[$i];$c=$s[$i];print$c;undef$s[$i];$i=($i+(ord$c))%$l}
------------------------------
Date: Tue, 22 Jul 2003 10:18:32 +0200
From: "Erwin Radermacher" <ERadermacher@skynet.be>
Subject: SELECT mit Parametern: Problem
Message-Id: <3f1cf34e$0$262$ba620e4c@reader0.news.skynet.be>
Help, an alle,
Bin ein Newbie in Perl.
Habe eine Datenbank unter Visual Foxpro 6.0 genannt Patwin
Unter Perl ActivePerl Win32 5.8.0806, Treiber DBI::ODBC installiert mit ppm,
OS: Windows XP Prof
Code arbeitet gut wenn die Parameterangabe = 2003 hart einkodiert ist.
aber gibt kein Resultat wenn
$krit = 2003;
...
später
...
$sth->execute($krit);
und im SELECT ... WHERE YEAR(geb)>=? gesetzt wird.
<CODE>
#!/usr/bin/perl
use DBI;
open (OUT,">Kinder.txt");
print "\n";
@row = ();
$dbh = DBI->connect('DBI:ODBC:Patwin',"","") or die "Keine Verbindung mit
Patwin";
#$krit = 2003 ;
# arbeitet nicht korrekt;
$sth = $dbh->prepare("SELECT TRIM(Name) As Nom,Vorname,Ort,Telefon, geb FROM
Patwin WHERE YEAR(geb)=2003 ORDER BY 1,2");
$sth->execute();
while(@row = $sth->fetchrow_array)
{
print OUT "@row\n";
}
close OUT;
</CODE>
Was mache ich falsch ?
Erwin Radermacher
ERadermacher@skynet.be
------------------------------
Date: Tue, 22 Jul 2003 10:32:10 +0200
From: "Erwin Radermacher" <ERadermacher@skynet.be>
Subject: Re: SELECT with parameters: a bug ??
Message-Id: <3f1cf680$0$284$ba620e4c@reader0.news.skynet.be>
I'am newbie in Perl
I'm searching to extract some tables in VFP 6.0
Myystem: Windows XP Prof
ActivePerl Win32 5.8.0806
driver DBI::ODBC installed with ppm
Prgramm is working
wenn the parameter = 2003 is given in the source code
but it gives no result with
coding
$krit = 2003;
# and then
$sth->execute($krit);
and SELECT ... WHERE YEAR(geb)>=?
<CODE>
#!/usr/bin/perl
use DBI;
open (OUT,">Kinder.txt");
print "\n";
@row = ();
$dbh = DBI->connect('DBI:ODBC:Patwin',"","") or die "no connection with
table Patwin";
#$krit = 2003 ;
# does not work
$sth = $dbh->prepare("SELECT TRIM(Name) As Nom,Vorname,Ort,Telefon, geb FROM
Patwin WHERE YEAR(geb)=2003 ORDER BY 1,2");
$sth->execute();
while(@row = $sth->fetchrow_array)
{
print OUT "@row\n";
}
close OUT;
</CODE>
What am I doing wrong ?
Erwin Radermacher
ERadermacher@skynet.be
------------------------------
Date: Tue, 22 Jul 2003 09:28:37 +0100
From: news@roaima.freeserve.co.uk
Subject: Re: Using SMTP through a proxy server
Message-Id: <l69vu-cf4.ln1@moldev.cmagroup.co.uk>
Mario542 <member17678@dbforums.com> wrote:
> Does anyone know how to run NET::SMTP through a corporate proxy server
> to a SMTP server on the Internet??
> This proxy only allows HTTP.
You don't.
More specifically, you can't talk SMTP over an HTTP proxy without
encapsulating it. Once you've done that you then need something on the
"other side" to un-encapsulate it, by which time you might as well have
not bothered.
Have you spoken to your corporate system administrators (either
informally, or via the appropriate route) to see whether they can
help you?
Chris
------------------------------
Date: 22 Jul 2003 07:26:47 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: Why is 'last' not allowed here
Message-Id: <slrnbhpppn.pkh.abigail@alexandra.abigail.nl>
Ronald Fischer (ronaldf@eml.cc) wrote on MMMDCXII September MCMXCIII in
<URL:news:219750c.0307212225.2238600@posting.google.com>:
)) Abigail <abigail@abigail.nl> wrote in message news:<slrnbhcv5t.53v.abigail@a
)) > Ronald Fischer (ronaldf@eml.cc) wrote on MMMDCVII September MCMXCIII in
)) > <URL:news:219750c.0307170227.2cff1f13@posting.google.com>:
)) > %% "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de> wrote in messag
)) > %% > That's because the blocks of 'if', 'unless' and 'do' (missed one?)
)) > %% > aren't treated as a block that is subject to 'last' or 'next'.
)) > %%
)) > %% The strange thing is that the manpages explain that 'do' can't be
)) > %% used, but they tell nothing about if. Just the contrary: They say
)) > %% that, WRT blocks, 'if' behaves like a loop ('while', 'for').
)) >
)) > Which manual page is that?
))
)) It is
))
)) http://www.perldoc.com/perl5.8.0/pod/perlsyn.html#Basic-BLOCKs-and-Switch-St
))
)) where it says:
))
)) "A BLOCK by itself (labeled or not) is semantically equivalent to a
^^^^^^^^^
)) loop that executes once. Thus you can use any of the loop control
)) statements in it to leave or restart the block. (Note that this is NOT
)) true in eval{}, sub{}, or contrary to popular belief do{} blocks,
)) which do NOT count as loops.)"
))
)) Interestingly, http://www.perldoc.com/perl5.8.0/pod/perlsyn.html#Loop-Contro
)) seems to say the contrary, as I found out right now:
))
)) "The loop control statements don't work in an if or unless, since they
)) aren't loops."
))
)) These two sentences can be true at the same time only if what goes
)) after an 'if'
)) or an 'unless' were NOT a block:
))
)) if (CONDITION)
)) {
)) # are we in a block here?
)) }
))
)) But I think this *must* be a block, because you can declare
)) my-variables
)) inside it.
It's a block, but your first quote says "A block BY ITSELF". A block
belonging by an if isn't a block by itself.
)) So I would say that the man pages are in error, because they are
)) contradicting.
)) Right?
Wrong.
Abigail
--
srand 123456;$-=rand$_--=>@[[$-,$_]=@[[$_,$-]for(reverse+1..(@[=split
//=>"IGrACVGQ\x02GJCWVhP\x02PL\x02jNMP"));print+(map{$_^q^"^}@[),"\n"
------------------------------
Date: Sat, 19 Jul 2003 01:59:56 GMT
From: Bob Walton <bwalton@rochester.rr.com>
Subject: Re:
Message-Id: <3F18A600.3040306@rochester.rr.com>
Ron wrote:
> Tried this code get a server 500 error.
>
> Anyone know what's wrong with it?
>
> if $DayName eq "Select a Day" or $RouteName eq "Select A Route") {
(---^
> dienice("Please use the back button on your browser to fill out the Day
> & Route fields.");
> }
...
> Ron
...
--
Bob Walton
------------------------------
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.
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 5255
***************************************
