From vannwms at mindspring.com  Fri Aug 25 22:31:39 2000
From: vannwms at mindspring.com (Valerie Vann-Williams)
Date: Thu Aug  5 00:08:04 2004
Subject: [HRPM] "My class" program
Message-ID: <LPBBILCMIGKIAHAICKDNIEBMCAAA.vannwms@mindspring.com>

I finished correcting my first perl program we reviewed in class today. I
have another problem... the program only works with whole numbers.  Can you
give me a hint?  How should I proceed?

I'm going to start on the same program using hashes now.

Your assistance is greatly appreciated.
Valerie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Myclass
Type: application/octet-stream
Size: 1848 bytes
Desc: not available
Url : http://mail.pm.org/archives/norfolk-pm/attachments/20000825/cc1068c0/Myclass.obj
From chicks at chicks.net  Wed Aug  2 07:42:10 2000
From: chicks at chicks.net (chicks@chicks.net)
Date: Thu Aug  5 00:08:07 2004
Subject: [HRPM] Yung Park's email address
Message-ID: <Pine.LNX.4.10.10008020840590.27949-100000@yakko>

Does anybody know Yung Park's new email address?  Maybe Yung?  :-)  The
address I had for him at ODU is bouncing.

-- 
</chris>

There are two ways of constructing a software design. One way is to make
it so simple that there are obviously no deficiencies. And the other way
is to make it so complicated that there are no obvious deficiencies.
                                                        - - C.A.R. Hoare


From jduffy at semcor.com  Wed Aug  2 08:31:32 2000
From: jduffy at semcor.com (jeff)
Date: Thu Aug  5 00:08:07 2004
Subject: [HRPM] Yung Park's email address
References: <8525692F.00466CD7.00@NTMTA2.semcor.com>
Message-ID: <398822B4.837D9C1E@semcor.com>

chicks@chicks.net wrote:
> 
> Does anybody know Yung Park's new email address?  Maybe Yung?  :-)  The
> address I had for him at ODU is bouncing.

 I left a message on his voicemail. I'l get it when I talk to him later.

 Jeff

From chicks at chicks.net  Thu Aug  3 13:49:08 2000
From: chicks at chicks.net (chicks@chicks.net)
Date: Thu Aug  5 00:08:07 2004
Subject: [HRPM] Very cool looking XML module.
Message-ID: <Pine.LNX.4.10.10008031448490.1803-100000@yakko>

http://www.cpan.org/modules/by-module/XML/RHANSON/XML-EasyOBJ-1.0.readme

-- 
</chris>

There are two ways of constructing a software design. One way is to make
it so simple that there are obviously no deficiencies. And the other way
is to make it so complicated that there are no obvious deficiencies.
                                                        - - C.A.R. Hoare


From jduffy at semcor.com  Thu Aug  3 13:55:39 2000
From: jduffy at semcor.com (Jeff Duffy)
Date: Thu Aug  5 00:08:07 2004
Subject: [HRPM] Very cool looking XML module.
References: <85256930.0066AE15.00@NTMTA.semcor.com>
Message-ID: <3989C02B.3EA93BAA@semcor.com>

chicks@chicks.net wrote:
> 
> http://www.cpan.org/modules/by-module/XML/RHANSON/XML-EasyOBJ-1.0.readme
> 

 I could see a few cases where this could be useful, but I like the
event-based structure of XML::Parser. This module really requires you to
know the layout of the document first (Of course, if there's a DTD, you
could just parse that and use it as a template for code generation).

 I was playing a bit with XML::Parser a couple of weeks ago, and it's
very cool to be able to say "Everytime you encounter a <chapter>
element, do this". You could do the same thing with the above, but you
would end up with like fifty nested loops (although I was just reading
about the concept of buillding factory objects, which would fit in well
there).

 Jeff
-- 
"I can't afford to make exceptions.  I mean once word leaks out that a
pirate 
has gone soft people begin to disobey him, and its nothing but work,
work, work 
all the time."
	-- The Dread Pirate Roberts

From chicks at chicks.net  Fri Aug 11 23:06:31 2000
From: chicks at chicks.net (chicks@chicks.net)
Date: Thu Aug  5 00:08:07 2004
Subject: [HRPM] Re: [twuug] Address change
In-Reply-To: <3994277C.6B170D31@nfx.net>
Message-ID: <Pine.LNX.4.10.10008112350120.2177-100000@yakko>

On Fri, 11 Aug 2000, firespring wrote:
> I must have missed the first part of this thread.

Not really.  I don't think anything has been mentioned about it on the
list.

> Was someone talking about offering PERL classes somewhere?

