[24594] in Perl-Users-Digest
Perl-Users Digest, Issue: 6770 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Jul 6 09:05:51 2004
Date: Tue, 6 Jul 2004 06: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, 6 Jul 2004 Volume: 10 Number: 6770
Today's topics:
Re: Cleanup file path <ymartin@nospam.fr>
Re: Digest::Base HELP! <root@slate.comm.ad.roke.co.uk>
Re: equality test for multiple variables (Anno Siegel)
Re: equality test for multiple variables <gnari@simnet.is>
Re: equality test for multiple variables <Eugene.Mikheyev@kiev.com.com.ua>
Re: equality test for multiple variables (Anno Siegel)
Re: equality test for multiple variables <Joe.Smith@inwap.com>
Homer & Marge having sex with Bart Simpson <glowthat@xxx-adult-toons.com>
How to fetch new line from cgi textarea object <roman@sky.lviv.ua>
Re: How to fetch new line from cgi textarea object <Eugene.Mikheyev@kiev.com.com.ua>
Re: How to fetch new line from cgi textarea object <roman@sky.lviv.ua>
Math::BigFloat oddities (Peter J. Acklam)
Re: Nonblocking Pipe Open <Joe.Smith@inwap.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
User Currently logged on to the local system (Aqua)
Why use dollar sign $ for variables <dwmail@gmx.net>
Re: Why use dollar sign $ for variables <peter@semantico.com>
Re: Why use dollar sign $ for variables <richard@zync.co.uk>
Re: Why use dollar sign $ for variables <tadmc@augustmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 06 Jul 2004 12:15:16 +0200
From: Yves Martin <ymartin@nospam.fr>
Subject: Re: Cleanup file path
Message-Id: <f6vfh1a1cb.fsf@pcyma.elca.ch>
pjacklam@online.no (Peter J. Acklam) writes:
> It's not guaranteed to be wrong. For instance, it won't be wrong
> if the symlink is to a directory within the same directory as the
> symlink.
>
> So the problem isn't that it is guaranteed to fail, but that it
> isn't guaranteed to succeed. Of course, that is hardly any
> better.
Thank you for your help.
In fact, my perl script is supposed to read build system
configuration files (generated and read in Java) and to provide
Emacs JDEE project files (prj.el)
The source configuration files have known constraints (relative path
and no symbolic links at that level - but perhaps out of the build
system) and the prj.el supports "~/" but not ../ or ./ in path. Here
is the complete story.
--
Yves Martin
------------------------------
Date: Tue, 06 Jul 2004 10:54:08 +0100
From: root <root@slate.comm.ad.roke.co.uk>
Subject: Re: Digest::Base HELP!
Message-Id: <pan.2004.07.06.09.54.03.959078@slate.comm.ad.roke.co.uk>
On Mon, 05 Jul 2004 17:26:15 +0100, root wrote:
> Sorry for my ignornance, but I need to install the Digest::Base CPAN
> module into the default Perl 5.8.0 install of RH9.0 to satisfy some
> dependancies, but cannot obviously work out how to do it (there is no
> Makefile.PL).
>
> Can anyone help me with this. It's pretty urgent.
>
> Thanks
>
> Tony
Yes, I am running as root. Not good I know. This was a very quick
post from a development box.
Anyway, if I run perl -MCPAN -e 'install Digest::Base' I get the following
message back
CPAN: Storable loaded ok
Going to read /root/.cpan/Metadata
Database was generated on Mon, 05 Jul 2004 02:05:12 GMT
Warning: Cannot install Digest::Base, don't know what it is.
Try the command
i /Digest::Base/
to find objects with matching identifiers.
Any other recommendations?
Thanks
------------------------------
Date: 6 Jul 2004 09:38:54 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: equality test for multiple variables
Message-Id: <ccdrve$1oo$1@mamenchi.zrz.TU-Berlin.DE>
Eugene Mikheyev <Eugene.Mikheyev@kiev.com.com.ua> wrote in comp.lang.perl.misc:
> > > use List::Util ;
> > >
> > > min( $a, $b, $c, $d, $e ) == max( $a, $b, $c, $d, $e ) ;
> >
> > I expect that you meant to post this instead:
> >
> > minstr( $a, $b, $c, $d, $e ) eq maxstr( $a, $b, $c, $d, $e ) ;
> >
>
> You really think this is more elegant? And, of course, this is fast...
Elegant? It's about correct vs. incorrect.
Anno
------------------------------
Date: Tue, 6 Jul 2004 09:33:10 -0000
From: "gnari" <gnari@simnet.is>
Subject: Re: equality test for multiple variables
Message-Id: <ccdrh6$59b$1@news.simnet.is>
"Matt Garrish" <matthew.garrish@sympatico.ca> wrote in message
news:J_pGc.14982$JG5.481220@news20.bellglobal.com...
> Just curious if anyone has a more elegant way to check whether multiple
> values are equal. For example, given:
>
> $a = $b = $c = $d = $e = 'test';
>
> is there anything better than:
>
> if ( ($a eq $b) && ($b eq $c) && ($c eq $d) && ($d eq $e) ) { ... }
>
> It would be nice (cleaner) if you could simply test if $a eq $b eq $c eq
$d,
> but that obviously won't work.
if you know that the strings do not contain say, ':', you can use:
if ("$a:"x4 eq "$b:$c:$d:$e:") {...}
gnari
------------------------------
Date: Tue, 6 Jul 2004 13:07:21 +0300
From: "Eugene Mikheyev" <Eugene.Mikheyev@kiev.com.com.ua>
Subject: Re: equality test for multiple variables
Message-Id: <ccdtp1$25ut$1@news.univ.kiev.ua>
> Elegant? It's about correct vs. incorrect.
Don't get me wrong. One of them has mistyped, other one has corrected his
mstake, but in general, my statement was something like "this test for
equality is even less <elegant> as Matt's"
------------------------------
Date: 6 Jul 2004 10:47:57 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: equality test for multiple variables
Message-Id: <cce00t$4hm$1@mamenchi.zrz.TU-Berlin.DE>
Matt Garrish <matthew.garrish@sympatico.ca> wrote in comp.lang.perl.misc:
> Just curious if anyone has a more elegant way to check whether multiple
> values are equal. For example, given:
>
> $a = $b = $c = $d = $e = 'test';
>
> is there anything better than:
>
> if ( ($a eq $b) && ($b eq $c) && ($c eq $d) && ($d eq $e) ) { ... }
>
> It would be nice (cleaner) if you could simply test if $a eq $b eq $c eq $d,
> but that obviously won't work.
A hash can do it:
my %h;
@h{ $a, $b, $c, $d, $e} = ();
if ( keys %h == 1 ) { ... }
This doesn't need an external module, but Uri's suggestion using List::Util
is about twice as fast.
Anno
------------------------------
Date: Tue, 06 Jul 2004 11:36:17 GMT
From: Joe Smith <Joe.Smith@inwap.com>
Subject: Re: equality test for multiple variables
Message-Id: <R8wGc.33155$Oq2.24599@attbi_s52>
Eugene Mikheyev wrote:
>>>use List::Util ;
>>>
>>>min( $a, $b, $c, $d, $e ) == max( $a, $b, $c, $d, $e ) ;
>>
>>I expect that you meant to post this instead:
>>
>>minstr( $a, $b, $c, $d, $e ) eq maxstr( $a, $b, $c, $d, $e ) ;
>
> You really think this is more elegant? And, of course, this is fast...
No, I was pointing out that the OP use 'eq' (to compare strings) as
opposed to '==' (to compare numbers), therefor min()==max() was not
the correct answer.
-Joe
------------------------------
Date: Tue, 06 Jul 2004 12:49:46 GMT
From: Orgasmic <glowthat@xxx-adult-toons.com>
Subject: Homer & Marge having sex with Bart Simpson
Message-Id: <KdxGc.22234$vO1.116441@nnrp1.uunet.ca>
Plus i got movies of Bart making Lisa Simpson PREGNANT
Before it gets shut down, get it now: http://www.ToonToon.com///ximpsons
Then you could visit Http://WWW.comicsORGY.com////simpsons for
extra pics of Bart and Maggie touching their privates.
Then you could visit http://www.xxx-Adult-Toons.COM/simpsons for
xtra intimate scenes of Bart and Lisa masturbating together.
Home <soonLisa@xxx-adult-toons.com> wrote in message
news:QsEov7uv32XYhDGUbY5@xxx-adult-toons.com...
>
> climbed into them and they leaned back onto the bed in a
>
>
> pe419aa
------------------------------
Date: Tue, 06 Jul 2004 12:29:53 +0300
From: "Roman Khutkyy" <roman@sky.lviv.ua>
Subject: How to fetch new line from cgi textarea object
Message-Id: <opsaplz3pwbibonh@192.168.0.6>
Hi all,
The problem. User fills the form that includes the textarea object. He/she
fills the textarea with "Enter" key to start new line. Later this
information stores in database and will be shown in formatted HTML page.
How to fetch the 'enters' from user, i mean, how to save format of users
information. If to do nothing with received textarea parameter the enters
disapears. I tried to find %D0%A0 substring (I saw it in query string) but
nothing works out - looks like it is invisible for script.
Thanks
------------------------------
Date: Tue, 6 Jul 2004 13:00:10 +0300
From: "Eugene Mikheyev" <Eugene.Mikheyev@kiev.com.com.ua>
Subject: Re: How to fetch new line from cgi textarea object
Message-Id: <ccdtdd$25p3$1@news.univ.kiev.ua>
> If to do nothing with received textarea parameter the enters
> disapears.
If to do nothing - nothing dissapears.
Blind guess - have you tried to convert \n => <br/>, or just enclose all
this in <pre></pre> tags?
I think you should have shown some code snippet...
------------------------------
Date: Tue, 06 Jul 2004 13:17:07 +0300
From: "Roman Khutkyy" <roman@sky.lviv.ua>
Subject: Re: How to fetch new line from cgi textarea object
Message-Id: <opsapn6tmvbibonh@192.168.0.6>
You are right Eugene !!!
It's really so simple. I've got almost crazy - but have never tried to
fetch /n. Thanks a lot. А ще кажуть різні дурниці - що Українець Українцю
не допоможе - брехня це все...
On Tue, 6 Jul 2004 13:00:10 +0300, Eugene Mikheyev
<Eugene.Mikheyev@kiev.com.com.ua> wrote:
>> If to do nothing with received textarea parameter the enters
>> disapears.
> If to do nothing - nothing dissapears.
> Blind guess - have you tried to convert \n => <br/>, or just enclose all
> this in <pre></pre> tags?
>
> I think you should have shown some code snippet...
>
>
------------------------------
Date: 06 Jul 2004 14:12:16 +0200
From: pjacklam@online.no (Peter J. Acklam)
Subject: Math::BigFloat oddities
Message-Id: <k6xhibbz.fsf@online.no>
I am totally out of clues as to why the following happens.
Please, let me know...
First, subtracting an element from itself should give 0...
$ perl -MMath::BigFloat -wle \
'$x = Math::BigFloat->new(3.14) ; $x = $x - $x ; print $x'
0
$ perl -MMath::BigFloat -wle \
'$x = Math::BigFloat->new(3.14) ; $x -= $x ; print $x'
6.28
^^^^
What was that?
Secondly, dividing an element by itself should give 1...
$ perl -MMath::BigFloat -wle \
'$x = Math::BigFloat->new(3.14) ; $x = $x / $x ; print $x'
1 # OK; x / x = 1
$ perl -MMath::BigFloat -wle \
'$x = Math::BigFloat->new(3.14) ; $x /= $x ; print $x'
0.00000000000000000000000000000000000000000001
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
What was that?
Is there a bug in the operator overloading of Math::BigFloat
objects?
Peter
--
#!/local/bin/perl5 -wp -*- mode: cperl; coding: iso-8859-1; -*-
# matlab comment stripper (strips comments from Matlab m-files)
s/^((?:(?:[])}\w.]'+|[^'%])+|'[^'\n]*(?:''[^'\n]*)*')*).*/$1/x;
------------------------------
Date: Tue, 06 Jul 2004 11:22:39 GMT
From: Joe Smith <Joe.Smith@inwap.com>
Subject: Re: Nonblocking Pipe Open
Message-Id: <3YvGc.16472$JR4.477@attbi_s54>
Gregory Toomey wrote:
> # based on perlopentut
> open(NET, "ping 11.22.33.44 |", O_NONBLOCK ) || die "can't fork ping";
You need to read perlopentut again. It clearly shows that O_NONBLOCK is
to be used with sysopen(), not with open().
-Joe
------------------------------
Date: Tue, 06 Jul 2004 02:22:32 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <EqSdnZIN2JylznfdRVn-vA@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.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: 6 Jul 2004 05:28:31 -0700
From: junk@dlink.org (Aqua)
Subject: User Currently logged on to the local system
Message-Id: <55d7995c.0407060428.7e4524e9@posting.google.com>
Dear Perl Group,
I have a CGI script (in IIS) where I have to find out who has logged
on to the local Windows NT/Windows 2000 system (client).
Can I get this information from Win32::NetAdmin module? Appreciate any
pointers.
Regards
Dominic
------------------------------
Date: Tue, 06 Jul 2004 11:48:01 +0200
From: Dennis Walter <dwmail@gmx.net>
Subject: Why use dollar sign $ for variables
Message-Id: <ccdsge$ov2$1@kohl.informatik.uni-bremen.de>
Hello Perl-Experts,
we were just wondering (in our project room where there is no
sunlight...) why successful 'modern' programming languages like perl and
php need this ugly $-sign in front of (nearly) every variable name.
Is this really just because it makes parsing of program text easier? I
mean, then, after some time, some capable hacker should have volunteered
for improving the parser, shouldn't he?
Thanks for your answers
D.
------------------------------
Date: Tue, 06 Jul 2004 11:25:52 +0100
From: Peter Hickman <peter@semantico.com>
Subject: Re: Why use dollar sign $ for variables
Message-Id: <40ea7e31$0$11245$afc38c87@news.easynet.co.uk>
Dennis Walter wrote:
> Hello Perl-Experts,
>
> we were just wondering (in our project room where there is no
> sunlight...) why successful 'modern' programming languages like perl and
> php need this ugly $-sign in front of (nearly) every variable name.
>
> Is this really just because it makes parsing of program text easier? I
> mean, then, after some time, some capable hacker should have volunteered
> for improving the parser, shouldn't he?
>
>
> Thanks for your answers
>
> D.
The $ symbol is not used to indicate a variable as such but the type of the
variable $ = scalar, @ = array, % = hash, & = code and \ = reference. It can get
a little more complicated than that but it will do for starters.
I would have certainly helped witting the earlier parsers, Perl 4 is easily
identified from it's use of the & before subroutines, but I'm not sure that that
would be a valid argument now, but it certainly help with syntax highlighting!
As to 'fixing' it, just imagine the number of programs that would break.
------------------------------
Date: Tue, 06 Jul 2004 11:53:17 +0100
From: "Richard Gration" <richard@zync.co.uk>
Subject: Re: Why use dollar sign $ for variables
Message-Id: <cce0au$qk7$1@news.freedom2surf.net>
In article <ccdsge$ov2$1@kohl.informatik.uni-bremen.de>, "Dennis Walter"
<dwmail@gmx.net> wrote:
> Hello Perl-Experts,
> we were just wondering (in our project room where there is no
> sunlight...) why successful 'modern' programming languages like perl and
> php need this ugly $-sign in front of (nearly) every variable name. Is
> this really just because it makes parsing of program text easier? I
> mean, then, after some time, some capable hacker should have volunteered
> for improving the parser, shouldn't he? Thanks for your answers
> D.
Hmm. I was wondering the other day about those ugly 'int i' declaration
statements in 'ancient' programming languages like C. Is this really just
because it makes parsing of program text easier? I mean, then, after some
time, some capable hacker should have volunteered for improving the
parser, shouldn't he?
;-)
I've never studied CS, so I'm not aware of any formal requirements for
language design which might mandate variable typing, but I do know that
it helps in the practice of programming. Once you accept that, then how
you type those variables is an aesthetic choice. The '$', '@', '%', etc
signs on perl variables don't look ugly to me. In fact my parser (the one
in my head) likes them quite a lot, and would be sorry to see them go!
Programming languages in general go out of their way to help you help
yourself and variable typing is one of those ways, however it's done.
Rich
PS There is at least one handy side-effect, as in
$count = @lines;
------------------------------
Date: Tue, 6 Jul 2004 06:45:42 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Why use dollar sign $ for variables
Message-Id: <slrncel476.lj.tadmc@magna.augustmail.com>
Dennis Walter <dwmail@gmx.net> wrote:
> Subject: Why use dollar sign $ for variables
One reason is so you can have variables like:
$chomp
@print
%foreach
without having to memorize (and avoid using) a few hundred reserved words.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
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 6770
***************************************
