HDTenEightyP/NetNews huggingface dataset:
From: lwall@netlabs.com (Larry Wall)
Newsgroups: comp.lang.perl
Subject: Re: Flushing DBM file cache
Date: 10 Apr 92 01:12:27 GMT
Organization: NetLabs, Inc.

In article <DRW.92Apr4000517@kronecker.mit.edu> drw@kronecker.mit.edu (Dale R. Worley) writes:
: When I have a DBM file opened as an associative array via dbmopen(),
: is there any way to flush the cached values in memory?  It looks like
: reset can do this, but reset is a bit, uh, all-inclusive.  Is there
: any operation that can flush the cache for a single associative array?

There's no other way to do it currently apart from using dbmopen()
again, but with reset you can put it into its own package, which would
restrict the scope of the reset.

(You listen-in-ers note that we're talking about flushing the in-memory
cached values to the bit bucket, not flushing dirty values to the file,
since the cache is write-through.  Presumably you'd want to do this if
you were notified that someone else wrote to the file.)

Larry
Newsgroups: comp.lang.perl
From: forrie@morwyn.uucp (System Administrator)
Subject: Next release of perl (5.0?)
Date: Mon, 13 Apr 1992 21:05:27 GMT
Organization: VISION GRAPHICS - Dover, NH - USA
X-Bytes: 417

Anyone know when the next release of Perl is due out (v5.0?)... just
curious.

-- 
           -----------        Forrest Aldrich         -----------
           -------     morwyn!forrie@unhtel.unh.edu       -------
           ----                                              ---- 
           --        VISION GRAPHICS -- Dover, NH - USA        --
           ------------------------------------------------------
Newsgroups: comp.lang.perl
From: mab@wdl39.wdl.loral.com (Mark A Biggar)
Subject: Re: The '$.' variable: misleading.
Organization: Loral Western Development Labs
Date: Tue, 7 Apr 1992 15:35:26 GMT

In article <1992Apr7.064858.10841@nuscc.nus.sg> ccechk@nuscc.nus.sg (Heng Kek) writes:
>It appears (after some testing) that the '$.' variable doesn't
>really return the current line number.  It seems to be counting
>newline chars rather than give the absolute line number. ...

Well it depends on your definition of "Current line number".  Yes Perl just
counts the number of \n's read on the given filehandle, but thats because
that is Unix's definition of a line (some possible empty string of text
terminated by a \n).

>...  I
>discovered this with the following testcode:
>while(<infile>){
>	if(/$pattern/){
>		print "cur line num is = $.\n";
>		seek(infile, -40, 1); #'rewind 40 chars from current
>	}
>}
>Where '40' is sufficient to place the file pointer before
>$pattern.  The result is: the current line number printed keeps
>increasing when one would expect it to be the same.
>Any comments on this?  Also, is there an existing function to
>'rewind' a file by 'x' lines (instead of chars)?

If order to provide what you want, every time you did a negative seek you would
have to read the whole section of the file seeked over to count the number of
\n's so it could be subtracted from $. (or be clairvoyant).  If you really
need to do line oriented seeking you will have to keep an array of seek
positions yourself.  For example see how perldb.pl does it.

--
Perl's Maternal Uncle
Mark Biggar
mab@wdl1.wdl.loral.com