The local Hampton Roads Perl Mongers ( http://norfolk.pm.org ) put on a
free perl class this Spring at Semcor.  Plans for a Fall class are being
considered and would have been held at Semcor again if Jeff hadn't
switched jobs!  Work has been going on for several months to vastly
improve the content being taught.  A full public announcement of that
should come out in the next month or so.

-- 
</chris>

There are two ways of constructing a software design. One way is to make
it so simple that there are obviously no deficiencies. And the other way
is to make it so complicated that there are no obvious deficiencies.
                                                        - - C.A.R. Hoare


From webmaster at udtseals.com  Mon Aug 21 12:37:49 2000
From: webmaster at udtseals.com (Michael Theiss)
Date: Thu Aug  5 00:08:07 2004
Subject: [HRPM] scaler or array and why?
Message-ID: <002b01c00b96$8682e8a0$c301a8c0@alphas.com>

Hello all,
I'm working with a web page that includes several .shtml files that I'm
using for a master template.

Question: I need to put all of parsed and interpolated output of
master_htm.pl  page into a variable that will then be assigned to an array.
Should I put master_htm.pl into a scaler or an array and can you give me an
ideal how to approach that. Thanks in advance.

Michael Theiss

webmaster@udtseals.com



To view the current output of master_htm.pl
http://www.udtseals.com/cgi-bin/0/warrior_links0/templates/master_htm.pl

master_htm.pl
----------------------------------------------------------------------------
----------------------------------------------------------------------------
---------
#!/usr/bin/perl

print "Content-type: text/html\n\n";
print "<head>\n";
print "<!--START META DATA -->\n";
{
&PostIt;
}
print "<!--END META DATA -->\n";
print "<link rel='stylesheet' type='text/css' href='/style.css'
title='style' />\n";
{
&PostIt0;
}
print "</head>\n";
print "<body>\n";
print "<!--START HEADER -->\n";
{
&PostIt1;
}
print "<!--FINISH HEADER -->\n";
print "<!--START OUTER TABLE -->\n";
{
&PostIt2;
}
print "<!--FINISH LEFT TABLE -->\n";
print "<!--START MIDDLE TABLE -->\n";
{
&PostIt3;
}
print "<!--START BODY CONTENT -->\n";
print "<!--START INNER MIDDLE TABLE -->\n";
print "<table width='100%' bgcolor='#6b736b' border='0'>\n";
print "<tr><td align='center'>\n";



print "<form method='POST' action='category.cgi?display=form'>\n";
print "<p align='center'>&nbsp;<select size='1' name='category'>\n";
print "<option value='NULL..Category' selected>Quick Jump To</option>\n";
print "<option value='/'>Main</option>\n";
print "<!--CATEGORY OPTIONS-->\n";
print "</select><input type='submit' value='GO' name='B1'></p>\n";
print "</form>\n";
print "<h5 align='center'>[<a href='$add_url'>Add</a>] [<a
href='/cgi-bin/0/warrior_links0/main.cgi'>Search</a>]&nbsp;</h5>\n";


print "<p>!INSERT!</p>\n";





print "</td></tr>\n";
print "</table></td></tr>\n";
print "</table></td>\n";
print "<!--FINISH INNER MIDDLE TABLE -->\n";
print "<!--FINISH BODY CONTENT -->\n";
print "<!--START RIGHT TABLE -->\n";
{
&PostIt4;
}
print "<!--FINISH  OUTER TABLE -->\n";
print "<!--START FOOTER -->\n";
{
&PostIt5;
}
#print "<!--#echo
var='LAST_MODIFIED'-->&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<!--#e
cho var='DATE_LOCAL'-->\n";
print "<!--FINISH CONTAINER TABLE -->\n";
print "</body>\n";
print "</html>\n";



sub PostIt
{
$postit="/home/alphaudt/www/cgi-bin/0/includes/meta_data.shtml";

open (POST,$postit) || die "can't open $postout";
$postit="";
while (<POST>){$postit .=$_;}
close(POST);

print "$postit";

}


sub PostIt0
{
$postit="/home/alphaudt/www/cgi-bin/0/includes/onmouseover.shtml";

open (POST,$postit) || die "can't open $postout";
$postit="";
while (<POST>){$postit .=$_;}
close(POST);

print "$postit";

}


sub PostIt1
{
$postit="/home/alphaudt/www/cgi-bin/0/includes/header.shtml";

open (POST,$postit) || die "can't open $postout";
$postit="";
while (<POST>){$postit .=$_;}
close(POST);

print "$postit";

}


sub PostIt2
{
$postit="/home/alphaudt/www/cgi-bin/0/includes/left_nav_table.shtml";

open (POST,$postit) || die "can't open $postout";
$postit="";
while (<POST>){$postit .=$_;}
close(POST);

print "$postit";

}


sub PostIt3
{
$postit="/home/alphaudt/www/cgi-bin/0/includes/start_middle_table.shtml";

open (POST,$postit) || die "can't open $postout";
$postit="";
while (<POST>){$postit .=$_;}
close(POST);

print "$postit";

}


sub PostIt4
{
$postit="/home/alphaudt/www/cgi-bin/0/includes/right_table.shtml";

open (POST,$postit) || die "can't open $postout";
$postit="";
while (<POST>){$postit .=$_;}
close(POST);

print "$postit";

}


sub PostIt5
{
$postit="/home/alphaudt/www/cgi-bin/0/includes/footer.shtml";

open (POST,$postit) || die "can't open $postout";
$postit="";
while (<POST>){$postit .=$_;}
close(POST);

print "$postit";

}
1;
----------------------------------------------------------------------------
------------------------------------------------------------------




From jeff at alanne.com  Wed Aug 23 01:47:22 2000
From: jeff at alanne.com (jeff)
Date: Thu Aug  5 00:08:07 2004
Subject: [HRPM] scaler or array and why?
References: <002b01c00b96$8682e8a0$c301a8c0@alphas.com>
Message-ID: <39A3737A.F929DC0A@alanne.com>

Michael Theiss wrote:

> Question: I need to put all of parsed and interpolated output of
> master_htm.pl  page into a variable that will then be assigned to an array.

 Well, I have a couple of (maybe helpful) comments:

0. Always 'use strict'. Always. Always always always.'-w' is a good idea
too.

1. Anytime you find yourself writing the same code multiple times, it's
a good bet that you can genericize it down to one. Why not make all of
your PostIt() subs a single sub, and pass it arguments instead?
Something like:

   From the calling code:

my $filename =
"/home/alphaudt/www/cgi-bin/0/includes/onmouseover.shtml";
&post_it($filename);


   The sub:

sub post_it{
    my $filename = shift;
    open(FILE, $filename) or die "can't open $filename: $!\n";
    local $/ = undef;
    my $whole_file = <POST>;
    close(FILE) or die "Error closing $filename: $!\n";
    print $whole_file;
}


   Better yet, stuff the names of your files into an array and use that
