Not to beat a dead horse, because this subject is well over. Sorry, if I offended anyone. Anyway, I always get and often see others get:
"You obviously have not read the documentation answer." And wanted to put in my perspective being new to this list and trying to learn mod_perl. I love perl and have more than 15 books on the subject. Here is my list. Programming Perl Programming the Perl DBI Writing Apache Modules Object Oriented Perl => Damian Conway Advanced Perl Programming Perl Cookbook Perl for System Administration Regular Expressions Network Programming with Perl =>Lincoln Stein's new book Perl in a Nutshell Web Client Programming Effective Perl Programming Mastering Aogorithms with Perl CGI Programming MySQL & mSWL Official Guide to Programming with CGI.pm Learning Perl Programming Web Graphics Perl Core Language Plus the APache Book and some books that cover Perl and PHP on MySql I think your name, Parrin is on or around those books somewhere. I have seen it before. I know I have seen Randalls several times. He is famous for the answer: "Stop limiting the limits." whenever you ask a question about limits on Apache. The answer doesn't tell you the answer to your problem. I know now not to use it though. I also have several links to perl sources and yes, the guide. I have read most of these and or something out of them and some of them more than once. I have also read the parts of the guide more than once. I have been doing this for around 3 or 4 years I guess. I tried to tackle mod_perl about a year ago, but with no success and am doing it again with moderate success. I think it is easy when you know something to write out an answer that you think everyone else will know. For instance, Once I had a file locking problem and some one said: Use a semephore file. A day later, I finally found out what a semephore file was. Often when I get an answer, I usually have to go back to the books to find out what it means or how to use it. The turnaround on problems can be days, trying every combination under the sun to see if it works. When I got the previous answer that said: Don't use -w and to use PerlWarn On, it took me about 30 minutes to figure out where to put it. I put it in the startup.pl file. Still hoping that was the right place. Still, when you run into problems with Mod_perl, there are really only a couple of places to look. And just because you have read something, doesn't mean that when a problem arises, the answer will hit you. I often find myself reading old material with more knowledge than when i previously read it and now understand things I didn't have a clue about before. Even though I have read and used a lot of this information, I can tell by the answers and talks you have on the list, that I am still pretty much an amateur. I think when people ask questions, they have not always just opened up an email and sent it out without thought. There is a great fear in that. You don't know what kind of answer you will get, whether you will understand it and have to ask another seemingly stupid question, or get flammed for doing so and never be able to ask a question again. I usually think about it for a couple of hours, try every combination I can think of, and look in every book I think will have something to do with it before tucking my tale and asking a list. Yes, sometimes I will ask before spending the time if I feel I don't have the time to try and find it myself, or have just spent 3 hours trying to solve another problem. Obviously, there are either too many sources or not enough. :) I can't tell. Too many places to look sometimes and not enough others. Sometimes it would be nice to be able to ask stupid questions and get answers instead of clever indirect put downs. Maybe, I just read too much into the emails because of my own insecurities with the language. IT is hard to get a feel for text based conversation. Anyway, I just wanted to put in my two cents and am thinking I might just get flammed for this as well. Should I send it? Sometimes I get this far on emails and just delete them. Cya and thanks John Michael > John Michael wrote: > > > I don't know if this will help. I know very litlle about mod perl, but most > > of the people on this list don't seem to answer questions from beginners. > > > Hmmm. You asked some questions that made it sound like you hadn't read > the documentation, and you stil got 3 answers in 24 hours. One thing > you should consider is that not everyone here is in the same time zone. > > > > I think you might try adding: > > use subs qw(main); > > in the top of your script. > > or instead of > > main() use &main() > > > That's probably not it. The difference between mail() and &main() is > that &main() circumvents prototypes, as documented in the perlsub man page. > > > > If that doesn't work, you will probably need to make the lib a package and > > import it into your fetch.pl program. > > > That probably *is* the answer, and a good programming practice for any > perl project. > > > > Does anyone know of a news group that answers mod perl questions? > > > There are lots of places that will answer mod_perl questions > (http://perlmonks.org/ for example), but none as good as this list. > > - Perrin >
