[29118] in Perl-Users-Digest
Perl-Users Digest, Issue: 362 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Apr 20 03:10:09 2007
Date: Fri, 20 Apr 2007 00:09:04 -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 Fri, 20 Apr 2007 Volume: 11 Number: 362
Today's topics:
Booleans in Perl <dw149@acmex.gatech.edu>
Re: Booleans in Perl <cwilbur@chromatico.net>
Re: die problem? <purlgurl@purlgurl.net>
How to make perl script executable from anywhere on win veg_all@yahoo.com
Re: How to make perl script executable from anywhere on <purlgurl@purlgurl.net>
Re: How to make perl script executable from anywhere on <purlgurl@purlgurl.net>
new CPAN modules on Fri Apr 20 2007 (Randal Schwartz)
Newbie queston on Perl and lex. somedeveloper@gmail.com
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Server For Rent? Where? jayjuliano@optonline.net
Re: Top Turds of comp.lang.perl.misc (2007) <greg@lazymountain.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 20 Apr 2007 02:08:12 +0000 (UTC)
From: David Williams <dw149@acmex.gatech.edu>
Subject: Booleans in Perl
Message-Id: <f097ac$9k3$1@news-int.gatech.edu>
Small question.
Why does PERL do the following
$a=FALSE;
$b=FALSE;
$c=($a && $b);
if($c){
echo "the expr evaluates to true";
}
else{
echo "the expr evaluates to false;
}
I always get "the expr evaluates to true";
if it is false && false, should it not be false?
My workaround is to use the eq operand
--
David Williams
Georgia Institute of Technology, Atlanta Georgia, 30332
Email: dw149@prism.gatech.edu
------------------------------
Date: 19 Apr 2007 22:24:15 -0400
From: Charlton Wilbur <cwilbur@chromatico.net>
Subject: Re: Booleans in Perl
Message-Id: <874pnbzsts.fsf@mithril.chromatico.net>
>>>>> "DW" == David Williams <dw149@acmex.gatech.edu> writes:
DW> Small question. Why does PERL do the following
DW> $a=FALSE; $b=FALSE; $c=($a && $b); if($c){ echo "the expr
DW> evaluates to true"; } else{ echo "the expr evaluates to false;
DW> }
DW> I always get "the expr evaluates to true";
use strict; use warnings;
You'll probably find out that that code doesn't do what you think it does.
(That is, if you're using Perl at all; the 'echo' function in there
makes me think you're using PHP, in which case you're in the wrong
newsgroup.)
DW> if it is false && false, should it not be false?
It's not false && false; it's the string "FALSE" and the string
"FALSE" - since non-empty strings evaluate to true, the whole
expression evaluates to true.
This will all be made clearer when you enable strictures and warnings.
Charlton
--
Charlton Wilbur
cwilbur@chromatico.net
------------------------------
Date: Thu, 19 Apr 2007 18:15:34 -0700
From: Purl Gurl <purlgurl@purlgurl.net>
Subject: Re: die problem?
Message-Id: <yNydnegYo5WjibXbnZ2dnUVZ_i2dnZ2d@giganews.com>
Tad McClellan wrote:
> Purl Gurl wrote:
>> g4173c wrote:
(snipped)
>>> system ("cleatool co -unr -nc $revfilename") || die "Error:
>>> Couldn't Check Out $revfilename: $!\n";
>>> The system call has a typo for the command. I thought that it should
>>> have stopped there, however I get this:
>>> Can't exec "cleatool": No such file or directory at ba line 83,
>> Your system call is successful. An error message is returned to
>> your call,
> No it isn't.
My presumption is you are not wearing your reading glasses
rather than your usual habit of lying to readers.
"Can't exec "cleatool": No such file or directory at ba line 83"
Nah, this is not a problem of your not wearing your reading glasses.
This is a problem of your constant childish trolling of this group.
>> which is success. Your argument "cleatool" is incorrect
>> but your "system" call successfully runs and completes; no system
>> error code is returned.
> Yes it is.
> perl -le '$ret = system "bad"; print $ret'
> -1
Irrelevant. Your example code does not comply with the
originating author's parameters.
You will earn more respect by being truthful with readers
rather than continuing your years long habit of lying to
readers. All you have accomplished is to exemplify how
childish are you.
Purl Gurl
------------------------------
Date: 19 Apr 2007 21:06:16 -0700
From: veg_all@yahoo.com
Subject: How to make perl script executable from anywhere on windows?
Message-Id: <1177041976.758977.189160@b75g2000hsg.googlegroups.com>
I have ActivePerl installed and want to place all my scripts in one
directory but be able to execute them from anywhere. So if I type perl
myscript.pl from any directory/folder in windows dos prompt it will
run.
------------------------------
Date: Thu, 19 Apr 2007 21:44:23 -0700
From: Purl Gurl <purlgurl@purlgurl.net>
Subject: Re: How to make perl script executable from anywhere on windows?
Message-Id: <TPidnZo6XYWy2LXbnZ2dnUVZ_oOknZ2d@giganews.com>
veg_all@yahoo.com wrote:
> I have ActivePerl installed and want to place all my scripts in one
> directory but be able to execute them from anywhere. So if I type perl
> myscript.pl from any directory/folder in windows dos prompt it will
> run.
http://aspn.activestate.com/ASPN/docs/ActivePerl/5.8/faq/Windows/ActivePerl-Winfaq4.html#How_do_I_associate_Perl_scripts_
http://radio.weblogs.com/0100529/WinXp/
Purl Gurl
------------------------------
Date: Thu, 19 Apr 2007 22:26:06 -0700
From: Purl Gurl <purlgurl@purlgurl.net>
Subject: Re: How to make perl script executable from anywhere on windows?
Message-Id: <avydnQBT8JJq07XbnZ2dnUVZ_oytnZ2d@giganews.com>
Purl Gurl wrote:
> veg_all wrote:
>> I have ActivePerl installed and want to place all my scripts in one
>> directory but be able to execute them from anywhere. So if I type perl
>> myscript.pl from any directory/folder in windows dos prompt it will
>> run.
> http://aspn.activestate.com/ASPN/docs/ActivePerl/5.8/faq/Windows/ActivePerl-Winfaq4.html#How_do_I_associate_Perl_scripts_
> http://radio.weblogs.com/0100529/WinXp/
A more advanced method, treated separately in this article,
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/environment_variables.mspx?mfr=true
Simple matter of adding your perl bin path. An example,
Path=C:\apache\bin;C:\WINDOWS\system32;C:\WINDOWS;...(other paths)
For my system, c:\apache\bin is the location of my perl executable.
This location is all your truly need to run perl core from a command line.
I type in perl at my command line, Windows check paths until perl.exe
is found in my apache\bin directory. For my installation I renamed my
perl5.6.1.exe to simply perl.exe to keep my command line short and simple.
Using this method will allow you to run perl from a command line, in any directory,
and allow you to associate a program editor with a .pl file or .cgi file. Click
on .pl or .cgi file in a directory, a program editor opens the file. Type perl
on a command line, perl core runs.
Your Path syntax for adding a path to Windows must be precise and correct.
For Windows XP use the Microsoft link.
For Windows 95/98/ME same Path syntax but add this your autoexec.bat file
found in your C:\ root directory. You will have to reboot.
You can also set a Path on a temporary basis at a command line.
Research syntax on this well before attempting to do this. Your syntax
must be perfect.
A problem is suggested. Your Active State install should have set a
path for you during installation. You should check this to discover
why your Active State install failed to perform this task.
Purl Gurl
------------------------------
Date: Fri, 20 Apr 2007 04:42:10 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Fri Apr 20 2007
Message-Id: <JGs52A.JqG@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
AutoReloader-0.02
http://search.cpan.org/~shmem/AutoReloader-0.02/
Lazy loading and reloading of anonymous subroutines
----
CPAN-1.91
http://search.cpan.org/~andk/CPAN-1.91/
query, download and build perl modules from CPAN sites
----
Catalyst-Manual-5.700701
http://search.cpan.org/~jrockway/Catalyst-Manual-5.700701/
The Catalyst developer's manual
----
Catalyst-Plugin-Authentication-Credential-Livedoor-0.02
http://search.cpan.org/~ikebe/Catalyst-Plugin-Authentication-Credential-Livedoor-0.02/
livedoor Auth API for Catalyst.
----
Catalyst-Plugin-Authentication-Credential-Livedoor-0.03
http://search.cpan.org/~ikebe/Catalyst-Plugin-Authentication-Credential-Livedoor-0.03/
livedoor Auth API for Catalyst.
----
Class-C3-0.15_05
http://search.cpan.org/~blblack/Class-C3-0.15_05/
A pragma to use the C3 method resolution order algortihm
----
Coro-3.61
http://search.cpan.org/~mlehmann/Coro-3.61/
coroutine process abstraction
----
Dyer-Autosort-1.03
http://search.cpan.org/~leocharre/Dyer-Autosort-1.03/
sort and unsort client files to and from incoming
----
Dyer-Autosort-1.04
http://search.cpan.org/~leocharre/Dyer-Autosort-1.04/
sort and unsort client files to and from incoming
----
Email-MIME-Creator-1.453
http://search.cpan.org/~rjbs/Email-MIME-Creator-1.453/
Email::MIME constructor for starting anew.
----
Gaim-Log-Parser-0.07
http://search.cpan.org/~mschilli/Gaim-Log-Parser-0.07/
Parse Gaim's Log Files
----
HTML-Menu-TreeView-0.5.1
http://search.cpan.org/~lze/HTML-Menu-TreeView-0.5.1/
----
JSON-DWIW-0.08
http://search.cpan.org/~dowens/JSON-DWIW-0.08/
JSON converter that Does What I Want
----
Kwiki-LivedoorAuth-0.01
http://search.cpan.org/~yappo/Kwiki-LivedoorAuth-0.01/
Kwiki LivedoorAuth integration
----
Lemonldap-Portal-Standard-3.2.0
http://search.cpan.org/~egerman/Lemonldap-Portal-Standard-3.2.0/
Perl extension for the Lemonldap SSO system
----
Lingua-FR-Ladl-v0.0.4
http://search.cpan.org/~ingrif/Lingua-FR-Ladl-v0.0.4/
represent, query and investigate the Ladl tables, a french linguistic resource
----
Linux-Taskstats-Read-3.03
http://search.cpan.org/~scottw/Linux-Taskstats-Read-3.03/
Read Linux taskstats structures
----
Net-DRI-0.80
http://search.cpan.org/~pmevzek/Net-DRI-0.80/
Interface to Domain Name Registries/Registrars/Resellers
----
Parse-QTEDI-0.03
http://search.cpan.org/~dongxu/Parse-QTEDI-0.03/
Parse QT/KDE preprocessed headers
----
Parse-QTEDI-0.04
http://search.cpan.org/~dongxu/Parse-QTEDI-0.04/
Parse QT/KDE preprocessed headers
----
Perl6-Perldoc-v0.0.4
http://search.cpan.org/~dconway/Perl6-Perldoc-v0.0.4/
Use Perl 6 documentation in a Perl 5 program
----
URI-Template-0.05
http://search.cpan.org/~bricas/URI-Template-0.05/
Object for handling URI templates
----
wxPerl-Constructors-v0.0.3
http://search.cpan.org/~ewilhelm/wxPerl-Constructors-v0.0.3/
parameterized constructors
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
------------------------------
Date: 19 Apr 2007 23:01:54 -0700
From: somedeveloper@gmail.com
Subject: Newbie queston on Perl and lex.
Message-Id: <1177048914.825711.40980@p77g2000hsh.googlegroups.com>
Hi,
1. If my needs are only lexical scanning (and not compiler- and
interpretor-writing), and
2. If I'm proficient in Perl and Perl regular expressions,
would I ever need to learn a tool such as f/lex? Is there anything
that Perl REs cannot do easily/elegantly which f/lex can, for example?
Many thanks,
Some Developer.
------------------------------
Date: 20 Apr 2007 06:10:13 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.7 $)
Message-Id: <46285944$0$3162$ae4e5890@news.nationwide.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.7 $)
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://www.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 that they do
know and are being the "bad kind" of Lazy.
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: 19 Apr 2007 19:47:36 -0700
From: jayjuliano@optonline.net
Subject: Re: Server For Rent? Where?
Message-Id: <1177037256.166368.213940@n59g2000hsh.googlegroups.com>
On Apr 18, 2:48 pm, skieros <nikos1...@gmail.com> wrote:
> Hello iam thinkignt o start a web design + domain registration +
> hosting company on my own and i want to ask you if you know where can
> i find reliable an very cheap servers for rent. Thank you.
Reliable and Cheap can't be used in the same sentence. Also, what's
cheap to one may not be cheap to another. You *CAN* lease dedicated
servers for as little as $59 a month but that particular computer
could be thrown together in under $250.
The BEST thing you can do (financially and performance wise) is to
build your own server then send you're server to a housing facility
that will provide you with IP addresses and a fast connection. This is
called co-location. Most big web hosts and ISPs that offer Dedicated
Server will have a co-location service. This is a good way to save on
monthly costs but you're still looking anywheres from $60 to a couple
hundred a month.
*IF* you cannot afford either routes you can always get a VPS (Virtual
Private Server). Just like the name suggests it's a virtual server
hosted on a dedicated server. Though it's a shared environment the
Memory, Resources, and Space are dedicated and guaranteed for each
VPS. VPS's will run anywheres from $29/month up to $99/month.
*IF* a VPS is too expensive for you then it would be a good idea to
get a Web Host that offers a RESELLERS ACCOUNT. This is Shared Hosting
in a Shared Environment but it's usually dirt cheap. You can charge
your customers whatever but a portion must go to the Web Host. This is
the easiest way to do what you seek. This will cost you anywheres from
$8-$49 per month.
*IF* that is too expensive than you must be reminded that it takes
money to make money and if you are planning to make solid money than
it is a wise idea to invest in your project.
There are too many Web Hosts out there. Since you mentioned $5/month
in another post I won't even bother showing you any servers. You can
check out http://www.jaguarpc.net for shared hosting.
>
> I askes this in other forums as well but i also asked here
It's poor netiquette, selfish, and greedy to clutter usenet with cross
posts hoping to get your answer faster. It's better to take a little
more time to find the appropriate on-topic group to post your question
in to ensure the response you want. I was just being nice to you.
> you people are on the business of web design/programmign
Perl has nothing to do with the World Wide Web. In fact, most people
here don't know how to program Perl for the web. In the late 90's Perl
became the language of choice for CGI applications but Perl was never
written nor meant to be used for the internet. You apparently didn't
know, which is not a big deal. But Jurgen Exner Tad McClellan, and
Michele Dondi are classic anti-social dorks who don't know how to
socially interact with other PEOPLE.
> and there is a good chanc of you know...
There really wasn't. A newsgroup focused on Web Hosts or Web Masters
probably would of been a better choice.
Check out
http://www.jaguarpc.net
http://www.communitech.net
http://www.ev1servers.net
All good companies that offer Reseller Programs.
Also check out http://www.godaddy.com to become a reseller for Domain
Names too. I believe Dotster also has a program.
------------------------------
Date: Thu, 19 Apr 2007 22:13:33 -0800
From: Greg Jetter <greg@lazymountain.com>
Subject: Re: Top Turds of comp.lang.perl.misc (2007)
Message-Id: <132gmh7t0l3r104@corp.supernews.com>
Ed Jay wrote:
> You're just a kid. 9600 baud? I was around for the 110 baud audio-coupled
> modems. In those days we didn't post at all. :-)
dam I still got a mini thats got a 110 baud modem ... zilog z80 it's now
used as a plant stand in the office <G>... man i feel old...
Greg
--
"You are what you is" - Frank Zappa
------------------------------
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 V11 Issue 362
**************************************