to call the sub:

my @files = qw( /home/alphaudt/www/cgi-bin/0/includes/onmouseover.shtml
		/home/alphaudt/www/cgi-bin/0/includes/meta_data.shtml
		you_get_the_idea );

    Then just:

&post_it( $files[0] );
&post_it( $files[1] );

 This lets you change everything in one neat place, if you need to.



# Neat recursive explanation
2. A neat trick to slurp in the contents of a file is to make a local
copy of the $/ variable (the input record separator, normally a
newline). Instead of:

while (<POST>){$postit .=$_;}

you do:

 local $/ = undef;
 my $whole_file = <POST>; #slurp it all into one scalar 



3. Use here documents for printing multiple lines. Instead of:

print "Content-type: text/html\n\n";
print "<head>\n";
print "<!--START META DATA -->\n";

 do this:

print <<END;
Content-type: text/html

<head>
<!--START META DATA -->
END



4. The thing about saving it to a scalar is that your output is going to
STDOUT, not your script. You can get around this by wrapping the whole
thing in an eval{} block, like so:

my $output = eval{

print <<END;
Content-type: text/html

<head>
<!--START META DATA -->
END
...
&post_it( $files[0] );
...
&post_it( $files[1] );
...
 };


 I'm not sure what good this does you, since you end up with the entire
output in a scalar, but nowhere for it to go. Also keep in mind that
this approach can consume copious amounts of memory, since you're
stuffing everything into a variable.

 Reference the Camel book for more. Hope this helps.

 Jeff

From chicks at chicks.net  Wed Aug 23 12:31:27 2000
From: chicks at chicks.net (chicks@chicks.net)
Date: Thu Aug  5 00:08:07 2004
Subject: [HRPM] scaler or array and why?
In-Reply-To: <39A3737A.F929DC0A@alanne.com>
Message-ID: <Pine.LNX.4.10.10008231307210.19590-100000@yakko>

On Wed, 23 Aug 2000, jeff wrote:
> Michael Theiss wrote:
> > Question: I need to put all of parsed and interpolated output of
> > master_htm.pl  page into a variable that will then be assigned to an array.
> 
>  Well, I have a couple of (maybe helpful) comments:

I'm going to make a couple of nits about your helpful comments. ;-)  [ For
the uninitiated, Jeff and I maintain some friendly harassment about our
different styles of getting things accomplished in perl.  TIMTOWTDI. ]

> 0. Always 'use strict'. Always. Always always always.'-w' is a good
> idea too.

Always use '-w'.  'use strict' is usually a good idea.  :-)  If I'm
writing something I'm going to throw away after one use, use strict isn't
worth the trouble.  For anything mod_perl, serious applications
programming, anything with more than 3 functions, then always 'use
strict'.  Sometimes 'strict' is just too much of a pain.  When i was doing
lots of CGI programming and working with alternative name spaces for
variables the program just wouldn't work under a total use strict.

> 1. Anytime you find yourself writing the same code multiple times,
> it's a good bet that you can genericize it down to one. Why not make
> all of your PostIt() subs a single sub, and pass it arguments instead?
> Something like:
> 
>    From the calling code:
> 
> my $filename =
> "/home/alphaudt/www/cgi-bin/0/includes/onmouseover.shtml";
> &post_it($filename);

The ampersand (&) is only necessary for perl4 compatibility or creating
references and it's basically ugly for just a plain call.

>    The sub:
> 
> sub post_it{
>     my $filename = shift;
>     open(FILE, $filename) or die "can't open $filename: $!\n";
>     local $/ = undef;
>     my $whole_file = <POST>;
>     close(FILE) or die "Error closing $filename: $!\n";
>     print $whole_file;
> }

If you take the newline off the die it will give you the line number which
is usually pretty helpful.

>    Better yet, stuff the names of your files into an array and use that
> to call the sub:
> 
> my @files = qw( /home/alphaudt/www/cgi-bin/0/includes/onmouseover.shtml
> 		/home/alphaudt/www/cgi-bin/0/includes/meta_data.shtml
> 		you_get_the_idea );
> 
>     Then just:
> 
> &post_it( $files[0] );
> &post_it( $files[1] );

foreach $file (@files) { post_it($file); } # :-)

> 3. Use here documents for printing multiple lines. Instead of:
> 
> print "Content-type: text/html\n\n";
> print "<head>\n";
> print "<!--START META DATA -->\n";
> 
>  do this:
> 
> print <<END;
> Content-type: text/html
> 
> <head>
> <!--START META DATA -->
> END

You can also just let your data be a big quoted string:

print 'Content-type: text/html

<head>
<!--START META DATA -->
';

I used single quotes in this case and I recommend doing so by default.  If
you need interpolation you can switch to double quotes and escape all the 
bad characters.

-- 
</chris>

There are two ways of constructing a software design. One way is to make
it so simple that there are obviously no deficiencies. And the other way
is to make it so complicated that there are no obvious deficiencies.
                                                        - - C.A.R. Hoare


From jeff at alanne.com  Thu Aug 24 18:27:03 2000
From: jeff at alanne.com (jeff)
Date: Thu Aug  5 00:08:07 2004
Subject: [HRPM] scaler or array and why?
References: <Pine.LNX.4.10.10008231307210.19590-100000@yakko>
Message-ID: <39A5AF47.70529BC0@alanne.com>

chicks@chicks.net wrote:


> When i was doing
> lots of CGI programming and working with alternative name spaces for
> variables the program just wouldn't work under a total use strict.

 I might agree more with this, but Perl 5.6 introduced 'our', which lets
you declare a variable as global and still maintain the lexical scoping
requirements of the strict pragma. I use to complain loudly about having
to write things like $Foo::var in order to 'use strict', but now it's
just an issue of how lazy you want to be.


