FAQ 1.1 What is Perl?
PerlFAQ Server
comes with the standard Perl distribution. These postings aim to
reduce the number of repeated questions as well as allow the community
to review and update the answers. The latest version of the complete
perlfaq is at http://faq.perl.org .
--------------------------------------------------------------------
1.1: What is Perl?
Perl is a high-level programming language with an eclectic heritage
written by Larry Wall and a cast of thousands. It derives from the
ubiquitous C programming language and to a lesser extent from sed, awk,
the Unix shell, and at least a dozen other tools and languages. Perl's
process, file, and text manipulation facilities make it particularly
well-suited for tasks involving quick prototyping, system utilities,
software tools, system management tasks, database access, graphical
programming, networking, and world wide web programming. These strengths
make it especially popular with system administrators and CGI script
authors, but mathematicians, geneticists, journalists, and even managers
also use Perl. Maybe you should, too.
--------------------------------------------------------------------
The perlfaq-workers, a group of volunteers, maintain the perlfaq. They
are not necessarily experts in every domain where Perl might show up,
so please include as much information as possible and relevant in any
corrections. The perlfaq-workers also don't have access to every
operating system or platform, so please include relevant details for
corrections to examples that do not work on particular platforms.
Working code is greatly appreciated.
If you'd like to help maintain the perlfaq, see the details in
perlfaq.pod.
PerlFAQ Server
Bill H
Is the FAQ server talking to itself here?
Bill H
brian d foy
<cea2add7-7842-4104...@l42g2000hsc.googlegroups.com>,
Bill H <bi...@ts1000.us> wrote:
> Is the FAQ server talking to itself here?
What do you mean? If you think there's a problem, can you be more
specific?
Thanks,
Bill H
> In article
> <cea2add7-7842-4104-aeb7-adf27856c...@l42g2000hsc.googlegroups.com>,
>
> Bill H <b...@ts1000.us> wrote:
> > Is the FAQ server talking to itself here?
>
> What do you mean? If you think there's a problem, can you be more
> specific?
>
> Thanks,
Hi brian
On July 5th the server posted this, then on July 11th it posted it
again. Google has them linked up as a single conversation - so it
appears that the server is talking to itself.
Bill H
Keith Keller
>
> On July 5th the server posted this, then on July 11th it posted it
> again. Google has them linked up as a single conversation - so it
> appears that the server is talking to itself.
That's just how Google is displaying the messages. There is no direct
link between the two postings other than the similarity of the Subject:
headers (which can't be helped).
--keith
--
kkeller...@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information
Leon Timmermans
The problem with that is simple: the way google groups works. Never
assume other people will see it the way GG presents it to you, that will
confuse other people.
Leon Timmermans
szr
There are also some news readers that (incorrectly) will group messages
with the name subject, instead of checking for references. The easy fix
is add something variable to the subject to make it different each time
that FAQ is posted, like, for example,
FAQ 123: Short Description of FAQ %
FAQ 123: Short Description of FAQ ^
FAQ 123: Short Description of FAQ $
Or some other way of making it unique. Yes, it's not a pretty way of
getting around that deficienty in some readers, but if you want to, then
that's what needs to be done afaik.
I wish more user agents would pay better attention to standards.
--
szr
Keith Keller
>
> There are also some news readers that (incorrectly) will group messages
> with the name subject, instead of checking for references. The easy fix
> is add something variable to the subject to make it different each time
> that FAQ is posted, like, for example,
>
>
> FAQ 123: Short Description of FAQ %
> FAQ 123: Short Description of FAQ ^
> FAQ 123: Short Description of FAQ $
>
> Or some other way of making it unique.
It seems like putting a posting date would help make it unique, if that
were actually desired. (I don't see a real need.)
Ted Zlatanov
s> There are also some news readers that (incorrectly) will group messages
s> with the name subject, instead of checking for references.
...
s> I wish more user agents would pay better attention to standards.
It's very common that references in a thread will get corrupted, so
grouping messages by subject is very helpful. I don't see how that's a
bad thing, as there is no standard AFAIK that messages should NOT be
grouped by subject.
Ted
Peter J. Holzer
> On 2008-07-13, szr <sz...@szromanMO.comVE> wrote:
>> There are also some news readers that (incorrectly) will group messages
>> with the name subject, instead of checking for references.
In good readers this is configurable. If the user has explicitely
configured it, it isn't incorrect.
>> The easy fix is add something variable to the subject to make it
>> different each time that FAQ is posted, like, for example,
>>
>> FAQ 123: Short Description of FAQ %
>> FAQ 123: Short Description of FAQ ^
>> FAQ 123: Short Description of FAQ $
>>
>> Or some other way of making it unique.
>
>
> It seems like putting a posting date would help make it unique, if that
> were actually desired. (I don't see a real need.)
I don't think it's very useful to distinguish otherwise identical
postings in the subject. It might be useful to include the date when an
FAQ entry was *last changed* in the subject:
* FAQ entries which have been recently changed can be easily identified
* FAQ entries which are very old (and hence likely to be out-of-date)
can be easily identified
* a use could killfile each entry after reading it (perhaps for a
limited time) and still get the new version if the entry is updated.
(although given the number of different FAQ entries I doubt anyone
would do this).
hp