Xref: sparky comp.lang.perl:3122 comp.sys.hp:5164
From: moconnor@pms704.pms.ford.com (Mike O'Connor)
Newsgroups: comp.lang.perl,comp.sys.hp
Subject: Re: Problem compiling perl on hp9000/730 running hp-ux 8.05
Date: 12 Apr 92 16:59:27 GMT
Article-I.D.: fmsrl7.1992Apr12.165927.25478
Reply-To: Mike O'Connor <mjo@fmsrl7.srl.ford.com>
Organization: "Fordz"
X-Disclaimer: Not an official spokesperson for Ford Motor Co.

In article <9204121040.AA19923@menora.weizmann.ac.il> dov@menora.weizmann.ac.il (Dov Grobgeld) writes:

:I have tried to unsuccesfully tried to compile perl on our new
:hp9000/730 running hp-ux 8.05.
:
:I ran the Configure script, chose hpux for default values, accepted all
:values, ran makedepend, and then make.
:
:Compilation goes smoothly, except a couple of warnings of the form
:
:  cc: Optdriver 2003 basic blocks; defaulting to level 1 optimization.
:  Use +Obb<num> with num >= the number given in this message. (6059)
:
:on some modules.

Help is on the way.

Under HP-UX 8.05, you have two solutions:

1.  Compile in debug mode (cc -g)
2.  Upgrade to HP-UX 8.07

Under HP-UX 8.07, the caveat is:  Use HP's own malloc rather than
perl's.  I would recommend doing this under 8.05 as well, but I don't
recall if I HAD to do that to get perl to work.

						...Mike

-- 
 Mike O'Connor                     |  Ford Motor Company, USA
 Applications Systems Analyst      |  CPD P&MS ECC Core Software
 Phone #:  +1 (313) 390-4008       |  P.O. Box 2053, ECC MD-7
 Fax #:    +1 (313) 845-0576       |  Dearborn, MI  48121-2053
Newsgroups: comp.lang.perl
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: help with type glob -- UNIX 3.2.4
Originator: tchrist@pixel.convex.com
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Realtime Development, Colorado Springs, CO
Distribution: usa
Date: Fri, 10 Apr 1992 20:22:43 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

From the keyboard of watson@carssdf.UUCP (- Self Empl. Sys.Integrator):
:I need help from ONE PERSON, but I don't know how to limit it to that,
:so first, if you are reading this after Monday morning, stop here.  Also
:I've limited the distribution to USA only, so my waste of bandwidth is
:atleast cheaper bandwidth.

which monday morning? :-)

:
:I'm trying to debug why 'TYPE GLOB' aka 'PASS BY NAME' doesn't work for me.
:Two previous postings with no response suggest that no-one else has the
:problem ... so I'm on my own.
:
:If you are also running patch level 19 (current I think) AND
:you are configured with -DDEBUGGING and ...
:
:If this program prints OK for you, please run it with -D1040, and email
:me the results to      rutgers!carssdf!watson
:Or if I've made a stupid mistake I need to know that too.
:
:-------- cut here -------
:
:$x = 'OK';
:&mysub($x);
:
:sub mysub {
:  local (*y) = @_;
:  print $y,"\n";
:}

I'm going to post this instead of mailing it because I think it a common
mistake.  If you think of perl *foo objects as C pointers, it'll make more
sense.  You've done essentially this:

    main() {
	int a;
	mysub(a);
    } 
    mysub(int *a) {
	printf("%d\n", *a);
    } 

That is, you passed a scalar as the actual parameter, but declared it a
pointer in the formal parameter, so it didn't work.  Perl is a little
more forgiving that C, in that you get no answer instead of a core dump,
but sometimes doing the wrong thing with perl pointers will get you thing.

Can we write a perl lint that catches type mismatches between pointers
and regular objects?  Not quite, because there are some very rare
instances where you *do* want to play fast and loose between scalars
and pointers, but certainly when you first start using them, I wouldn't
suggest it.


--tom
From: cscon105@uoft02.utoledo.edu
Newsgroups: comp.lang.perl
Subject: VMS perl command line params? how?
Date: 12 Apr 92 16:13:46 EST
Organization: University of Toledo, Computer Services


How can I pass command line parameters to perl scripts under VMS???

Under Unix, you just need to make a script with the top line in the
script being

#!/usr/bin/perl
program here

But VMS doesn't work this way.

Thanks,

Bryan Kruzynski
cscon105@uoft02.utoledo.edu
From: ajay@acsu.buffalo.edu (Ajay Shekhawat)
Newsgroups: comp.lang.perl
Subject: Re: Malloc problems in perl
Date: 9 Apr 92 04:43:20 GMT
Organization: University at Buffalo, Dept. of Computer Science