> The ampersand (&) is only necessary for perl4 compatibility or creating
> references and it's basically ugly for just a plain call.

 Okay, in this case I agree. 

> If you take the newline off the die it will give you the line number which
> is usually pretty helpful.

 Also cool.


> >    Better yet, stuff the names of your files into an array and use that
> > to call the sub:
> >
> > my @files = qw( /home/alphaudt/www/cgi-bin/0/includes/onmouseover.shtml
> >               /home/alphaudt/www/cgi-bin/0/includes/meta_data.shtml
> >               you_get_the_idea );
> >
> >     Then just:
> >
> > &post_it( $files[0] );
> > &post_it( $files[1] );

> foreach $file (@files) { post_it($file); } # :-)

 Bzzzzt! He wanted to incorporate other data between the output of each
sub. Here, you are running the outputs together, which doesn't do what
he was looking for.


> print 'Content-type: text/html
> 
> <head>
> <!--START META DATA -->
> ';
> 
> I used single quotes in this case and I recommend doing so by default.  If
> you need interpolation you can switch to double quotes and escape all the
> bad characters.

 This is also cool, but I was trying to give him the option of
interpolating the output of the subs as scalars so the whole page could
be printed at once. Using single quotes increases the number of print
statements by the number of subs, which I consider ugly.

 Having said all that, I would probably take another approach to
generating the content in any case, pulling in the HTML from somewhere
else and using pure Perl to automagically glue it all together.
TIMTOWTDI.

 Jeff

From twebster at pcs.cnu.edu  Fri Aug 25 09:03:30 2000
From: twebster at pcs.cnu.edu (Troy E. Webster)
Date: Thu Aug  5 00:08:07 2004
Subject: [HRPM] scaler or array and why?
In-Reply-To: <39A5AF47.70529BC0@alanne.com>
Message-ID: <Pine.GSO.4.02A.10008250954200.12735-100000@dufferin>

Hey all,

I am getting random messages from this list. I seem to sometimes get
answers with no questions or vice-versa. Is there some problem with the
mailing list? I would really like to benefit from peoples' problems and
solutions, but it seems like I don't get every message.

On the hrpm web site, the mailing list is norfolk-pm-list@hfb.pm.org.,
but I also sometimes get messages from norfolk-pm-list@happyfunball.pm.org

Which one is correct, or are both? Obviously, hfb stands for happyfunball,
but which one should I submit questions to? Or does it matter?

Also, isn't there supposed to be a meeting soon, like next week?

Not complaining, just curious ...

Troy Webster


From chicks at chicks.net  Fri Aug 25 12:16:19 2000
From: chicks at chicks.net (chicks@chicks.net)
Date: Thu Aug  5 00:08:07 2004
Subject: [HRPM] list screwiness
In-Reply-To: <Pine.GSO.4.02A.10008250954200.12735-100000@dufferin>
Message-ID: <Pine.LNX.4.10.10008251313060.25623-100000@yakko>

On Fri, 25 Aug 2000, Troy E. Webster wrote:

> I am getting random messages from this list. I seem to sometimes get
> answers with no questions or vice-versa. Is there some problem with
> the mailing list? I would really like to benefit from peoples'
> problems and solutions, but it seems like I don't get every message.
> 
> On the hrpm web site, the mailing list is norfolk-pm-list@hfb.pm.org.,
> but I also sometimes get messages from
> norfolk-pm-list@happyfunball.pm.org
> 
> Which one is correct, or are both? Obviously, hfb stands for
> happyfunball, but which one should I submit questions to? Or does it
> matter?

I'm not sure what the story with the mailing list is.  I haven't noticed
that I've been missing any.  Has anyone else noticed spurious list
behavior?  I can run the list off my own list server if necessary.

> Also, isn't there supposed to be a meeting soon, like next week?

Yeah.  I'll send out an official announcement today.

-- 
</chris>

There are two ways of constructing a software design. One way is to make
it so simple that there are obviously no deficiencies. And the other way
is to make it so complicated that there are no obvious deficiencies.
                                                        - - C.A.R. Hoare



From mpatten at exis.net  Fri Aug 25 17:02:57 2000
From: mpatten at exis.net (Mike Patten)
Date: Thu Aug  5 00:08:07 2004
Subject: [HRPM] list screwiness
In-Reply-To: <Pine.LNX.4.10.10008251313060.25623-100000@yakko>
Message-ID: <Pine.LNX.4.10.10008251706240.28974-100000@freya.newvalhalla.net>

On Fri, 25 Aug 2000 chicks@chicks.net wrote:

> I'm not sure what the story with the mailing list is.  I haven't noticed
> that I've been missing any.  Has anyone else noticed spurious list
> behavior?  I can run the list off my own list server if necessary.

I haven't seen anything that would indicate a problem.  (i.e. all the
answers I've seen also had questions and my questions have been answered--
although it's been a while since I had a question.)

I hadn't seen much activity here in the last couple of weeks until a few
days ago when there was a CGI question about whether it would be better to
use scalars or an array.  I saw a reply from Jeff, one from Chris, and
Jeff's reply to Chris.

If it helps, the following lines from my .procmailrc have worked for me:

:0:
* ^Reply-To: norfolk-pm-list@happyfunball\.pm\.org
hrpm

-- 
Mike Patten <mpatten@exis.net>





From webmaster at udtseals.com  Fri Aug 25 19:35:00 2000
From: webmaster at udtseals.com (Michael Theiss)
Date: Thu Aug  5 00:08:08 2004
Subject: [HRPM] newby_Perl_copious_memory_consumer_program
Message-ID: <004f01c00ef5$782d8780$0300050a@vbch1.va.home.com>

#/usr/bin/perl -w

use strict;

