[29894] in Perl-Users-Digest
Perl-Users Digest, Issue: 1137 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Dec 21 16:09:43 2007
Date: Fri, 21 Dec 2007 13:09:07 -0800 (PST)
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, 21 Dec 2007 Volume: 11 Number: 1137
Today's topics:
Re: A problem with storing a filehandle as an instance <ben@morrow.me.uk>
Re: A problem with storing a filehandle as an instance <peter@makholm.net>
Re: A problem with storing a filehandle as an instance <esniff@gmail.com>
Re: A problem with storing a filehandle as an instance <esniff@gmail.com>
Re: A problem with storing a filehandle as an instance <uri@stemsystems.com>
Re: FAQ 4.3 Why isn't my octal data interpreted correct <hjp-usenet2@hjp.at>
Re: FAQ 4.3 Why isn't my octal data interpreted correct <hjp-usenet2@hjp.at>
FileHandle messes up Oracle connection <simon.chao@fmr.com>
Re: Problem installing DBD::mysql <m@rtij.nl.invlalid>
Re: Problem installing DBD::mysql <newsmanDELETE@REMOVEdahl-stamnes.net>
Re: Problem installing DBD::mysql <newsmanDELETE@REMOVEdahl-stamnes.net>
Re: Which editor for Perl hacking are you using (John M. Gamble)
Re: Which editor for Perl hacking are you using <jurgenex@hotmail.com>
Re: Which editor for Perl hacking are you using <kkeller-usenet@wombat.san-francisco.ca.us>
Re: Which editor for Perl hacking are you using <nospam@somewhere.com>
Re: Which editor for Perl hacking are you using <veatchla@yahoo.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 21 Dec 2007 16:41:59 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: A problem with storing a filehandle as an instance variable
Message-Id: <nv6t35-5j51.ln1@osiris.mauzo.dyndns.org>
Quoth "John W. Krahn" <krahnj@telus.net>:
<snip sound advice>
>
> It is probably better to just use lexical variables for filehandles:
Unfortunately this doesn't work with open3, which is what the OP was
using.
Ben
------------------------------
Date: Fri, 21 Dec 2007 17:22:15 +0000
From: Peter Makholm <peter@makholm.net>
Subject: Re: A problem with storing a filehandle as an instance variable
Message-Id: <87r6hg2cag.fsf@hacking.dk>
Ben Morrow <ben@morrow.me.uk> writes:
> Quoth "John W. Krahn" <krahnj@telus.net>:
> <snip sound advice>
>>
>> It is probably better to just use lexical variables for filehandles:
>
> Unfortunately this doesn't work with open3, which is what the OP was
> using.
Lexical variables does work with open3 and it even shown in the
documentation, except that you have to do some magic to get the error
filhandle to work:
use Symbol;
my ($in, $out, $err);
# Generate filehandle for $err so it's not false:
$err = gensym;
my $pid = open3($in,$out,$err,'cmd');
//Makholm
------------------------------
Date: Fri, 21 Dec 2007 11:21:41 -0800 (PST)
From: Sniff <esniff@gmail.com>
Subject: Re: A problem with storing a filehandle as an instance variable
Message-Id: <cf1e9940-5ed2-4bcc-9b8d-d5d69c7227d6@e6g2000prf.googlegroups.com>
Well, I'm learning more than I ever wanted to about Perl Filehandles
and typeglob :-). I hacked at it last night and final got it to work
by doing this:
in contructor:
my $fhw = *wr{FILEHANDLE};
$self->{"WRITE"} = $fhw;
in my method:
local(*WRITE);
*WRITE = $self->{"WRITE"};
print *WRITE "$flag\n" ;
Now I'm going to take some time to absorb the info you gave me above
and incorporate that knowledge into how I'm using the handles.
Thanks to John, Ben and Makholm
------------------------------
Date: Fri, 21 Dec 2007 11:24:17 -0800 (PST)
From: Sniff <esniff@gmail.com>
Subject: Re: A problem with storing a filehandle as an instance variable
Message-Id: <a831aa4f-c4e3-4297-8f1f-18c1cc4b1601@l1g2000hsa.googlegroups.com>
On Dec 21, 11:21=A0am, Sniff <esn...@gmail.com> wrote:
> Well, I'm learning more than I ever wanted to about Perl Filehandles
> and typeglob :-). =A0I hacked at it last night and final got it to work
> by doing this:
>
> in contructor:
> =A0 =A0my $fhw =3D *wr{FILEHANDLE};
> =A0 =A0$self->{"WRITE"} =3D $fhw;
>
> in my method:
> =A0 =A0local(*WRITE);
> =A0 =A0*WRITE =A0=3D $self->{"WRITE"};
> =A0 =A0print *WRITE "$flag\n" ;
TYPO: Should be
print WRITE "$flag\n" ;
>
> Now I'm going to take some time to absorb the info you gave me above
> and incorporate that knowledge into how I'm using the handles.
>
> Thanks to John, Ben and Makholm
------------------------------
Date: Fri, 21 Dec 2007 20:56:57 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: A problem with storing a filehandle as an instance variable
Message-Id: <x7prwzpy07.fsf@mail.sysarch.com>
>>>>> "S" == Sniff <esniff@gmail.com> writes:
S> Well, I'm learning more than I ever wanted to about Perl Filehandles
S> and typeglob :-). I hacked at it last night and final got it to work
S> by doing this:
S> in contructor:
S> my $fhw = *wr{FILEHANDLE};
stop doing that! that is not doing what you think it does. it gets the
handle slot of a glob, but NOT a handle. there is NO REASON for you to
use that syntax to get a handle.
you can use IO::Handle or Symbol::gensym to get new handles. or use open
with a undefined lexical. but STOP using the above construct!
S> in my method:
S> local(*WRITE);
S> *WRITE = $self->{"WRITE"};
use a lexcial to hold handles. globs (even localized) are very old
fashioned.
my $wr = IO::Handle->new() ;
or
open( my $wr, '>', $file ) or die "can't create $file" ;
S> print *WRITE "$flag\n" ;
S> Now I'm going to take some time to absorb the info you gave me above
S> and incorporate that knowledge into how I'm using the handles.
better to forget what you know about globs and learn about lexicals and
handles.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
------------------------------
Date: Fri, 21 Dec 2007 19:36:52 +0100
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: FAQ 4.3 Why isn't my octal data interpreted correctly?
Message-Id: <slrnfmo1u4.bel.hjp-usenet2@hrunkner.hjp.at>
On 2007-12-20 15:59, brian d foy <brian.d.foy@gmail.com> wrote:
> In article <47695b7e$0$13929$fa0fcedb@news.zen.co.uk>, RedGrittyBrick
><RedGrittyBrick@SpamWeary.foo> wrote:
>> You and Peter seem to be arguing at cross-purposes. I believe Peter was
>> objecting to the final words of this part of the FAQ:
>
> That would make sense. I couldn't (an still can't) tell that from his
> original message, which quoted the entire answer.
For very small values of "entire":
The entire answer has 29 lines. I quoted the first five lines and part
of the sixth, which amounts to about 19 %. I could have snipped the
first sentence, but that would have removed the contrast between
literals in source-code and strings being processed at run-time, which I
considered relevant.
I also underlined the word "decimal". I pointed out that I didn't care
about the actual storage format, just that there is a difference between
a number and its representation as a string, and I suggested two
improvements. I don't see how I could have been more specific.
hp
------------------------------
Date: Fri, 21 Dec 2007 20:51:45 +0100
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: FAQ 4.3 Why isn't my octal data interpreted correctly?
Message-Id: <slrnfmo6ah.bel.hjp-usenet2@hrunkner.hjp.at>
On 2007-12-20 16:03, brian d foy <brian.d.foy@gmail.com> wrote:
> In article <slrnfmisf0.n0u.hjp-usenet2@hrunkner.hjp.at>, Peter J.
> Holzer <hjp-usenet2@hjp.at> wrote:
>> On 2007-12-19 17:11, brian d foy <brian.d.foy@gmail.com> wrote:
>> > In article <slrnfmg4dg.go9.hjp-usenet2@hrunkner.hjp.at>, Peter J.
>> > Holzer <hjp-usenet2@hjp.at> wrote:
>> >> > I still say that Perl numbers are decimal unless we say otherwise.
>> >>
>> >> That's easy to disprove:
>> >>
>> >> % perl -l -e 'for ($i = 0; $i != 1; $i += 0.1) { print $i }'
>> >
>> > I see Perl using the digits 0 to 9.
>> >
>> > There are underlying implementation details based on the architecture,
>> > but that's implementation. The language is not the processor or the
>> > storage. That there is some round-off error because of the limitations
>> > of computers doesn't change the fact that Perl is using the digits 0 to
>> > 9.
>>
>> You are confusing Source code and run-time. I was talking about
>> run-time.
>
> I'm not confusing them at all. The run time is not the implementation.
> You're not talking about run time either. You're talking about the
> implementation on binary computers.
The difference between "Perl" and "perl" is rather academic. Unlike
languages like C, which have a formal standard, the abstract language
"Perl" is only defined by its implementation "perl" and the assorted
documentation.
The perl documentation has little to say about numbers. Mainly it says
that scalars may be strings or numbers (or references, but we can ignore
that in this context) and that there are automatic conversions between
these two types and that an application cannot tell whether a scalar is
a string or a number (in fact, it may be both at the same time). It
doesn't define any specific format, although it does drop some hints
(for example it says that "~0 is 32 bits wide on a 32-bit platform, but
64 bits wide on a 64-bit platform", or that "printf "%.20g\n",
123456789123456789; produces 123456789123456784". An implementation with
base 10 would probably be allowed, but it certainly isn't required, and
I don't know any implementation of perl which does use base 10. You may
call that a bug, an imperfection, a deviation from the ideal Perl, but I
don't. I think this is quite intentional, and I think that a Perl
programmer should be aware that perl numbers are not decimal, despite
the automatic conversion between numbers and strings. He shouldn't
assume ANY specific representation, but he has to (some people don't
seem to be able to think in abstractions) he should get used to thinking
of Perl numbers as binary, because that's what they are on any platform
he's likely to use. Otherwise he will get bitten badly.
> The run time is just the bit that does what the op codes say. By that
> time, Perl has already decided to parse numbers. It's not a problem
> with phase.
Do you really not understand the difference between
my $x = 0377;
and
my $s = '0377';
my $x = oct($s);
?
In the first case the octal number is parsed by the compiler and
converted to some internal form. When the interpreter gets to that
statement it does't know whether the number was written in octal, hex,
or decimal in the source code. All it knows is that it has a numeric
constant.
In the second case the function oct is called with a scalar argument
which happens to be a string (I used a variable which has been assigned
a string literal in this example, but the string could have been read
from a file or a database, or be the result of some other operation).
When the interpreter reaches that statement, it calls the oct function,
which parses the string and computes a number with the equivalent value
which it then returns.
The parsing of the numbers happens at different phases of the program's
execution and it is done by different functions.
hp
------------------------------
Date: Fri, 21 Dec 2007 10:40:21 -0800 (PST)
From: nolo contendere <simon.chao@fmr.com>
Subject: FileHandle messes up Oracle connection
Message-Id: <5a1d6af8-3a97-4575-bfdd-0dacddf74fef@b1g2000pra.googlegroups.com>
I had a simple script which connected to an Oracle DB, and when I
ported the subs to a larger script, I got the following error:
DBI
connect('database=FFOSD1;sid=FFOSD1;host=fosappdaldev2;port=1521','FFOSPOCDBO',...)
failed: ERROR OCIEnvNlsCreate. Check ORACLE_HOME env var, NLS
settings, permissions, etc. at ./FFOS_CmpDriver.NEW.pl line 661
bash-2.03$ echo $ORACLE_HOME
/ffosbasedir/common/oracle/iclient10_2
I copied the head of my larger script, along with the sub to connect
to Oracle and still got the error. So I pruned various pieces of code
and discovered that commenting out 'use FileHandle;' allowed my
connection to succeed.
Anyone else notice this?
The version of Perl i'm using is:
bash-2.03$ perl -V
Summary of my perl5 (revision 5 version 8 subversion 8) configuration:
Platform:
osname=solaris, osvers=2.8, archname=sun4-solaris
uname='sunos smmk183 5.8 generic_117350-43 sun4u sparc sunw,netra-
t12 '
config_args='-Dcc=gcc -Dprefix=/ffosbasedir/common/perl'
hint=recommended, useposix=true, d_sigaction=define
usethreads=undef use5005threads=undef useithreads=undef
usemultiplicity=undef
useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
use64bitint=undef use64bitall=undef uselongdouble=undef
usemymalloc=n, bincompat5005=undef
Compiler:
cc='gcc', ccflags ='-fno-strict-aliasing -pipe -I/usr/local/
include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64',
optimize='-O',
cppflags='-fno-strict-aliasing -pipe -I/usr/local/include'
ccversion='', gccversion='3.2.3', gccosandvers='solaris2.8'
intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=4321
d_longlong=define, longlongsize=8, d_longdbl=define,
longdblsize=16
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t',
lseeksize=8
alignbytes=8, prototype=define
Linker and Libraries:
ld='gcc', ldflags =' -L/usr/local/lib '
libpth=/usr/local/lib /usr/lib /usr/ccs/lib
libs=-lsocket -lnsl -ldl -lm -lc
perllibs=-lsocket -lnsl -ldl -lm -lc
libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a
gnulibc_version=''
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' '
cccdlflags='-fPIC', lddlflags='-G -L/usr/local/lib'
Characteristics of this binary (from libperl):
Compile-time options: PERL_MALLOC_WRAP USE_LARGE_FILES USE_PERLIO
Built under solaris
Compiled at Jun 6 2007 12:34:43
%ENV:
PERL5LIB=""
@INC:
/ffosbasedir/common/perl/lib/5.8.8/sun4-solaris
/ffosbasedir/common/perl/lib/5.8.8
/ffosbasedir/common/perl/lib/site_perl/5.8.8/sun4-solaris
/ffosbasedir/common/perl/lib/site_perl/5.8.8
/ffosbasedir/common/perl/lib/site_perl
.
------------------------------
Date: Fri, 21 Dec 2007 17:17:47 +0100
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: Problem installing DBD::mysql
Message-Id: <pan.2007.12.21.16.17.46@rtij.nl.invlalid>
On Fri, 21 Dec 2007 16:13:39 +0100, Jørn Dahl-Stamnes wrote:
> Martijn Lievaart wrote:
>
>> On Fri, 21 Dec 2007 14:17:05 +0100, Jørn Dahl-Stamnes wrote:
>>
>>> I also tried to upgrade perl by using yum, but that does not work very
>>> well (see below). Perhaps I need to install perl from source?
>>
>> No, you need to straighten out your install. You have a non-FC install
>> of mysql that conflicts with the FC package. Uninstall mysql* and
>> reinstall.
>
> Hmm.. where does that one come from? I have installed FC from scratch
> (from CDs) and then tried to install the perl modules. I have not done
> anything else to install mysql.
Hmmm, 4.1.11-2 is indeed the original FC4 version. This seems to be a
repository bug in FC4. You can still uninstall mysql and reinstall, that
way you avoid this issue and are more up to date.
FC4 is old, though. You may want to upgrade. I use CentOS myself, and I
like it a lot better than Fedora in terms of stability. Otherwise, try
FC8.
This is getting very OT, but I suggest you first get your machine up to
date, and then retry. I use both Fedora and CentOS and have no issues
with the perl, mysql or DBI::mysql packages.
HTH,
M4
------------------------------
Date: Fri, 21 Dec 2007 17:24:54 +0100
From: =?ISO-8859-1?Q?J=F8rn?= Dahl-Stamnes <newsmanDELETE@REMOVEdahl-stamnes.net>
Subject: Re: Problem installing DBD::mysql
Message-Id: <476be8d6@news.broadpark.no>
Martijn Lievaart wrote:
> On Fri, 21 Dec 2007 16:01:53 +0100, Christian Winter wrote:
>> That won't solve the original problem, that Perl is linked against a
>> glibc version that isn't available any longer, therefore breaking the
>> mechanism ExtUtils::MakeMaker uses to determine linker paramters.
>
> It might solve it, as that allows to upgrade to the latest Perl. As
> suggested by you.
I tried to install/update ExtUtils::MakeMaker, but that did not solve the
problem.
--
Jørn Dahl-Stamnes
http://www.dahl-stamnes.net/dahls/
------------------------------
Date: Fri, 21 Dec 2007 17:27:50 +0100
From: =?ISO-8859-1?Q?J=F8rn?= Dahl-Stamnes <newsmanDELETE@REMOVEdahl-stamnes.net>
Subject: Re: Problem installing DBD::mysql
Message-Id: <476be986@news.broadpark.no>
Martijn Lievaart wrote:
> Hmmm, 4.1.11-2 is indeed the original FC4 version. This seems to be a
> repository bug in FC4. You can still uninstall mysql and reinstall, that
> way you avoid this issue and are more up to date.
I'll try that later.
> FC4 is old, though. You may want to upgrade. I use CentOS myself, and I
> like it a lot better than Fedora in terms of stability. Otherwise, try
> FC8.
I know. But I reinstalled it to get up the server up and running as fast as
possible after a disk crash (well, non of the disk crashed but it seems
that the logical volume information was corrupt and I was not able to boot
the system. But I was able to recover all filesystems by booting the
recovery CD and then copied all configuration to other disks).
> This is getting very OT, but I suggest you first get your machine up to
> date, and then retry. I use both Fedora and CentOS and have no issues
> with the perl, mysql or DBI::mysql packages.
I plan to upgrade from FC 4 to 5 and then to 6 and maybe up to 7. I'm not
sure if I can just go directly to 7 (have not looked into this yet).
--
Jørn Dahl-Stamnes
http://www.dahl-stamnes.net/dahls/
------------------------------
Date: Fri, 21 Dec 2007 17:54:59 +0000 (UTC)
From: jgamble@ripco.com (John M. Gamble)
Subject: Re: Which editor for Perl hacking are you using
Message-Id: <fkgulj$nq$2@e250.ripco.com>
In article <fkg321$ags$1@nntp.fujitsu-siemens.com>,
Josef Moellers <josef.moellers@fujitsu-siemens.com> wrote:
>John Bokma wrote:
>> Please no editor war, but I am curious, what's the editor of choice you're
>> using to write Perl,
>
>vim
>
vim and jedit.
>> and why (if you want to share).
>
>I started with ed, dispising full-screen-editors, then learned that vi
Huh, me too (an ed variant but same principle).
>was like ed but full-screen (and it was able to solve a maze ;-), now
(*) Maze?
>I'm using vim.
>
--
-john
February 28 1997: Last day libraries could order catalogue cards
from the Library of Congress.
------------------------------
Date: Fri, 21 Dec 2007 18:02:41 GMT
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Which editor for Perl hacking are you using
Message-Id: <pkvnm3l6qgl9urc24a17fmgbj0tn1rcgkg@4ax.com>
On 21 Dec 2007 04:52:26 GMT, John Bokma <john@castleamber.com> wrote:
>Please no editor war, but I am curious, what's the editor of choice you're
>using to write Perl, and why (if you want to share).
emacs with CPerl mode.
When I started I could never figure out how to convince vi to do what I
wanted it to do, so I switches to the most powerful editor of the time.
Not to mention that for emacs you can write your own extensions to do
whatever you can imagine.
And now 2 decades later I am still happy with it.
jue
------------------------------
Date: Fri, 21 Dec 2007 10:25:49 -0800
From: Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us>
Subject: Re: Which editor for Perl hacking are you using
Message-Id: <d2dt35xv0b.ln2@goaway.wombat.san-francisco.ca.us>
On 2007-12-21, John Bokma <john@castleamber.com> wrote:
> Please no editor war, but I am curious, what's the editor of choice you're
> using to write Perl, and why (if you want to share).
I use both vi/vim and nedit, mainly because I use vi/vim and nedit for
my other editing tasks. (I picked vi because, at the time, it was
smaller and more likely to be available on a small and/or embedded
system (like a rescue floppy (!)) than emacs.)
> I am currently using Textpad, but in the very near future I am moving to
> GNU/Linux. I've some experience with using vi(m) for editing work, and
> have printed both the emacs and vim manual, but not sure which one to
> start reading first.
Well, just from the vi/emacs standpoint, it's pretty much a religious
war (or inertial). You might as well flip a coin. For other editors, I
imagine just trying each of them for an hour or a day will be more
instructive than advice from random usenet posters. ;-)
--keith
--
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information
------------------------------
Date: Fri, 21 Dec 2007 14:10:36 -0500
From: "Thrill5" <nospam@somewhere.com>
Subject: Re: Which editor for Perl hacking are you using
Message-Id: <-aOdnUq1NdkwkvHanZ2dnUVZ_i2dnZ2d@comcast.com>
"John Bokma" <john@castleamber.com> wrote in message
news:Xns9A0CE8B10A2Ecastleamber@130.133.1.4...
> Please no editor war, but I am curious, what's the editor of choice you're
> using to write Perl, and why (if you want to share).
>
> I am currently using Textpad, but in the very near future I am moving to
> GNU/Linux. I've some experience with using vi(m) for editing work, and
> have printed both the emacs and vim manual, but not sure which one to
> start reading first.
>
ActiveState Visual Perl for Visual Studio 2003
It's a shame ActiveState choose to discontinue this product instead of
putting into the public domain, since it doesn't work with later versions of
Visual Studio. Built-in debugging support (using all the debugging features
of VS, such as breakpoints, watches, etc). The editor has bracket matching,
auto-indenting, highlighting code that issues compiler warnings and errors
as you type, and a raft of other features. I'm pretty sure that Komodo has
all of the same features so even though it might take some time to learn all
of the features, you will gain that time back many times over because you
can code faster by finding errors as you write. I never have to go back and
fix and compiler errors or warnings, because I never have any! It even
understands compiler directives (such as "use warnings" and "no
warnings('uninitialized').
Visual Perl does not have (or I've never used it) any integrated help system
for Perl. I keep my "Programming Perl" reference handy in those cases.
> I've had a short peek at Komodo Edit, but considered the start up time way
> too high. Ages ago I had a peek at Eclipse, but not sure if I am the IDE
> kind of guy (I manage quite ok with a "perldoc" keymark in Firefox, and
> perldoc on the cli most of the time).
>
> --
> John
>
> http://johnbokma.com/mexit/2007/12/20/
------------------------------
Date: Fri, 21 Dec 2007 14:29:58 -0600
From: l v <veatchla@yahoo.com>
Subject: Re: Which editor for Perl hacking are you using
Message-Id: <13mo8i79k7rnj5f@news.supernews.com>
John Bokma wrote:
> Please no editor war, but I am curious, what's the editor of choice you're
> using to write Perl, and why (if you want to share).
>
> I am currently using Textpad, but in the very near future I am moving to
> GNU/Linux. I've some experience with using vi(m) for editing work, and
> have printed both the emacs and vim manual, but not sure which one to
> start reading first.
>
> I've had a short peek at Komodo Edit, but considered the start up time way
> too high. Ages ago I had a peek at Eclipse, but not sure if I am the IDE
> kind of guy (I manage quite ok with a "perldoc" keymark in Firefox, and
> perldoc on the cli most of the time).
>
Perl Builder by Solutionsoft.
--
Len
------------------------------
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 1137
***************************************