utashiro@InterTech.COM (Kazumasa Utashiro) writes:
: In article <1992Apr5.072818.4196@acsu.buffalo.edu> I'd written
:  >I'm using Kazumasa Utashiro's Multi-line Grep (mg), posted here
:  >a few days ago. It's a neat script, but it is giving me a "Bus Error"
:  >when I do a recursive grep on a large number of files, and there are
:  >a few matches.
:  >This is perl, version 4.0
:  >Patch level: 10
: 
: I got a segmentation fault on our IPX with perl4.010 too.
: But there is no problem with perl4.019 compiled with system
: standard malloc.  I tried it for whole /usr directory.  So
: updating your perl to 4.019 will solve the problem.
: 
: --utashiro

Doesn't help. I downloaded Perl 4.019 today, compiled it (gcc 2.1) and
tried it again. This time it ran for longer, and it didn't give a
Bus Error; instead it gave a Segmentation Fault.

I tried it with the system standard malloc, and without it. Same result.

Is anyone else having this kind of a problem?  I'm on a Sun4, SunOS 4.1.1.

This thing's got me stymied  :-(

Ajay S.
--
ajay@cs.Buffalo.EDU
Newsgroups: comp.lang.perl
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: printf conflict with $#
Originator: tchrist@pixel.convex.com
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Realtime Development, Colorado Springs, CO
Distribution: usa
Date: Fri, 17 Apr 1992 18:54:27 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

From the keyboard of lukas@cbnewsc.cb.att.com (LUKAS):
:Can anyone explain why this simple program:
:
:	$# = "%.6g";
:	printf ("%15f", 43);
:	print "\n";
:
:produces for output:
:
:	43
:
:instead of the expected (and desired):
:
:	      43.000000
:
:(15 characters with leading spaces)? If I remove the reference
:to $#, the program works ok. Why should setting $# affect printf?
:BTW, setting $#, and then setting it back to its default of "%.20g"
:does NOT return printf to a working state.

This has come up before...

When $# is defined, then print will format anything that *looks* like
a number.  Numbers are allowed to have leading and trailing whitespace.

	$# = "%.4g";
	print ' .1234567  ';

Since printf(ARGS) is defined to be print sprintf(ARGS), you're
getting burned by this same problem.

As far as I can tell, if you ever muck with it, your prints (and printfs!)
go awry.  I feel that $# is basically IMHO broken, in that it violates the
principle of least astonishment (so does the way popen's fail, BTW.)   I
don't know whether it can be made sane.

--tom
Xref: sparky comp.lang.perl:3121 comp.sys.hp:5163
From: dov@menora.weizmann.ac.il (Dov Grobgeld)
Newsgroups: comp.lang.perl,comp.sys.hp
Subject: Problem compiling perl on hp9000/730 running hp-ux 8.05
Date: 12 Apr 92 16:11:05 GMT
Article-I.D.: menora.9204121040.AA19923
Organization: Mail to News Gateway

I have tried to unsuccesfully tried to compile perl on our new
hp9000/730 running hp-ux 8.05.

I ran the Configure script, chose hpux for default values, accepted all
values, ran makedepend, and then make.

Compilation goes smoothly, except a couple of warnings of the form

  cc: Optdriver 2003 basic blocks; defaulting to level 1 optimization.
  Use +Obb<num> with num >= the number given in this message. (6059)

on some modules.

The perl executable is created. Trying to run it gives core dump. Even
without a script.

The error message is:

  Segmentation fault (core dumped)

Would very much appreciate help from anyone who has managed to compile
Perl on this platform.

--
                                                        ___   ___
                                                      /  o  \   o \
Dov Grobgeld                                         ( o  o  ) o   |
The Weizmann Institute of Science, Israel             \  o  /o  o /
"Where the tree of wisdom carries oranges"              | |   | |
                                                       _| |_ _| |_
Newsgroups: comp.lang.perl
From: kherron@ms.uky.edu (Kenneth Herron)
Subject: Re: Retrieving elements of an associative array in order.
Distribution: na
Date: Wed, 15 Apr 1992 23:18:57 GMT
Organization: University Of Kentucky, Dept. of Math Sciences
X-Bytes: 

pete@egh-qc.uucp (Pete Phillips) writes:
>I'd like to be able to retrieve the elements of an associative array
>in the order in which they've been defined:

	%menu=(
		"a:quit","Exit",
		"b:about","About SMTL",
		"c:refdb","References Database",
		"d:stabdb","Stability Database",
		"e:dcarddb","Dressing Data Cards Database",
		"f:strixhelp","Help on using the Databases"
	       );
	@subs=sort(keys %menu);
		
	for ($i=0 ; $i <= $#subs; $i++) {
		print "  $i) $menu{$subs[$i]}\n";
	}

You'll need to strip the letter and colon off the front of the
key before eval-ing it, of course.
-- 
Kenneth Herron                                       kherron@ms.uky.edu
University of Kentucky                                  +1 606 257 2975
Department of Mathematics
                                              Flame early, flame often.
From: ajay@acsu.buffalo.edu (Ajay Shekhawat)
Newsgroups: comp.lang.perl
Subject: Malloc problems in perl
Date: 5 Apr 92 07:28:18 GMT
Organization: University at Buffalo, Dept. of Computer Science

I'm using Kazumasa Utashiro's Multi-line Grep (mg), posted here
a few days ago. It's a neat script, but it is giving me a "Bus Error"
when I do a recursive grep on a large number of files, and there are
a few matches. Here's a script: (Maybe someone else would like to try
the following and let me know if the same thing happens on their m/c also?)
------------------------------------------
Script started on Sun Apr  5 03:18:35 1992
> pwd
/util/math/Packages
> mg -Ri chord *
Corrupt malloc ptr 0x66696e69 at 0x6e800
Corrupt malloc ptr 0x66696e69 at 0x6e800
> mg -Ri triangle * > /dev/null
Corrupt malloc ptr 0x66696e69 at 0x6e800
Bus error
> ^D
script done on Sun Apr  5 03:19:21 1992
---------------------------------------