##################################################################################
#**********************************************************************************
#***                   The original author of the proram is 'magic1on'
#**                    Contributing mentors: Jeff, </chris>
#**
#**                    *******This program is pre beta***********
#**
#**********************************************************************************
###This script is being written to fulfill the following need:
###1. To import 7 or more :text/html files and parse the imput with some local
###   :text/html content and then put the resulting document into a scaler
###   which will then be assigned to @master which will then be joined to one
### of 8 possible scalers listed in the sub routine below. The subroutine below
### serves as a global routine for the main.cgi script at the following url:
###  http://www.udtseals.com/cgi-bin/0/warrior_links0/main.cgi
###
###
### sub LoadTemplate {
### my($file) = @_;
### open(TEMPLATE, "$file")||&DieNice("Opening: $file -- $!");
### my @template = <TEMPLATE>;
### close(TEMPLATE);
### open(MASTER, "$t_dir/master.htm")||&DieNice("Openeing: $t_dir/master.htm");
### my @master = <MASTER>;
### close(MASTER);
### my $html = join("",@master);
### $html =~ s/!INSERT!/@template/gi;
### $html =~ s/\$version/$version/gi;
### $html =~ s/\$add_url/add\.cgi/gi;
### $html =~ s/\$search_url/search\.cgi/gi;
### $html =~ s/\$new_url/whatsnew\.cgi/gi;
### $html =~ s/\$old_url/whatsold\.cgi/gi;
### $html =~ s/\$random_url/random\.cgi/gi;
### $html =~ s/<!--CATEGORY OPTIONS-->/$category_options/gi;
### return $html;
### }
###
###2. In order to test the result of the 7 :text/html files and the local :text/html
### being parsed and put into a scaler, I am attempting to print the resulting $scaler
###   to standard output first, by calling it from the following url:
###  http://www.udtseals.com/cgi-bin/0/warrior_links0/templates/master1.pl
###
###3. Then I will assign the resulting $scaler to the @master
###   and test the full output of the subroutine by calling main.cgi from a client/web
###   browser from the following url:
###  http://www.udtseals.com/cgi-bin/0/warrior_links0/main.cgi
###
###4. The orriginal request that I posted to the HRPM contained a script called master0.pl.
### master0.pl was the first pre beta attempt to parse the 7: text/html files and
### print to standard output. master0.pl is below and the output can be viewed live
### by calling it from the following url:
###  http://www.udtseals.com/cgi-bin/0/warrior_links0/templates/master0.pl
###
###    Below is the original script master0.pl
###
### print "Content-type: text/html\n\n";
### print "<head>\n";
### print "<!--START META DATA -->\n";
### {
###  &PostIt;
### }
### print "<!--END META DATA -->\n";
### print "<link rel='stylesheet' type='text/css' href='/style.css'
### title='style' />\n";
### {
### &PostIt0;
### }
### print "</head>\n";
### print "<body>\n";
### print "<!--START HEADER -->\n";
### {
### &PostIt1;
### }
### print "<!--FINISH HEADER -->\n";
### print "<!--START OUTER TABLE -->\n";
### {
### &PostIt2;
### }
### rint "<!--FINISH LEFT TABLE -->\n";
### print "<!--START MIDDLE TABLE -->\n";
### {
### &PostIt3;
### }
### print "<!--START BODY CONTENT -->\n";
### print "<!--START INNER MIDDLE TABLE -->\n";
### print "<table width='100%' bgcolor='#6b736b' border='0'>\n";
### print "<tr><td align='center'>\n";
### print "<form method='POST' action='category.cgi?display=form'>\n";
### print "<p align='center'>&nbsp;<select size='1' name='category'>\n";
### print "<option value='NULL..Category' selected>Quick Jump To</option>\n";
### print "<option value='/'>Main</option>\n";
### print "<!--CATEGORY OPTIONS-->\n";
### print "</select><input type='submit' value='GO' name='B1'></p>\n";
### print "</form>\n";
### print "<h5 align='center'>[<a href='$add_url'>Add</a>] [<a
### href='/cgi-bin/0/warrior_links0/main.cgi'>Search</a>]&nbsp;</h5>\n";
### print "<p>!INSERT!</p>\n";
### print "</td></tr>\n";
### print "</table></td></tr>\n";
### print "</table></td>\n";
### print "<!--FINISH INNER MIDDLE TABLE -->\n";
### print "<!--FINISH BODY CONTENT -->\n";
### print "<!--START RIGHT TABLE -->\n";
### {
### &PostIt4;
### }
### print "<!--FINISH  OUTER TABLE -->\n";
### print "<!--START FOOTER -->\n";
### {
### &PostIt5;
### }
### #print "<!--#echo
### var='LAST_MODIFIED'-->&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<!--#e
### cho var='DATE_LOCAL'-->\n";
### print "<!--FINISH CONTAINER TABLE -->\n";
### print "</body>\n";
### print "</html>\n";
###  sub PostIt
### {
### $postit="/home/alphaudt/www/cgi-bin/0/includes/meta_data.shtml";
### open (POST,$postit) || die "can't open $postout";
### $postit="";
### while (<POST>){$postit .=$_;}
### close(POST);
### print "$postit";
### }
###   sub PostIt0
### {
### $postit="/home/alphaudt/www/cgi-bin/0/includes/onmouseover.shtml";
### open (POST,$postit) || die "can't open $postout";
### $postit="";
### while (<POST>){$postit .=$_;}
### close(POST);
### print "$postit";
###  }
### sub PostIt1
### {
### $postit="/home/alphaudt/www/cgi-bin/0/includes/header.shtml";
### open (POST,$postit) || die "can't open $postout";
### $postit="";
### while (<POST>){$postit .=$_;}
### close(POST);
### print "$postit";
### }
###  sub PostIt2
### {
### $postit="/home/alphaudt/www/cgi-bin/0/includes/left_nav_table.shtml";
### open (POST,$postit) || die "can't open $postout";
### $postit="";
### while (<POST>){$postit .=$_;}
### close(POST);
### print "$postit";
### }
###  sub PostIt3
### {
### $postit="/home/alphaudt/www/cgi-bin/0/includes/start_middle_table.shtml";
### open (POST,$postit) || die "can't open $postout";
### $postit="";
### while (<POST>){$postit .=$_;}
### close(POST);
### print "$postit";
### }
### sub PostIt4
### {
### $postit="/home/alphaudt/www/cgi-bin/0/includes/right_table.shtml";
### open (POST,$postit) || die "can't open $postout";
### $postit="";
### while (<POST>){$postit .=$_;}
### close(POST);
### print "$postit";
### }
###  sub PostIt5
### {
### $postit="/home/alphaudt/www/cgi-bin/0/includes/footer.shtml";
### open (POST,$postit) || die "can't open $postout";
### $postit="";
### while (<POST>){$postit .=$_;}
### close(POST);
### print "$postit";
### }
### 1;
###
###
### The above script master0.pl ran without errors, however the script was
### way too redundant and contained no method for putting the resulting
### document into a $scaler which ultimately needs to be assigned to the
### @master in the subroutine shown above. Due to my inexperience, I needed
### to ask for help in accomplishing the talk. That's when I submitted the
### above script to the HRPM list and the rest is history. Jeff and Chris,
### thanks a million for your help and your professional approach to the
### request. I will see to it that full credit is given to all who contribute.
###
###
###5. After submitting the above master0.pl script to the HRPM list, I was given
### the following advice listed below:
###**********************************************************************************
#********Jeff Wrote***********
# Well, I have a couple of (maybe helpful) comments:
# 0. Always 'use strict'. Always. Always always always.'-w' is a good idea
# too.
# 1. Anytime you find yourself writing the same code multiple times, it's
# a good bet that you can genericize it down to one. Why not make all of
# your PostIt() subs a single sub, and pass it arguments instead?
# Something like:
# From the calling code:
#
#my $filename =
#"/home/alphaudt/www/cgi-bin/0/includes/onmouseover.shtml";
#&post_it($filename);
#
#   The sub:
#
#sub post_it{
#    my $filename = shift;
#    open(FILE, $filename) or die "can't open $filename: $!\n";
#    local $/ = undef;
#    my $whole_file = <POST>;
#    close(FILE) or die "Error closing $filename: $!\n";
#    print $whole_file;
#}
#
#   Better yet, stuff the names of your files into an array and use that
#to call the sub:
#
#my @files = qw( /home/alphaudt/www/cgi-bin/0/includes/onmouseover.shtml
#/home/alphaudt/www/cgi-bin/0/includes/meta_data.shtml
#you_get_the_idea );
#
#    Then just:
#
#&post_it( $files[0] );
#&post_it( $files[1] );
#
# This lets you change everything in one neat place, if you need to.
#
#
#
# Neat recursive explanation
#2. A neat trick to slurp in the contents of a file is to make a local
#copy of the $/ variable (the input record separator, normally a
#newline). Instead of:
#
#while (<POST>){$postit .=$_;}
#
#you do:
#
# local $/ = undef;
# my $whole_file = <POST>; #slurp it all into one scalar
#
#
#3. Use here documents for printing multiple lines. Instead of:
#
#print "Content-type: text/html\n\n";
#print "<head>\n";
#print "<!--START META DATA -->\n";
#
# do this:
#
#print <<END;
#Content-type: text/html
#
#<head>
#<!--START META DATA -->
#END
#
#
#
#4. The thing about saving it to a scalar is that your output is going to
#STDOUT, not your script. You can get around this by wrapping the whole
#thing in an eval{} block, like so:
#
#my $output = eval{
#
#print <<END;
#Content-type: text/html
#
#<head>
#<!--START META DATA -->
#END
#...
#&post_it( $files[0] );
#...
#&post_it( $files[1] );
#...
# };
#
#
# I'm not sure what good this does you, since you end up with the entire
#output in a scalar, but nowhere for it to go. Also keep in mind that
#this approach can consume copious amounts of memory, since you're
#stuffing everything into a variable.
#
# Reference the Camel book for more. Hope this helps.
#
# Jeff
#*********************************************************************************
#****Chris Wrote*******
#I'm going to make a couple of nits about your helpful comments. ;-)  [ For
#the uninitiated, Jeff and I maintain some friendly harassment about our
#different styles of getting things accomplished in perl.  TIMTOWTDI. ]
#
# 0. Always 'use strict'. Always. Always always always.'-w' is a good
# idea too.
#
#Always use '-w'.  'use strict' is usually a good idea.  :-)  If I'm
#writing something I'm going to throw away after one use, use strict isn't
#worth the trouble.  For anything mod_perl, serious applications
#programming, anything with more than 3 functions, then always 'use
#strict'.  Sometimes 'strict' is just too much of a pain.  When i was doing
#lots of CGI programming and working with alternative name spaces for
#variables the program just wouldn't work under a total use strict.
#
#1. Anytime you find yourself writing the same code multiple times,
# it's a good bet that you can genericize it down to one. Why not make
# all of your PostIt() subs a single sub, and pass it arguments instead?
# Something like:
#
#    From the calling code:
#
# my $filename =
# "/home/alphaudt/www/cgi-bin/0/includes/onmouseover.shtml";
# &post_it($filename);
#
#The ampersand (&) is only necessary for perl4 compatibility or creating
#references and it's basically ugly for just a plain call.
#
#    The sub:
#
# sub post_it{
#     my $filename = shift;
#     open(FILE, $filename) or die "can't open $filename: $!\n";
#     local $/ = undef;
#     my $whole_file = <POST>;
#     close(FILE) or die "Error closing $filename: $!\n";
#     print $whole_file;
# }
#
#If you take the newline off the die it will give you the line number which
#is usually pretty helpful.
#
#    Better yet, stuff the names of your files into an array and use that
# to call the sub:
#
# my @files = qw( /home/alphaudt/www/cgi-bin/0/includes/onmouseover.shtml
# /home/alphaudt/www/cgi-bin/0/includes/meta_data.shtml
# you_get_the_idea );
#
#     Then just:
#
# &post_it( $files[0] );
# &post_it( $files[1] );
#
#foreach $file (@files) { post_it($file); } # :-)
#
# 3. Use here documents for printing multiple lines. Instead of:
#
# print "Content-type: text/html\n\n";
# print "<head>\n";
# print "<!--START META DATA -->\n";
#
#  do this:
#
# print <<END;
# Content-type: text/html
#
#<head>
# <!--START META DATA -->
# END
#
#You can also just let your data be a big quoted string:
#
#print 'Content-type: text/html
#
#<head>
#<!--START META DATA -->
#';
#
#I used single quotes in this case and I recommend doing so by default.  If
#you need interpolation you can switch to double quotes and escape all the
#bad characters.
#
#--
#</chris>
#
#There are two ways of constructing a software design. One way is to make
#it so simple that there are obviously no deficiencies. And the other way
#is to make it so complicated that there are no obvious deficiencies.
#                                                        - - C.A.R. Hoare
#*************************************************************************
#********Jeff Wrote***********
# When i was doing
# lots of CGI programming and working with alternative name spaces for
# variables the program just wouldn't work under a total use strict.
#
#I might agree more with this, but Perl 5.6 introduced 'our', which lets
#you declare a variable as global and still maintain the lexical scoping
#requirements of the strict pragma. I use to complain loudly about having
#to write things like $Foo::var in order to 'use strict', but now it's
#just an issue of how lazy you want to be.
#
#
# The ampersand (&) is only necessary for perl4 compatibility or creating
# references and it's basically ugly for just a plain call.
#
#Okay, in this case I agree.
#
# If you take the newline off the die it will give you the line number which
# is usually pretty helpful.
#
#Also cool.
#
#
#    Better yet, stuff the names of your files into an array and use that
# to call the sub:
#
# my @files = qw( /home/alphaudt/www/cgi-bin/0/includes/onmouseover.shtml
#               /home/alphaudt/www/cgi-bin/0/includes/meta_data.shtml
#               you_get_the_idea );
#
#     Then just:
#
# &post_it( $files[0] );
# &post_it( $files[1] );
#
# foreach $file (@files) { post_it($file); } # :-)
# Bzzzzt! He wanted to incorporate other data between the output of each
#sub. Here, you are running the outputs together, which doesn't do what
#he was looking for.
#
#
# print 'Content-type: text/html
#
# <head>
# <!--START META DATA -->
# ';
#
# I used single quotes in this case and I recommend doing so by default.  If
# you need interpolation you can switch to double quotes and escape all the
# bad characters.
#
#This is also cool, but I was trying to give him the option of
#interpolating the output of the subs as scalars so the whole page could
#be printed at once. Using single quotes increases the number of print
#statements by the number of subs, which I consider ugly.
#
#Having said all that, I would probably take another approach to
#generating the content in any case, pulling in the HTML from somewhere
#else and using pure Perl to automagically glue it all together.
#TIMTOWTDI.
#
# Jeff
#************************************************************************************
###
###
###
###
###
###
###
###*******Below is the revised version of the master0.pl that I am working
###*******on now. The script executes with no errors, however, the output is
###*******not correct because the subroutine is failing and the scalers are
###*******not returning the values in the resulting document.
###*******the below script can be called from the url below, but it does
###*******not produce the desired output yet:
###*******http://www.udtseals.com/cgi-bin/0/warrior_links0/templates/master1.pl
###*******
###*******
###****************ANY ADVICE ON OBVIOUS FLAWS IN THE CODE BELOW WOULD BE
###****************HELPFULL. I will be away from computers for until after
###****************Labor day. I am going on my yearly retreat. Gonna get
###****************freaky with nature up in michigan..Going camping....
###****************Thanks ahead of time for all your help and expertise.
###****************I will continue work on this program on Sep. 05, 2000
#######################################################################################
#######################################################################################

