On Feb 11, 2010, at 3:18, newbie01 perl wrote:
> Hi all,
>
> I am wanting some advise/input on setting up some sort of intranet site to
> allow system operators to manage the servers, mostly UNIX servers and some
> Windows. I am constrained by not being able to install new modules or a
> databas
On 2/10/10 Wed Feb 10, 2010 6:18 PM, "newbie01 perl"
scribbled:
> Hi all,
>
> I am wanting some advise/input on setting up some sort of intranet site to
> allow system operators to manage the servers, mostly UNIX servers and some
> Windows. I am constrained by not being able to install new mod
On Thu, Feb 11, 2010 at 10:18 AM, newbie01 perl wrote:
>
> I need some guidance if someone know of any existing set of CGI-BIN scripts
> that I can just plug it and used for this purpose.
>
Will you run the scripts under the share hosting environment?
If so you are very hard to get the applicati
Hi all,
I am wanting some advise/input on setting up some sort of intranet site to
allow system operators to manage the servers, mostly UNIX servers and some
Windows. I am constrained by not being able to install new modules or a
database, for example, MySQL. The web server will be Apache. Given t
> "SHC" == Shawn H Corey writes:
SHC> Uri Guttman wrote:
>>
>> computers don't hate you. you hate yourself and so you commit bad code
>> full of bugs. self flagelation programmer style! :)
SHC> No, it comes from maintaining other people's bad code for too
SHC> many years. It me
Uri Guttman wrote:
>> "SHC" == Shawn H Corey writes:
>
> SHC> Uri Guttman wrote:
> >>> "SHC" == Shawn H Corey writes:
> SHC> Call it paranoid defensive programming. ;)
> >>
> >> overly paranoid imo. but that doesn't mean the bugs aren't out to get
> >> ya! :)
>
> SHC> Ju
> "SHC" == Shawn H Corey writes:
SHC> Uri Guttman wrote:
>>> "SHC" == Shawn H Corey writes:
SHC> Call it paranoid defensive programming. ;)
>>
>> overly paranoid imo. but that doesn't mean the bugs aren't out to get
>> ya! :)
SHC> Just because you're not paranoid doesn't
Uri Guttman wrote:
>> "SHC" == Shawn H Corey writes:
> SHC> Call it paranoid defensive programming. ;)
>
> overly paranoid imo. but that doesn't mean the bugs aren't out to get
> ya! :)
Just because you're not paranoid doesn't mean computers don't hate me.
--
Just my 0.0002 million
> "SHC" == Shawn H Corey writes:
SHC> Uri Guttman wrote:
>>> "SHC" == Shawn H Corey writes:
>>
SHC> Uri Guttman wrote:
>> >> why the || '' ??
>> >>
>> >> the help sub doesn't seem to exit/die
>>
SHC> Not proven; you cannot assume this.
>>
SHC> One school of thou
Uri Guttman wrote:
>> "SHC" == Shawn H Corey writes:
>
> SHC> Uri Guttman wrote:
> >> why the || '' ??
> >>
> >> the help sub doesn't seem to exit/die
>
> SHC> Not proven; you cannot assume this.
>
> SHC> One school of thought about programming is that all functions must have
>
> "SHC" == Shawn H Corey writes:
SHC> Uri Guttman wrote:
>> why the || '' ??
>>
>> the help sub doesn't seem to exit/die
SHC> Not proven; you cannot assume this.
SHC> One school of thought about programming is that all functions must have
SHC> only one return and all programs
Shawn H Corey wrote:
> Uri Guttman wrote:
>> why the || '' ??
>>
>> the help sub doesn't seem to exit/die
>
> Not proven; you cannot assume this.
>
> One school of thought about programming is that all functions must have
> only one return and all programs must have only one exit. Therefore,
> h
Uri Guttman wrote:
> why the || '' ??
>
> the help sub doesn't seem to exit/die
Not proven; you cannot assume this.
One school of thought about programming is that all functions must have
only one return and all programs must have only one exit. Therefore,
help() may return or it may not.
Unti
> "SHC" == Shawn H Corey writes:
SHC> John W. Krahn wrote:
>> Shawn H Corey wrote:
>>> Steve Bertrand wrote:
You can replace them all with this:
my $station = $channels{ $opt_s };
>>>
>>> my $station = $channels{ $opt_s } || help();
>>
>> my $station = $c
Shawn H Corey wrote:
> John W. Krahn wrote:
>> Shawn H Corey wrote:
>>> Steve Bertrand wrote:
You can replace them all with this:
my $station = $channels{ $opt_s };
>>> my $station = $channels{ $opt_s } || help();
>> my $station = $channels{ $opt_s } or help();
>
>
> my $station =
John W. Krahn wrote:
> Shawn H Corey wrote:
>> Steve Bertrand wrote:
>>> You can replace them all with this:
>>>
>>> my $station = $channels{ $opt_s };
>>
>> my $station = $channels{ $opt_s } || help();
>
> my $station = $channels{ $opt_s } or help();
my $station = $channels{ $opt_s } || '' or h
Shawn H Corey wrote:
Steve Bertrand wrote:
You can replace them all with this:
my $station = $channels{ $opt_s };
my $station = $channels{ $opt_s } || help();
my $station = $channels{ $opt_s } or help();
Or:
( my $station = $channels{ $opt_s } ) || help();
John
--
The programmer is figh
Steve Bertrand wrote:
> You can replace them all with this:
>
> my $station = $channels{ $opt_s };
my $station = $channels{ $opt_s } || help();
Make sure help() ends with `return;` or `exit();`
--
Just my 0.0002 million dollars worth,
Shawn
Programming is as much about organization and
Steve Bertrand wrote:
> trapd...@trapd00r.se wrote:
>> On 08/12/09 23:15 -0500, Steve Bertrand wrote:
>>> To the OP, without code, it makes it difficult to tell what you are
>>> after.
>> Sorry, tired... :) Here's the code
>
> You didn't cc the list ;)
>
>> #!/usr/bin/perl
>> use strict;
>> use
trapd...@trapd00r.se wrote:
> On 08/12/09 23:15 -0500, Steve Bertrand wrote:
>> To the OP, without code, it makes it difficult to tell what you are
>> after.
>
> Sorry, tired... :) Here's the code
You didn't cc the list ;)
> #!/usr/bin/perl
> use strict;
> use warnings;
Nice.
> use diagnostic
> "AHA" == Alan Haggai Alavi writes:
>> Hello,
>>
>> I would like to have someone looking over my script, which is a basic
>> frontend for playing radio with mplayer. In particular, I'm wondering how I
>> could get rid of all those elsif's when parsing the arguments; as you can
>
>Hello,
>
>I would like to have someone looking over my script, which is a basic
>frontend for playing radio with mplayer. In particular, I'm wondering how I
>could get rid of all those elsif's when parsing the arguments; as you can
>see, there's lots of them, and I suspect that there's a better wa
> "SB" == Steve Bertrand writes:
SB> Uri Guttman wrote:
>>> "t" == trapd00r writes:
>>
t> I would like to have someone looking over my script, which is a
t> basic frontend for playing radio with mplayer. In particular, I'm
t> wondering how I could get rid of all those elsif
Uri Guttman wrote:
>> "t" == trapd00r writes:
>
> t> I would like to have someone looking over my script, which is a
> t> basic frontend for playing radio with mplayer. In particular, I'm
> t> wondering how I could get rid of all those elsif's when parsing the
> t> arguments; as you
> "t" == trapd00r writes:
t> I would like to have someone looking over my script, which is a
t> basic frontend for playing radio with mplayer. In particular, I'm
t> wondering how I could get rid of all those elsif's when parsing the
t> arguments; as you can see, there's lots of them,
Hello,
I would like to have someone looking over my script, which is a basic
frontend for playing radio with mplayer. In particular, I'm wondering how I
could get rid of all those elsif's when parsing the arguments; as you can
see, there's lots of them, and I suspect that there's a better way of
26 matches
Mail list logo