The machine is a Sun4 running SunOS 4.1.1.

perl -v gives:
This is perl, version 4.0
$RCSfile: perl.c,v $$Revision: 4.0.1.4 $$Date: 91/06/10 01:23:07 $
Patch level: 10


Is there anyway I can fix this bug or find out what's going wrong?

Any help would be appreciated...Thanks!

Ajay S.
--
ajay@cs.Buffalo.EDU
From: jmay@ctp.com (Jason May)
Newsgroups: comp.lang.perl
Subject: reset behavior: bug or feature?
Date: 15 Apr 92 17:03:22 GMT
Organization: Cambridge Technology Partners


The perl reset function clears the selected variables or arrays, but they
remain defined.  For example:

    if (defined $a) {
	print "a is defined: $a\n";
    }
    else {
	print "a is not defined\n";
    }

    $a = "foo";

    if (defined $a) {
	print "a is defined: $a\n";
    }
    else {
	print "a is not defined\n";
    }


    reset 'a';

    if (defined $a) {
	print "a is defined: $a\n";
    }
    else {
	print "a is not defined\n";
    }

will give:

a is not defined
a is defined: foo
a is defined:


Is this a bug?  I would like a way to undefine many variables at once, so
that I can use 'if defined' checks later on on those variables.

-Jason
(jmay@ctp.com)
From: olson@mcs.anl.gov (Bob Olson)
Newsgroups: comp.lang.perl
Subject: Re: Converting Perl to x
Date: 8 Apr 92 17:26:09 GMT
	<1992Mar31.123903.19397@micromuse.co.uk>
	<1992Apr7.134733.16894@ctp.com>
Organization: Math & Computer Science Divison, ANL

This brings up something that I've been thinking about for a while.
What we could do is define 'Pidgin Perl': that subset of perl that is
easy to compile. We would need to

    o	Regularize the syntax to make it easy to parse 
	(require parens around all function invocations, say)
    o	Disallow eval
    o	Disallow s///e and anything else that wants to use eval
    o	Place strict restrictions on the use of lexically scoped
	variables; perhaps requiring that all variables are either
	globally or locally declared (globally declared meaning
		&Pidgin'DeclareGlobal(varname)
    o	And whatever else makes it difficult to compile to C.

I claim what we would have left would still be a quite useful
langauge, especially since you could still do the development in Perl,
only compiling down to C when needed.

--bob

--
   Bob Olson   -*-   olson@mcs.anl.gov   -*-   Argonne National Laboratory
     "You can't win a game of chess with an action figure!" --bob&dave
Newsgroups: comp.lang.perl
From: merlyn@iWarp.intel.com (Randal L. Schwartz)
Subject: Re: Programming Perl Version
Keywords: book printing
Reply-To: merlyn@iWarp.intel.com (Randal L. Schwartz)
Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA
Date: Wed, 8 Apr 1992 21:43:54 GMT

In article <1692@toro.MTS.ML.COM>, scott@toro (Scott Strool) writes:
| I have Programming Perl First printing Jan 1991:
| 
|  Has an upgrade been published, if so how new is 
|  it. Does anybody know if there are plans for
|  a book update. 

As a semi-authoritative answer... :-)