'
@files = qw
(/cgi-bin/0/includes/meta_data.shtml,/cgi-bin/0/includes/onmouseover.shtml,/cgi-bin/0/includes/header.shtml,/cgi-bin/0/includes/left
_nav_table.shtml,/cgi-bin/0/includes/start_middle_table.shtml,/cgi-bin/0/includes/right_table.shtml,/cgi-bin/0/includes/footer.shtml
);

my $output = eval{

print Content-type: text/html

<head>
<!--START META DATA -->
END

&post_it( $files[0] );

<!--END META DATA -->
<link rel='stylesheet' type='text/css' href='/style.css' title='style' />

&post_it( $files[1] );

</head>
<body>
<!--START HEADER -->

&post_it ( $files[2] );

<!--FINISH HEADER -->
<!--START OUTER TABLE -->

&post_it ( $files[3] );

<!--FINISH LEFT TABLE -->
<!--START MIDDLE TABLE -->

&post_it ( $files[4] );

<!--START BODY CONTENT -->
<!--START INNER MIDDLE TABLE -->
<table width='100%' bgcolor='#6b736b' border='0'>
<tr><td align='center'>
<form method='POST' action='category.cgi?display=form'>
<p align='center'>&nbsp;<select size='1' name='category'>
<option value='NULL..Category' selected>Quick Jump To</option>
<option value='/'>Main</option>
<!--CATEGORY OPTIONS -->
</select><input type='submit' value='GO' name='B1'></p>
</form>
<h5 align-'center'>[<a href='/cgi-bin/0/warrior_links0/add.cgi'>Add</a>] [<a
href="/cgi-bin/0/warrior_links0/main.cgi">Search</a>]&nbsp;</h5>

<p>!INSERT!</p>


</td></tr>
</table></td></tr>
</table></td>
<!--FINISH INNER MIDDLE TABLE -->
<!--FINISH BODY CONTENT -->
<!--START RIGHT TABLE -->

&post_it ( $files[5] );

<!--FINISH OUTER TABLE -->
<!--START FOOTER -->

&post_it ( $files[6] );

<!--FINISH CONTAINER TABLE -->
</body>
</html>


while (<POST>){$postit .=$_;}

print "$file";




sub post_it{
    my $files = shift;
    open(FILE, $files) or die "can't open $files: $!\n";
    local $/ = undef;
    my $file = <POST>;
    close(FILE) or die "Error closing $files: $!\n";
    print $file;
    }
}
';"


