Uff!

How are you feeling now?  Has your anger gone or is still there?
Why is there a mailing list for perl6 up and running before the version is
out?
Why is it when you check for perl mailing lists on perl.com only mailing
lists for perl6 come up?

Thanks

Ajdin

-----Original Message-----
From: Tad McClellan [mailto:[EMAIL PROTECTED]]
Sent: 24 October 2000 13:43
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: new to perl



[ Cc'd to OP ]

On Tue, Oct 24, 2000 at 12:00:48PM +0100, Ajdin Brandic wrote:

> I have this perl script


Your message is completely off-topic on this mailing list.

Please do not abuse mailing lists like that.


This mailing list is for discussion of Perl *6* (note the mailing
list name).

Perl 6 does not yet exist, so nobody can write programs that
would be on-topic here.




   All of the rest of this post is off-topic here.

   Stop reading now (except for Ajdin :-)



You do not have a Perl question.

You have a web server setup question.

You have asked a bunch of Perl people to help you with a server
problem. You will get better answers if you ask a bunch of
server people your server question.   :-)

So, I cannot answer your question, but I have some advice
for you nonetheless.

Good luck!



> site.  But the problem is that I get an internal server error and as I am
> new to this I have no idea what it means.  I tried the error log file but
I
> cannot understand anything there.  The error is
> "Internal Server Error
> The server encountered an internal error or misconfiguration and was
unable
> to complete your request."
>
> Any help welcome,


Questions about Perl 5 can be asked on a Perl 5 mailing list,
or on one of the comp.lang.perl.* Usenet newsgroups.

Questions about CGI and web server setup can be asked on newsgroups
for those topics:

      comp.infosystems.www.authoring.cgi
      comp.infosystems.www.servers.mac
      comp.infosystems.www.servers.misc
      comp.infosystems.www.servers.ms-windows
      comp.infosystems.www.servers.unix



But Frequently Asked Questions (FAQs) can never be asked in any
of those forums (because they have already been answered, why
answer them yet again?).

Posting hundred-line programs is also likely to get you ignored.

You can search Perl's FAQs using the 'perldoc' program:

   perldoc -q "Server Error"

It finds this one:

   "My CGI script runs from the command line but not the
    browser.   (500 Server Error)"


So your question is off-topic everywhere!

(unless you have done what is suggested there and still have the problem)



It is obvious that you are completely lost. This is probably due
to trying to learn many things all at the same time. I suggest
you slow down, and learn one thing at a time.

This may not be the case for you, but many people try to
learn all of these at once:

1) Usenet

   see the    news.announce.newusers   newsgroup to find out
   what is socially acceptable in newsgroups.

   Lurk (read, don't post) in the newsgroup for a few days
   before posting (or skim several days worth of posts in
   a news archive such as deja.com).


2) Programming

   What is a "loop", "array", ...


3) Perl

   Write some programs that run from the *command line* before
   trying to write programs that run in the CGI environment.

   Write little programs before trying big programs.


4) CGI

   You can write CGI programs in *any language* you like.
   Many people choose to use Perl, but Perl is not
   "wedded" to WWW stuff.

   Perl is not CGI. Ask Perl questions in a Perl newsgroup.
   Ask CGI questions in a CGI newsgroup.

   Get your CGI programs working from the command line before
   trying them on the web server (this is easy to do if you
   are using the CGI.pm module).

   Type:

      perldoc -q CGI

   to find Perl FAQs that mention CGI. They have lots of pointers
   to information that you will need.


If you cannot determine whether you have a "Perl problem" or a
"CGI problem" then you will have a hard time finding help.


If you don't have time to learn all of those things, then you
will likely need to pay somebody who _has_ learned all of those
things.



> #!/usr/bin/perl


You have 2 bugs already. That should be:

   #!/usr/bin/perl -w
   use strict;


And if you are using <form>s, make that:

   #!/usr/bin/perl -wT
   use strict;



Type:

   perldoc perlrun
   perldoc perlsec

to find about about the '-wT' part.


Type:

   perldoc strict
   perldoc -f my

do find out about the "use strict" part.




Please try to find *appropriate* places to ask
your questions in the future.


--
    Tad McClellan                          SGML consulting
    [EMAIL PROTECTED]                     Perl programming
    Fort Worth, Texas

Reply via email to