Facts:

The January 1991 book covered Perl 4.0 (more or less)
The August 1991 book covered Perl 4.010 (more or less)
The March 1992 book covers Perl 4.010, with a 4.019 refcard

Faint, distant rumors, which may or may not come to pass,
so don't even hold your breath or pester Larry or me about it: :-)

The October 1992 book will cover Perl 5.0 (more or less)

$Camel = "Perl"; print "Just another $Camel hacker,"
-- 
/=Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ==========\
| on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III      |
| merlyn@iwarp.intel.com ...!any-MX-mailer-like-uunet!iwarp.intel.com!merlyn |
\=Cute Quote: "Intel: putting the 'backward' in 'backward compatible'..."====/
From: unikocp@uts.uni-c.dk (Ole Carsten Pedersen)
Newsgroups: comp.lang.perl
Subject: Where to find compiled MSDOS PERL?
Date: 9 Apr 92 20:50:06 GMT
Organization: UNI-C Lyngby, DK

Is PERL for MSDOS available at any server site in compiled "plugh and play" 
form?

Thanks in advance
Ole Carsten Pedersen
Ole Carsten Pedersen         Phone +45 45 93 83 55
UNI-C                        FAX   +45 45 93 02 20
Bygning 305, DTH             EMail Ole.Carsten.Pedersen@uni-c.dk
DK-2800  LYNGBY
Newsgroups: comp.lang.perl
From: bernd@euler.iss.nus.sg (Bernd Nordhausen)
Subject: Perl for commercial software?
Reply-To: bernd@iss.nus.sg (Bernd Nordhausen)
Organization: Institute of Systems Science, NUS, Singapore
Date: Tue, 7 Apr 1992 08:11:46 GMT


By now we all now what a great language perl is. However, I would like to 
hear whether people are using Perl to write commercial software.

I am in contact with a software company to do some development work for them.
When I suggested to use Perl they were extremely reluctant. As a commerical
company, they do not want to give out any source code or scripts.

So I would like to hear whether any commercial software has been developed in
Perl, and in what form it has been distributed.

Or is that people use perl only to develop prototypes that are then recoded
in C or some other compiled language?

Bernd
-- 
   Bernd Nordhausen (bernd@iss.nus.sg)
   Institute of Systems Science                           Ph: +65 772-6240 
   National University of Singapore                      FAX: +65 778-2571
   Singapore 0511                               
Newsgroups: comp.lang.perl
From: cameron@spectrum.cs.unsw.oz.au (Cameron Simpson)
Subject: Re: integer math in Perl ...
Followup-To: poster
Reply-To: cameron@spectrum.cs.unsw.oz.au (Cameron Simpson)
Organization: CS&E Computing Facility, Uni Of NSW, Oz
Date: Thu, 9 Apr 1992 08:41:54 GMT

Silly me. I ask a question on the net. I got several short and very helpful answers.
Thanks to all concerned. Then this article. Jeez.

lezz@merlin.dev.cdx.mot.com (Lezz Giles) writes:
| cameron@spectrum.cs.unsw.oz.au (Cameron Simpson) writes:
| |> Here I am converting seconds into hours/minutes/seconds:
| ...
| |> There's just _got_ to be a better method than this. But I can't find it.
| |> Maybe it's in the Camel book, but mine's on loan just now...
| 
| I never understand how somebody can write programs without the language
| manual beside them.  The answer to your problem is gmtime() - to misquote
| from the Camel book...
|     ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) =
| 	gmtime($h);