From chicks at chicks.net  Fri Aug 25 20:52:53 2000
From: chicks at chicks.net (chicks@chicks.net)
Date: Thu Aug  5 00:08:08 2004
Subject: [HRPM] 30 August - HRPM Meeting Announcement
Message-ID: <Pine.LNX.4.10.10008251817190.25623-100000@yakko>

 Please pass the word on for the next Hampton Roads Perl Mongers meeting:
 
 What:         The monthly Hampton Roads Perl Mongers Meeting
               http://norfolk.pm.org/

 Who:          Everyone in Hampton Roads interested in perl.  There
               are no dues or signup requirements.  All are welcome to
               attend.
 
 Where:        The meetings were alternating between Chesapeake and
               Newport News, but due to a change in employment, we're
               currently without a Chesapeake place to meet.  August's
               meeting will be at the Jefferson Lab in Newport News.
               Directions on the web and below.
 
 When:         7:30 PM till whenever on Wednesday 30 August 2000
               It's generally going to be on the last Wednesday of the
               month unless major holidays intervene.  (This puts us
               consistantly one week before TWUUG.)
 
 Why:          Why not?  What could be better than to come and talk with
               others about the world's most fun programming language?
               Jabber, learn, teach, enjoy.  Starbucks is not far away.
 
 Agenda:       Whatever people on the HRPM mailing list decide!
               Various people who do perl rather often will be
               there to answer your perl questions.  Some expected
               topics are on the site.

               **    This month Jeff is scheduled to present a
                     talk on Object Oriented Perl.
 
 Directions:   http://norfolk.pm.org/location.shtml

               (This is an improvement on last month's
               directions thanks to an anonmous source.
               I had no idea the other directions sent people
               so far out of the way.  My apologies. - chicks)

               Take 64 until you get to the exit for Oyster Point West.

               Upon exiting, you will be on Oyster Point Road headed
               toward Jefferson Ave. (If, after exiting, you find yourself
               approaching the Kiln Creek shopping center and passing Farm
               Fresh and Kmart, you've exited in the wrong direction, so
               turn around.)  The third light ahead, and the biggest
               intersection, is Jefferson Ave.

               Turn left onto Jefferson and go to the second light. On
               your left is Jefferson Lab. On your right is Dixie Trailer
               park.

               Turn left into Jefferson Lab (Onnes Road) and go about 100
               yards to the T-intersection at which Onnes ends.

               Turn right and check in at the guard shack.

               Turn around and head (in between all the flag poles)
               directly to CEBAF Center where the meeting will be held.

               Turn right just before you reach the circular drive in
               front of CEBAF Center, and park in the parking lot you will
               see on your left.

               Find your way into the building and to the building atrium.
               The atrium is right off the circular drive.

               Room L104 branches off the atrium on the right.











