[25806] in Perl-Users-Digest
Perl-Users Digest, Issue: 8045 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue May 3 06:05:36 2005
Date: Tue, 3 May 2005 03:05:05 -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, 3 May 2005 Volume: 10 Number: 8045
Today's topics:
Re: [Golf-ish] Ordered hash keys <bart.lateur@pandora.be>
Re: Entirely new idea for a webpage <jurgenex@hotmail.com>
LWP and getting secured documents (justme)
Re: LWP and getting secured documents <mark.clementsREMOVETHIS@wanadoo.fr>
Re: pattern matching dynamic strings w/ regex ending in <flowerysong00@yahoo.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: start_table problem <hackeras@gmail.com>
Re: start_table problem <hackeras@gmail.com>
Re: start_table problem <mark.clementsREMOVETHIS@wanadoo.fr>
Re: start_table problem <hackeras@gmail.com>
why explicit package name required? <geoff.cox@notquitecorrectfreeuk.com>
Re: why explicit package name required? (Anno Siegel)
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 03 May 2005 07:44:50 GMT
From: Bart Lateur <bart.lateur@pandora.be>
Subject: Re: [Golf-ish] Ordered hash keys
Message-Id: <cqae719didvre76p87j4illrtp8r4h8ucg@4ax.com>
Fabian Pilkowski wrote:
>When typing `perldoc -q "keep my hash sorted"` I get:
>
> Found in C:\Programme\Perl\lib\pod\perlfaq4.pod
> How can I always keep my hash sorted?
> You can look into using the DB_File module and tie() using the $DB_BTREE
> hash bindings as documented in "In Memory Databases" in DB_File. The
> Tie::IxHash module from CPAN might also be instructive.
>
>Have a look at this Tie::IxHash from CPAN.
See also Tie::Hash::Indexed, which is an XS implementation.
<http://search.cpan.org/search?module=Tie::Hash::Indexed>
I wish module authors chose their names so it's more obvious what other
modules they're related to.
--
Bart.
------------------------------
Date: Tue, 03 May 2005 06:14:10 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: Entirely new idea for a webpage
Message-Id: <SEEde.5460$db7.1071@trnddc01>
Nikos wrote:
> So, do you mind if i ask simple questions when i get stuck on
> something?
No, not at all.
That is, if you are following the posting guidelines that are posted here
very frequently.
Some rules to remember:
- ask about Perl, not about your Web design, not about your database schema,
not about your cooking book archive.
- make a serious attempt to find the answer in the existing documentation
(man pages and FAQ) and demonstrate that you did so.
- post a minimal, self-contained sample program that exposes your problem
together with an explanation of what the program is supposed to do versus
what you observe.
Then people are usually glad to answer any question, even if it is simple.
jue
------------------------------
Date: 2 May 2005 23:11:21 -0700
From: eight02645999@yahoo.com (justme)
Subject: LWP and getting secured documents
Message-Id: <c0837966.0505022211.7b90b66d@posting.google.com>
hi
i need to connect to a secured server to get a security log file. This
log file
can only be accessed using the software client (GUI) that comes with
the distribution CD. And everytime i used the software to get the
file, it requires me to use a username and password. After that, the
first page is http://securedserver:1010/logs/. So i gathered a little
code in perl to do that automatically. It seems that the software does
not allow ppl to use scripts to get its files, not even ftp or SSH.
Any other suggestions?
thanks
use LWP::UserAgent;
use HTTP::Request::Common qw(POST GET);
use HTTP::Headers;
use LWP::Debug;
$PROXY_URL = 'http://securedserver:1010/';
$TARGET_URL = 'http://securedserver:1010/logs/log.txt'; #the file i
want to get
$PROXYUSER = 'admin';
$PROXYPASS = 'password';
LWP::Debug::level('+') ;
$ua = LWP::UserAgent->new();
$req = HTTP::Request->new(GET => $PROXY_URL);
$req->proxy_authorization_basic($PROXYUSER, $PROXYPASS);
$res = $ua->request($req);
if ($res->is_success) {
print($res->content);
}
else {
print("Something wrong!\n");
}
...
....
the output is:
LWP::UserAgent::new: ()
LWP::UserAgent::request: ()
LWP::UserAgent::send_request: GET http://securedserver:1010/
LWP::UserAgent::_need_proxy: Not proxied
LWP::Protocol::http::request: ()
LWP::Protocol::collect: read 350 bytes
LWP::UserAgent::request: Simple response: OK
<html>
<!-- <h1> Server </h1> -->
<HEAD><TITLE>Some company Co.</TITLE></HEAD>
<BODY>
<CENTER><IMG SRC = "sample.gif"></CENTER>
<P ALIGN=CENTER><I><B>
This server cannot be configured via a web browser.<br>
Use the software that is included on the distribution CD instead.
</B></I></P>
</BODY>
</html>
------------------------------
Date: Tue, 03 May 2005 11:46:56 +0200
From: Mark Clements <mark.clementsREMOVETHIS@wanadoo.fr>
Subject: Re: LWP and getting secured documents
Message-Id: <4277488b$0$813$8fcfb975@news.wanadoo.fr>
justme wrote:
> hi
> i need to connect to a secured server to get a security log file. This
> log file
> can only be accessed using the software client (GUI) that comes with
> the distribution CD. And everytime i used the software to get the
> file, it requires me to use a username and password. After that, the
> first page is http://securedserver:1010/logs/. So i gathered a little
> code in perl to do that automatically. It seems that the software does
> not allow ppl to use scripts to get its files, not even ftp or SSH.
> Any other suggestions?
> thanks
<snip>
> This server cannot be configured via a web browser.<br>
> Use the software that is included on the distribution CD instead.
I take it pretty much the same thing happens if you point a browser at
it directly. The server software will probably be looking for a certain
User-agent string and the presence of various headers, some of which may
be cryptographically generated and so difficult to mock-up. What you
could try doing is setting up a proxy between the GUI and your server so
that you can see exactly what is sent backwards and forwards between
client and server. You *may* then be able to replicate this using LWP.
Try HTTP::Proxy (note I have never used this myself).
Mark
------------------------------
Date: Tue, 03 May 2005 02:36:47 -0400
From: Paul Arthur <flowerysong00@yahoo.com>
Subject: Re: pattern matching dynamic strings w/ regex ending in $ problem
Message-Id: <8b6e71ld46iqvln6bgqjugpp2fpana1r0u@4ax.com>
rader <rader@hep.wisc.edu> wrote:
>I'm seeing a simple, ah, problem with perl 5.8.0...
>
>chive(rader): perl -v | head -2 | tail -1
>This is perl, v5.8.0 built for i386-linux-thread-multi
[paul@linux ~]$ perl -v
This is perl, v5.8.5 built for i386-linux-thread-multi
[paul@linux ~]$ cat rader.pl
#!/usr/bin/perl
use strict;
use warnings;
my $a = 'fuBar';
my $b = 'Bar$';
my $a_new = `echo -n $a`;
my $b_new = `echo -n $b`;
if ( $a_new =~ /$b_new/ ) {
print "match\n";
} else {
print "no match?!\n";
}
>
>chive(rader): ./crud
>no match?!
[paul@linux ~]$ ./crud.pl
match
>Anybody know of a workaround? The code above behaves as expected
>with 5.6.x. Could this actually be a bug?
If it is a bug, it's been fixed.
------------------------------
Date: 03 May 2005 07:22:07 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <4277269f$0$25888$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, 03 May 2005 11:58:21 +0300
From: Nikos <hackeras@gmail.com>
Subject: Re: start_table problem
Message-Id: <d57efc$i0i$1@nic.grnet.gr>
Chris Mattern wrote:
> Post a simple and complete program that is the minimum necessary to
> reproduce the problem. As you have been asked to do MANY, MANY times.
That what i did Chris! I posted the 5-6 lines of code containing the
strt_table that i was having problem with.
--
"Of course I cant stop you. And that would really bum me out
if that were my job. But my job isnt to stop you, its to
make it as difficult as possible, for as many as possible,
for as long as possible ."
------------------------------
Date: Tue, 03 May 2005 12:12:07 +0300
From: Nikos <hackeras@gmail.com>
Subject: Re: start_table problem
Message-Id: <d57f96$ipj$1@nic.grnet.gr>
Fabian Pilkowski wrote:
> * Nikos schrieb:
>
>>Trey Waters wrote:
>>
>>>Just to point out the relevant section from `perldoc CGI`:
>>>
>>> With a few exceptions (described below), start_tag_name
>>> and end_tag_name functions are not generated automatically
>>> when you use CGI. However, you can specify the tags you
>>> want to generate start/end functions for by putting an
>>> asterisk in front of their name, or, alternatively,
>>> requesting either "start_tag_name" or "end_tag_name" in
>>> the import list.
>>>
>>>Funny thing is, the section of the CGI.pm documentation relevant to this
>>>question was found with the FIRST match of searching for "start_table". I
>>>will admit, the text of the paragraph can be a little confusing (esp. if
>>>you're like me, and not the quickest kid on the block), but the example
>>>that follows makes it perfectly clear.
>>>
>>>I will let you figure out how to use perldoc to find the example in the
>>>CGI.pm docs which will show you how to fix your error message. :)
>>
>>Can you beleive that i dont know at all how to use perldoc even how to
>>serach the syntax of print?
>
>
> Well, reading this I understand why you're asking all your annoying
> questions here. You don't know *how* to read the docs.
>
> Hiltherto, you have told you won't read at all. -- Is the time coming
> where you want to read the docs yourself? Hoping this, I'll answer your
> question:
>
> `perldoc` is a program you can call from your console.
>
> To read the docs of one module you have to type `perldoc Module` -- in
> the case of CGI.pm (see above) you just have to type `perldoc CGI` as
> Trey has mentioned in his posting. When looking for some information
> about one of Perl's builtin functions like print(), you have to type
> `perldoc -f print`. All this is done from your console.
>
>
>>i have activestates perl.
>>Can i see the help document in browser somehow or is better in console?
>
>
> Additionally, when using ActiveState's Perl all these informations are
> already available in HTML format. Scout about a subdirectory of Perl's
> install dir (AFAIR, "C:\perl" as default) named "html". This HTML pages
> are using frames: a left one to show a navigation bar and a right one to
> show the information you have choosen in the first. The navigation bar
> begins with some ActiveState stuff, followed by the core docs. When
> scrolling down some lines you see the docs for all installed modules. As
> Sinan has pointed to, there is also a link in your start menu.
>
> Please, have a look at this and try to read it.
>
> regards,
> fabian
Thank you fabian, i really must start to read some docs or else iam
gonna ask for everything.
I must tell you that i was always afriad to look at the docs because i
think that they are complicated and even if i try to find an answer
there for a problem i currently facing it will be very hard to do so.
Anyway, i will try but it hink this will happena gain.
perldoc -f print
what does the -f switch stands for? find maybe?
So for every function i must ask perl to find help for that and for
every module -f is never required?
Also, i often see perl -e 'something'
Is this for trying instantly on console one statement and see directly
the output without having to create a perl prog to do that?
--
"Of course I cant stop you. And that would really bum me out
if that were my job. But my job isnt to stop you, its to
make it as difficult as possible, for as many as possible,
for as long as possible ."
------------------------------
Date: Tue, 03 May 2005 11:30:37 +0200
From: Mark Clements <mark.clementsREMOVETHIS@wanadoo.fr>
Subject: Re: start_table problem
Message-Id: <427744b8$0$811$8fcfb975@news.wanadoo.fr>
Nikos wrote:
> Thank you fabian, i really must start to read some docs or else iam
> gonna ask for everything.
"gonna" as in future tense? Are you *kidding*?
> I must tell you that i was always afriad to look at the docs because i
> think that they are complicated and even if i try to find an answer
> there for a problem i currently facing it will be very hard to do so.
>
> Anyway, i will try but it hink this will happena gain.
>
> perldoc -f print
>
> what does the -f switch stands for? find maybe?
> So for every function i must ask perl to find help for that and for
> every module -f is never required?
>
> Also, i often see perl -e 'something'
>
> Is this for trying instantly on console one statement and see directly
> the output without having to create a perl prog to do that?
>
Read the documentation about the documentation. How to do this is - wait
for it - covered in the *posting guidelines*, which you clearly *still*
haven't read.
perldoc perldoc
will, funnily enough, tell you about perldoc.
perldoc perlrun
will tell you about command-line switches for perl.
perldoc perl
will tell you which set of manpages to look in for documentation on
certain topics.
All of this is documented elsewhere. Nikos: do you really read *nothing*
beyond what is posted here?
You are never going to modify your approach, are you? I may have to
abandon reading this newsgroup: there is little point in killfiling you
because you generate so much traffic (most of it pointing out the error
of your ways to you, *none* of which you listen to) I'll see your posts
anyway.
Mark
------------------------------
Date: Tue, 03 May 2005 12:46:49 +0300
From: Nikos <hackeras@gmail.com>
Subject: Re: start_table problem
Message-Id: <d57haa$kjl$1@nic.grnet.gr>
Mark Clements wrote:
> All of this is documented elsewhere. Nikos: do you really read *nothing*
> beyond what is posted here?
I didnt even read the book i bought Perl- How to Program by Deitel.
> You are never going to modify your approach, are you? I may have to
> abandon reading this newsgroup: there is little point in killfiling you
> because you generate so much traffic (most of it pointing out the error
> of your ways to you, *none* of which you listen to) I'll see your posts
> anyway.
No please that wouldnt be fair.
You will NOT abandon reading this fine ng as well getting helped and
help others because of me.
I'am the one that doesnt read the docs and causing too much traffic
because i cant deal with the singlest problem i encounter.
I cause problem, and i ahve to go, not you.
I know i never gonan be a Perl Programmer because i dont have enouph
strengh of reading the docs and also i am a very unpatient persom.
When i enounter a problem i want it to be solved rigth away but i dont
know how to fix it or read soemthing that will talk about it, not 100
other stuff before i get to what i am looking for, i hate that.
The past few days i asked a huge amoutn of questions because i needed
help of correcting my perl cgi script that i run from my local
webserver. I just wanne get this fixed and nothing more.
I'am not going to ask forever. Maybe very rarely when something bothers
me ill ask. Now i have css problems as well, the perl is ok. i just cant
get some part of my website to look exactly as i want them.
I'am willing to read the docs but *only* that part that it *will* answer
my questions, not other general stuff, so the problem will be quickly fixed.
Anyway, please do not let those hard endless days that i was asking here
for almost about everything scare you and go away.
I 'll leave aa=nd maybe once in a while(rarely) i'll ask somethign specific.
Sorry for the trouble.
--
"Of course I cant stop you. And that would really bum me out
if that were my job. But my job isnt to stop you, its to
make it as difficult as possible, for as many as possible,
for as long as possible ."
------------------------------
Date: Tue, 03 May 2005 08:16:48 GMT
From: Geoff Cox <geoff.cox@notquitecorrectfreeuk.com>
Subject: why explicit package name required?
Message-Id: <jhce71l7s7j3vl7qru85qisu20oth8o9pq@4ax.com>
Hello,
I get the warning that the global symbol (re $picnumber on last line
below) requires explicit package name - I am not clear why. If I
remove the # from the first line that value of $picnumber is used on
the last line shown below.
What am I missing here?
Geoff
# my $picnumber = 20;
find sub {
if (-d $_) {
if ($_ eq "location") {
$picnumber = 20;
}
return;
}
line which uses $picnumber
------------------------------
Date: 3 May 2005 08:23:37 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: why explicit package name required?
Message-Id: <d57ce9$9r1$1@mamenchi.zrz.TU-Berlin.DE>
Geoff Cox <geoff.cox@notquitecorrectfreeuk.com> wrote in comp.lang.perl.misc:
> Hello,
>
> I get the warning that the global symbol (re $picnumber on last line
> below) requires explicit package name - I am not clear why. If I
> remove the # from the first line that value of $picnumber is used on
> the last line shown below.
>
> What am I missing here?
>
> Geoff
>
> # my $picnumber = 20;
>
> find sub {
>
> if (-d $_) {
>
> if ($_ eq "location") {
> $picnumber = 20;
> }
>
> return;
>
> }
>
> line which uses $picnumber
perldoc -f my. Also see "strict vars" in perldoc strict.
Anno
------------------------------
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 8045
***************************************
