On Monday, June 24, 2002, at 01:00 PM, drieux wrote:
> > On Monday, June 24, 2002, at 11:30 , Theresa Mullin wrote: > [..] >> use Test; >> > [..] >> >> …Here is module Test: >> >> #!/usr/bin/perl >> >> ### Program Name: Test.pm >> ### Created By: Theresa Mullin >> ### Date: 5/20/02 >> >> package Test; >> >> $dbase = "TEST"; >> print "And to all a good night \n"; >> >> The code appears to execute, and no error messages are generated. > [..] > > Remember - one of the reasons we advocate that you > > perldoc h2xs > > and start there is that the code maintenance will be much > easier in the long run. > > this way you can pay the usual fun of > > perl *.PL PREFIX=~ LIB=~/lib/perl > > to play around with it.... > > cf also > > perldoc perlsub > perldoc perlmod > perldoc perlmodlib > > a little practice.... yes but there is not a place to easily grasp the idea of using h2xs. a little holdhanding would help. what it does. why we want it where it puts things how we use it why we are doing makes and make install when all we want is to do is call a subroutine in an external file... you see? saying: perl *.PL PREFIX=~ LIB=~/lib/perl is a little far past step one for us newbots. you expect us to know that *.PL file we are using. that perl takes arguments like thta using tilde for user's home, and that you have your own <home>/lib/perl. newfoos 'may' be a tad turned left. all those docs are preliminary to doing something that tends to only make sense after someone helps us toddle across the minefield. in otro vez: we are looking for a kinder, gentle interface. after hearing rave about h2xs for a few days now it is beginning to make sense. but as if i am getting to it rather non-linearly.