From chicks at chicks.net  Sat Aug 26 14:46:58 2000
From: chicks at chicks.net (chicks@chicks.net)
Date: Thu Aug  5 00:08:08 2004
Subject: [HRPM] Damian Conway interview on www.perl.com
Message-ID: <Pine.LNX.4.10.10008261543410.31033-100000@yakko>

www.perl.com has posted an interview with Damian Conway.  Highly
recommended reading.  Here's the relevant excerpt from this weeks
www.perl.com update:

'
Joe surprised me by producing, apparently from nowhere, an interview with
Dr. Damian Conway.  Dr. Conway is the author of the excellent book _Object
Oriented Perl_ and the three-time winner of the annual Larry Wall award
for Practical Utility, for modules such as Parse::RecDescent, which writes
parser programs in Perl, and Coy, which turns all your error messages into
haiku.  Joe's interview with Dr. Conway is available at:

	http://www.perl.com/pub/2000/08/conway.html
';

Enjoy.

-- 
</chris>

There are two ways of constructing a software design. One way is to make
it so simple that there are obviously no deficiencies. And the other way
is to make it so complicated that there are no obvious deficiencies.
                                                        - - C.A.R. Hoare


From chicks at chicks.net  Sat Aug 26 14:49:41 2000
From: chicks at chicks.net (chicks@chicks.net)
Date: Thu Aug  5 00:08:08 2004
Subject: tidbit regarding [HRPM] mailing list foibles
Message-ID: <Pine.LNX.4.10.10008261547340.31033-100000@yakko>

Since Troy's concerns have made me a little more attentive to mailing list
issues, I've noticed that my HRPM/TWUUG cross-posts come through from the
HRPM list a bit faster than they come through on TWUUG.

-- 
</chris>

There are two ways of constructing a software design. One way is to make
it so simple that there are obviously no deficiencies. And the other way
is to make it so complicated that there are no obvious deficiencies.
                                                        - - C.A.R. Hoare