[24995] in Perl-Users-Digest
Perl-Users Digest, Issue: 7245 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Oct 14 09:07:01 2004
Date: Thu, 14 Oct 2004 06:05:09 -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 Thu, 14 Oct 2004 Volume: 10 Number: 7245
Today's topics:
Re: Concatenating an array into one string? (Anno Siegel)
Re: Getting Additional Perl Newsgroups (Peter Scott)
Re: hard references/arrays <nobull@mail.com>
Re: Help with sorting lists of lists <shawn.corey@sympatico.ca>
Re: Help with sorting lists of lists (Anno Siegel)
Re: HTML::Parser and <p> behaviour? <usa1@llenroc.ude.invalid>
Re: HTML::Parser and <p> behaviour? <tadmc@augustmail.com>
Re: HTML::Parser and <p> behaviour? <tadmc@augustmail.com>
Re: HTML::Parser and <p> behaviour? <1usa@llenroc.ude.invalid>
Re: Perl to monitor server stats burlo_stumproot@yahoo.se
Re: Range lookup (Anno Siegel)
Re: Restricting a program to one running instance (Anno Siegel)
Re: Top 10 list algorithm <shawn.corey@sympatico.ca>
Re: Top posting (was Re: Concatenating an array into on (Anno Siegel)
Re: Top posting (was Re: Concatenating an array into on <shawn.corey@sympatico.ca>
Re: Top posting (was Re: Concatenating an array into on (Anno Siegel)
Re: Top posting (was Re: Concatenating an array into on <do-not-use@invalid.net>
Re: Top posting (was Re: Concatenating an array into on <shawn.corey@sympatico.ca>
Re: Top posting (was Re: Concatenating an array into on <spikeywan@bigfoot.com>
Re: Top posting (was Re: Concatenating an array into on <tadmc@augustmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 14 Oct 2004 10:42:17 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Concatenating an array into one string?
Message-Id: <ckll69$p4h$1@mamenchi.zrz.TU-Berlin.DE>
Scott Bryce <sbryce@scottbryce.com> wrote in comp.lang.perl.misc:
> Paul Lalli wrote:
>
> > chomp @test;
>
> I've got the Camel book open right in front of me, and I missed that!
>
> I should have known that if I posted code, someone would find a better
> way to do it!
Well, that's the point of posting code, isn't it.
Anno
------------------------------
Date: Thu, 14 Oct 2004 10:10:55 GMT
From: peter@PSDT.com (Peter Scott)
Subject: Re: Getting Additional Perl Newsgroups
Message-Id: <Pgsbd.98320$a41.9886@pd7tw2no>
In article <slrncms17t.r1o.dha@panix2.panix.com>,
"David H. Adler" <dha@panix.com> writes:
>On 2004-10-14, Tad McClellan <tadmc@augustmail.com> wrote:
>> If not, then where did you hear of the perl.qa newsgroup?
>>
>> I cannot find any evidence of it.
>
>One must keep in mind that the perl mailing lists tend to have a gateway
>to usenettieness. Or not, I suppose. :-)
>
>If one uses nntp.perl.org as one's news server, one can find these
>mailing lists as newsgroups (which is probably the answer to Jim's
>original question - point your newsreader at a different server).
What's also helpful is that Google Groups indexes postings
there under the perl.* hierarchy:
http://groups.google.com/groups?safe=images&as_ugroup=perl.qa&lr=&hl=en
--
Peter Scott
http://www.perldebugged.com/
*** NEW *** http://www.perlmedic.com/
------------------------------
Date: Thu, 14 Oct 2004 12:28:53 +0100
From: Brian McCauley <nobull@mail.com>
Subject: Re: hard references/arrays
Message-Id: <cklnl4$ied$1@sun3.bham.ac.uk>
Tintin wrote:
> "Paul Lalli" <mritty@gmail.com> wrote in message
> news:Bm9bd.5421$275.4070@trndny01...
>
>>"Tintin" <tintin@invalid.invalid> wrote in message
>>news:2t495mF1s5ereU1@uni-berlin.de...
>>
>>>I'm wanting to set up a loop of array names like:
>>
>>No you don't. First read
>>perldoc -q "variable name"
>>and then search Google for the absurdly large number of posts dealing
>>with "variable as a variable name" and "symrefs", including more than a
>>few in the last week.
>
>
> Yes, I am painfully aware of the gazillion questions along those lines.
So, presumably, you should be painfully aware of the gazillion answers
saying "if you think you want a symref you probably really want a hash
of references instead".
> Notice I said "like", meaning, what is the correct way of doing this.
Er, use a hash of references instead.
>>>foreach my $array qw(name1 name2 name3) {
>>
>>Why would you want to loop through the *names* of the arrays instead of
>>the arrays themselves?
>
>
> Because I wanted to use the array name along with its data.
In that case you probaly want a hash of array references instead.
> [...] let me wind the clock right back
> and explain what I'm trying to do, ie: X.
>
> I'm reading in a fields from a text file to be loaded into a database.
> There are various sets of data that can have 1-6 lines of information. For
> example
>
> Address1=1 fred st
> Address2=suburb
> Address3=city
>
> In the database, there are 6 columns defined for the Address, so what I need
> to do is read in the addresses (and ensure that I account for records with
> less than 6 lines). Now there are at least 6 other data types like this.
>
> What I'm currently doing is
>
> foreach my $i (0..5) {
> push @insert_record,$addresses[$i];
> }
>
> foreach my $i (0..5) {
> push @insert_record,$elements[$i];
> }
>
> and so on, to build up an array used to insert a record into the database.
>
> Using repeated code like that is a red warning sign saying that it can be
> compacted,
> however I wasn't (still aren't) sure of the best way of handling
> it.
Like has been said in the gazillion threads alluded to above, use a hash
of references instead.
Replace the separate variables @addresses and @elements with a single
hash of arrays (say, %record) so @addresses becomes @{$record{ADDRESS}}
and @elements becomes @{$record{ELEMENT}}.
> Note that the loop is needed to pad out the insert_record array with undef
> values if the array being referenced is less than 6 elements.
No it isn't, a slice will do that perfectly well.
push @insert_record => map { @$_[0..5] } @record{'ADDRESS','ELEMENT'};
------------------------------
Date: Thu, 14 Oct 2004 07:38:07 -0400
From: Shawn Corey <shawn.corey@sympatico.ca>
Subject: Re: Help with sorting lists of lists
Message-Id: <gxtbd.36010$3C6.1596635@news20.bellglobal.com>
A. Sinan Unur wrote:
> No need to venture out to the whole world wide web. You can access the Perl
> documentation installed on your computer using this command from the shell
> you are using.
>
> To see the available documentation, type
>
> perldoc perltoc
>
> on the command line.
>
> Sinan.
The problem with perldoc is its lack of adequate searching. perldoc -q
keyword_guess only searches the FAQs. http://www.perldoc.com/ is more
extensive but like all searches, you have to guess the magic password to
open the Cave of Riches.
--- Shawn
------------------------------
Date: 14 Oct 2004 12:04:52 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Help with sorting lists of lists
Message-Id: <cklq14$rej$4@mamenchi.zrz.TU-Berlin.DE>
Shawn Corey <shawn.corey@sympatico.ca> wrote in comp.lang.perl.misc:
> A. Sinan Unur wrote:
> > No need to venture out to the whole world wide web. You can access the Perl
> > documentation installed on your computer using this command from the shell
> > you are using.
> >
> > To see the available documentation, type
> >
> > perldoc perltoc
> >
> > on the command line.
> >
> > Sinan.
>
> The problem with perldoc is its lack of adequate searching. perldoc -q
> keyword_guess only searches the FAQs. http://www.perldoc.com/ is more
> extensive but like all searches, you have to guess the magic password to
> open the Cave of Riches.
Direct grep is primitive, but efficient. Go to where the pods are:
eval set `perl -V:privlib`
cd $privlib/pod # or $privlib/pods, the name has changed recently
grep -li 'frobnitzer'
That will list all Perl documents that mention "frobnitzer". Vary
to taste. Modify appropriately for non-Unix systems.
Anno
------------------------------
Date: 14 Oct 2004 12:12:33 GMT
From: "A. Sinan Unur" <usa1@llenroc.ude.invalid>
Subject: Re: HTML::Parser and <p> behaviour?
Message-Id: <Xns958253CCA70A9asu1cornelledu@132.236.56.8>
"187" <bigal187@removethis.rx.eastcoasttfc.com> wrote in
news:2t6oieF1sinaeU1@uni-berlin.de:
> A. Sinan Unur wrote:
>> OTOH, I would think that someone who wishes to appear friendly might
>> want to avoid the nickname '187'.
>
> Why is that? This is how I uniquely identify myself. If "187" means
> something else that I am not awre of please let me know.
I assumed 'eastcoastttfc.com' indicated that you were US based. I might
have jumped to a conclusion there. FYI, AFAIK, 187 is the police code for
homicide. You might guess what that name might signal to at least
some others.
Sinan.
------------------------------
Date: Thu, 14 Oct 2004 05:58:41 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: HTML::Parser and <p> behaviour?
Message-Id: <slrncmsmv1.3ss.tadmc@magna.augustmail.com>
187 <bigal187@removethis.rx.eastcoasttfc.com> wrote:
> True. I do admit I was quick to judge and I'm sorry for snapping at you.
The Posting Guidelines caution against that too.
(but it doesn't work if you don't follow the suggestions it outlines. :-)
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Thu, 14 Oct 2004 07:32:40 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: HTML::Parser and <p> behaviour?
Message-Id: <slrncmssf8.3ss.tadmc@magna.augustmail.com>
Pinocchio (aka: Fred Canis, aka: 187, aka: krakle...)
<spambiat@yahoo.com> wrote:
> Tad McClellan wrote:
>> 187 <bigal187@remove.rx.eastcoasttfc.com> wrote:
>>> Grated soem sample code would of been nice,
^^^^^^^^
^^^^^^^^ hmmm
>>> You could of just rplied asking for more information,
^^^^^^^^
^^^^^^^^ hmmm some more
> Maybe best to let thread jsut die instead of going on so bitterly.
^^^^
^^^^
It will die if you stop adding persona to your repertoire[1].
Can't you find some other place to do your trolling?
[1] Message-ID: <3d76abc6.61075808@news.erols.com>
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 14 Oct 2004 12:58:29 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: HTML::Parser and <p> behaviour?
Message-Id: <Xns95825B4C251FEasu1cornelledu@132.236.56.8>
Geoff Cox <geoff.cox@removethisplease.freeuk.com> wrote in
news:mdasm0lhpv0ijfd9s6lcroniaqipptid4h@4ax.com:
> On 14 Oct 2004 00:07:44 GMT, "A. Sinan Unur"
> <usa1@llenroc.ude.invalid> wrote:
>
>
>>I think you probably want to emit the start and end tags only when the
>>start and end callbacks are invoked. I tried to shorten your script to
>>deal only with the p case:
>
> Many thanks for the code below - it woks fine and I will try to get to
> grips with how it achieves this. You can no doubt see that I do not
> have a very good understanding of HTML::Parser !
The fact is, I do not either.
I try to answer questions here because that helps me learn.
> Do you have any suggestions re possible HTML::Parser tutorial type
> places on the net?
I only have access to the exact same documentation you have access to. I
actually apply all the principles I listed elsethread when I attempt to
answer a question.
You might want to check all the examples in
http://search.cpan.org/src/GAAS/HTML-Parser-3.36/eg/
But don't just stare at them. Start with the simplest and try to work out
what they do.
Also, my inclination would have been not to subclass HTML::Parser, but
use the version 3 API instead.
Sinan.
--
A. Sinan Unur
1usa@llenroc.ude.invalid
(remove '.invalid' and reverse each component for email address)
------------------------------
Date: Thu, 14 Oct 2004 12:49:26 GMT
From: burlo_stumproot@yahoo.se
Subject: Re: Perl to monitor server stats
Message-Id: <usm8ha2h7.fsf@notvalid.se>
"KWall" <mirak63@carolina.rr.com> writes:
> Hello. Has anyone ever used PERL to monitor Windows server statistics? Is
> there a book or a place to start?
>
> Thanks,
> Kairm
> karim.wall@acs-inc.com
Have a look at this book by Dave Roth.
"Win32 Perl Programming: The Standard Extensions, Second Edition"
It includes chapters like:
Network Administration
Administration of Machines
and much more.
The authors web site http://www.roth.net/
------------------------------
Date: 14 Oct 2004 11:53:42 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Range lookup
Message-Id: <cklpc6$rej$3@mamenchi.zrz.TU-Berlin.DE>
Abigail <abigail@abigail.nl> wrote in comp.lang.perl.misc:
> Yash (yashgt@yahoo.com) wrote on MMMMLXI September MCMXCIII in
> <URL:news:5a373b1d.0410130456.4f12e63d@posting.google.com>:
> "" I have a set of ranges such as
> "" <0.1%
> "" 0.1-0.2%
> "" 0.2-0.3%
> "" 0.3-0.4%
> "" 0.4-0.5%
> "" 0.5-0.6%
> "" 0.6-0.7%
> "" 0.7-0.8%
> "" 0.8-0.9%
> "" 0.9-1.0%
> "" 1.0-1.5%
> "" 1.5-2.0%
> "" 2.0-2.5%
> "" 2.5-3.0%
> "" 3-20%
> "" 20-30%
> "" 30-40%
> "" >40%
> ""
> "" and I have to identify the range that contains an input value such as
> "" 1.25. The above set of ranges is not fixed and is configurable in a
> "" text file.
> "" Can somebody suggest the most efficient way to do this, in terms of
> "" the data structure to use and the lookup technique to apply.
>
>
> What a good method is depends on a couple of things. First, does the
> set of ranges overlap each other, that is, are there points that belong
> to more than one range? Second, how many queries per set of ranges
> will you do? If you just have a couple, there's no point in doing any
> preprocessing. Otherwise, building a datastructure might pay off.
The number of ranges would be another consideration. A handful or
two, as in the example, would probably be treated differently than
a million.
Lots of possibilities. I'll bet, binary search will figure large
in many of the more efficient ones.
> BTW, note that your question has nothing at all to do with Perl. Finding
> the most appropriate datastructure for this problem is independent of
> the language being used.
That said, I'd take a look at Tie::RangeHash, and probably other
CPAN modules with "range" in their description, either for direct
applicability or for inspiration.
Anno
------------------------------
Date: 14 Oct 2004 11:33:42 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Restricting a program to one running instance
Message-Id: <cklo6m$rej$1@mamenchi.zrz.TU-Berlin.DE>
Ben Morrow <usenet@morrow.me.uk> wrote in comp.lang.perl.misc:
>
> Quoth Michele Dondi <bik.mido@tiscalinet.it>:
[using file locks for mutual exclusion]
> > (ii) once (i) is done, then also check that the process corresponding
> > to the stored pid corresponds to a program called like $0.
> >
> > Now, the questions are: would (i) be a good idea?
>
> Yes. It would be anyway, so you can find it and kill it easily if it
> gets jammed.
>
> > Would (ii) be a good idea too?
>
> Not really. The risk that either it will be a process that matches that
> shouldn't (not *that* likely, but rather more so if someone's being
> malicious) or a process that doesn't match that should (consider
> starting the program as 'prog', '~/bin/prog', 'perl ../bin/prog'; I have
> no idea what the kernel puts in argv (although I would hope the first
> two were ('/usr/bin/perl', '/dev/fd/3') or in /proc/$$/cmdline for each
> of these cases, and I suspect there is no well-defined answer).
>
> If you make the pidfile secure, then you can simply check if that pid is
> still running (kill 0 => $pid); if you're worried about pid wraparound
> then you really need to get some positive check that the process
> concerned is one of yours, such as (in the extreme case) connecting to a
> Unix-domain socket the other copy is listening on and performing a
> secure authentication exchange.
That should only be necessary if the lock-able process must run under
various user-id's. If it is always run under the same id, the lock
file permissions should only allow the owner to open the file. Also,
(perhaps needless to say) the lock file must be specific to that process,
in particular, no other program (of yours) should ever lock that file.
Then, unless the uid is compromised, if there is a lock, it *must*
belong to the one process that can hold it.
Anno
------------------------------
Date: Thu, 14 Oct 2004 07:31:42 -0400
From: Shawn Corey <shawn.corey@sympatico.ca>
Subject: Re: Top 10 list algorithm
Message-Id: <frtbd.36009$3C6.1595279@news20.bellglobal.com>
John W. Krahn wrote:
> Why not use splice? :-)
>
> splice @top, $j + 1, 0, $num;
Not enough coffee? Too early in the morning? Failed to read the
documentation?
--- Shawn
(That's my story and I sticking to it!)
------------------------------
Date: 14 Oct 2004 10:51:58 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Top posting (was Re: Concatenating an array into one string?)
Message-Id: <cklloe$p4h$2@mamenchi.zrz.TU-Berlin.DE>
Richard S Beckett <spikeywan@bigfoot.com> wrote in comp.lang.perl.misc:
[...]
> Can someone please get a ruling from God or something as to which system we
> should use across ALL newsgroups, so we can put this to bed once and for
> all, 'cause I'm getting really pissed off by the anal twats who insist that
> people must post at the bottom in one newsgroup, and then a different bunch
> of anal twats who insist that you must post at the top in another group!
I was going to explain this (once again), but seeing as you disqualify
people with a firm opinion in the matter as "anal twats" put me out of
the mood.
Anno
------------------------------
Date: Thu, 14 Oct 2004 07:17:05 -0400
From: Shawn Corey <shawn.corey@sympatico.ca>
Subject: Re: Top posting (was Re: Concatenating an array into one string?)
Message-Id: <ydtbd.26011$hk6.958301@news20.bellglobal.com>
Hi,
Do whatever you like. Nobody owns a newsgroup. Those that don't like
what you do can skip the message. Nobody is forcing them to read it!
--- Shawn
Richard S Beckett wrote:
>>One of the prime sins to avoid is top-posting and fully quoting someone
>>else's post without actually referring to any part of it.
>>
>>Have fun learning.
>>
>>Sinan.
>
>
> One small question about this...
>
> In some news groups, they get upset if you top post, because they like the
> entire thread to be visible in each post from the top down. This means that
> you can pick any individual post, read from the top, and get the gist of the
> entire thread.
>
> In other newsgroups they much prefer people to top post. This means that if
> you've been reading the thread from the beginning, you don't have to trawl
> through everything that you've already read to find the latest comment, as
> it's there right at the top. If you do need to read back, then the
> information is still there.
>
> Both systems have their merits, and I can understand why the people in some
> groups opt for one style, and the people in other groups opt for the other
> style.
>
> However, if a person reads many newsgroups, it's a very difficult thing for
> them to know whether they're supposed to top post or bottom post in a
> particular newsgroup.
>
> As long as the pertinent information is there, who is to say which style is
> correct?
>
> Can someone please get a ruling from God or something as to which system we
> should use across ALL newsgroups, so we can put this to bed once and for
> all, 'cause I'm getting really pissed off by the anal twats who insist that
> people must post at the bottom in one newsgroup, and then a different bunch
> of anal twats who insist that you must post at the top in another group!
>
> Thanks.
>
> R.
>
>
PS: Sometimes I post to the top and bottom.
------------------------------
Date: 14 Oct 2004 11:37:31 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Top posting (was Re: Concatenating an array into one string?)
Message-Id: <cklodr$rej$2@mamenchi.zrz.TU-Berlin.DE>
Shawn Corey <shawn.corey@sympatico.ca> wrote in comp.lang.perl.misc:
> Hi,
>
> Do whatever you like. Nobody owns a newsgroup. Those that don't like
> what you do can skip the message. Nobody is forcing them to read it!
Splendid idea. Before asking a question, slap the people you want to
ask in the face a few times. They'll double their efforts to give
you good advice.
Anno
------------------------------
Date: 14 Oct 2004 13:59:32 +0200
From: Arndt Jonasson <do-not-use@invalid.net>
Subject: Re: Top posting (was Re: Concatenating an array into one string?)
Message-Id: <yzdis9djysb.fsf@invalid.net>
anno4000@lublin.zrz.tu-berlin.de (Anno Siegel) writes:
> Richard S Beckett <spikeywan@bigfoot.com> wrote in comp.lang.perl.misc:
>
> [...]
>
> > Can someone please get a ruling from God or something as to which system we
> > should use across ALL newsgroups, so we can put this to bed once and for
> > all, 'cause I'm getting really pissed off by the anal twats who insist that
> > people must post at the bottom in one newsgroup, and then a different bunch
> > of anal twats who insist that you must post at the top in another group!
>
> I was going to explain this (once again), but seeing as you disqualify
> people with a firm opinion in the matter as "anal twats" put me out of
> the mood.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
------------------------------
Date: Thu, 14 Oct 2004 07:57:10 -0400
From: Shawn Corey <shawn.corey@sympatico.ca>
Subject: Re: Top posting (was Re: Concatenating an array into one string?)
Message-Id: <7Ptbd.26016$hk6.962362@news20.bellglobal.com>
Anno Siegel wrote:
> Splendid idea. Before asking a question, slap the people you want to
> ask in the face a few times. They'll double their efforts to give
> you good advice.
>
> Anno
Actually find their gems of wisdom amongst their complains is an
interesting intellectual puzzle. The entertainment value of this
newsgroup is half the reason I read it.
--- Shawn
------------------------------
Date: Thu, 14 Oct 2004 12:53:28 +0100
From: "Richard S Beckett" <spikeywan@bigfoot.com>
Subject: Re: Top posting (was Re: Concatenating an array into one string?)
Message-Id: <cklpgp$53u$1@newshost.mot.com>
> > Can someone please get a ruling from God or something as to which system
we
> > should use across ALL newsgroups, so we can put this to bed once and for
> > all, 'cause I'm getting really pissed off by the anal twats who insist
that
> > people must post at the bottom in one newsgroup, and then a different
bunch
> > of anal twats who insist that you must post at the top in another group!
>
> I was going to explain this (once again), but seeing as you disqualify
> people with a firm opinion in the matter as "anal twats" put me out of
> the mood.
Oh well.
Anyway, that's my whole point. You were going to explain why, in your
OPINION, top posting is bad.
Top posting is good in some people's OPINION, and it's bad in other people's
OPINION.
The whole thing is based on OPINIONS, which VARY between different people,
and newsgroups. There is no definite answer as to which should be used.
Therefore, anyone insisting that it should be done in a certain way, is only
trying to force their OPINION on others.
I don't know about you, but I hate it when somoene does that!
In MY OPINION, all religions should be banned, because they cause nothing
but trouble, arguments, wars, etc. This is a valid and accurate opinion, but
if I insist that all religions become illegal, guess what, I'm going to have
Christians, Buddhists, Islamists (?), Sikhs, etc, etc (well, probably all
but the Zenists) jumping down my throat. I will also have a whole load of
other people agreeing with me. Which is right? Will there ever be an answer
to the question?
Similarly with top posting. Why keep jumping down the throat of newbies,
insisting that they don't top post? They go to a different newsgroup, and
get blasted for not top posting. Which is right? Will there ever be an
answer to the question?
R.
------------------------------
Date: Thu, 14 Oct 2004 07:23:49 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Top posting (was Re: Concatenating an array into one string?)
Message-Id: <slrncmsrul.3ss.tadmc@magna.augustmail.com>
Richard S Beckett <spikeywan@bigfoot.com> wrote:
[ Please provide a proper attribution when you quote someone. ]
>> One of the prime sins to avoid is top-posting and fully quoting someone
>> else's post without actually referring to any part of it.
> One small question about this...
>
> In some news groups, they get upset if you top post, because they like the
> entire thread to be visible in each post from the top down.
^^^^^^^^^^^^^ ^^^^^^^^^^^^
I don't know of any such newsgroups, could you please name one
or two of them for my enlightenment?
You are expected to trim posts in _this_ newsgroup.
> In other newsgroups they much prefer people to top post.
This is news to me too.
Please help me learn what you know by naming one or two
Big 8 newsgroups where top-posting is preferred.
Thank you.
> This means that if
> you've been reading the thread from the beginning, you don't have to trawl
> through everything that you've already read to find the latest comment, as
> it's there right at the top.
If you properly trim the quoted text, then you don't have to trawl
through everything that you've already read to find the latest comment,
as it's there right above their added comment.
> Can someone please get a ruling from God or something as to which system we
> should use across ALL newsgroups,
OK, I just spoke with her, here it is:
Quote only enough to establish the context for the comment
you are going to add. Put your comment immediately following
that carefully trimmed text.
Any other approach will surely lead to Eternal Damnation.
> I'm getting really pissed off by the anal twats who insist
Please stop changing your posting address, pick one and stick with it.
--
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 7245
***************************************