Idiot. I wasn't working from a time_t style number. Yes, gmtime() can be used to
the end I needed, but what a hack. I was just _formatting_ a number. My
question concerned integer math. Now, I had _a_ language manual beside me,
but it was for 3.0pl18, not the current version, and my Camel book was on
loan. Several people pointed out int() to me.
	- Cameron Simpson

P.S.	Naturally the person with the book returned it the morning after
	the night I posted the article. Isn't it always the way...
Newsgroups: comp.lang.perl
From: Andrew Hardie <ash@omega.uucp>
Subject: postscript file processing
Reply-To: ash@omega.uucp
Organization: The Internet
Date: Tue, 14 Apr 1992 02:42:55 GMT


Anyone out there got any perl scripts for handling Postscript files on
a page-by-page basis. What I am looking to do is take the Postscript
output from a WP program, find the page numbers, mark them and then 
de-postscript the rest of the files (text only, no graphics!), so that 
I can feed the result to an automatic index generator script which will
then index the occurrence of certain words using the page number markers.
I don't know a lot (OK, almost nothing) about Postscript, but I guess
the page boundary finding must be possible, as there are these neat
scripts for printing postscript files 2-up, 4-up, etc.
Thanks! 
Andrew
-- 
+----------------------------------------------------------------------------+
| Andrew Hardie                                               ash@omega.uucp |
| London, England                                      uknet!cctal!omega!ash |
+----------------------------------------------------------------------------+
Newsgroups: comp.lang.perl
From: mcook@mrc.dev.cdx.mot.com (Michael Cook)
Subject: Re: looking for a C parser
Organization: Motorola Codex, Canton, Massachusetts
Date: Thu, 9 Apr 1992 12:54:53 GMT

drw@nevanlinna.mit.edu (Dale R. Worley) writes:

>Parsing ANSI C exactly correctly is a real bitch.  To do it correctly,
>you will almomst certainly have to buy a commercial parser.

And (don't tell me!) you sell one?  Written in Perl, right? :-)
-- 
 ==========================================================
 Michael.Cook@merlin.dev.cdx.mot.com          (617)821-7590
 Motorola/Codex, 20 Cabot Blvd, C2-135, Mansfield, MA 02048
 ==========================================================
From: allbery@NCoast.ORG (Brandon S. Allbery KF8NH)
Newsgroups: comp.lang.perl
Subject: Re: Converting Perl to x
Date: 11 Apr 92 17:43:41 GMT
Article-I.D.: NCoast.1992Apr11.174341.12061
Reply-To: allbery@ncoast.org (Brandon S. Allbery KF8NH)
Followup-To: comp.lang.perl
Organization: North Coast Public Access *NIX, Cleveland, OH

As quoted from <OLSON.92Apr8112609@dalek.mcs.anl.gov> by olson@mcs.anl.gov (Bob Olson):
+---------------
|     o	Disallow eval
+---------------

I would modify that to allow ``eval BLOCK;'' and also allow any eval that can
be resolved at compile time, thus permitting, say, ``eval("\$$foo")'' for
double indirection (the translator could recognize that this can be expanded
to ``{local(*__tmp_1)=*foo;$__tmp_1;}'').

+---------------
|     o	Disallow s///e and anything else that wants to use eval
+---------------

As above, certain special cases can be permitted.  However, I think it's clear
that s///ee and such are not (reasonably) doable.

+---------------
|     o	Place strict restrictions on the use of lexically scoped
| 	variables; perhaps requiring that all variables are either
| 	globally or locally declared (globally declared meaning
| 		&Pidgin'DeclareGlobal(varname)
+---------------

Or simply issue warnings for non-declared variables and entering them into the
global symbol table as an ordinary statically-declared global.  Otherwise it
wouldn't be possible to compile even simple existing scripts, because there is
currently no mechanism to "declare" globals except by mentioning them.

+---------------
| I claim what we would have left would still be a quite useful
| langauge, especially since you could still do the development in Perl,
| only compiling down to C when needed.
+---------------

I might also suggest an option to Perl to issue warnings for non-compileable
features.

++Brandon
-- 
Brandon S. Allbery, KF8NH [44.70.4.88]        allbery@NCoast.ORG
Senior Programmer, Telotech, Inc. (if I may call myself that...)