[27519] in Perl-Users-Digest
Perl-Users Digest, Issue: 9094 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Mar 27 00:05:44 2006
Date: Sun, 26 Mar 2006 21:05:04 -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 Sun, 26 Mar 2006 Volume: 10 Number: 9094
Today's topics:
Re: A Problem With GD <brian.d.foy@gmail.com>
Re: A Problem With GD <uri@stemsystems.com>
ANNOUNCE: User::Utmp 1.8 <mxp@dynalabs.de>
Re: file renamer... request feedback <matthew.garrish@sympatico.ca>
Re: file renamer... request feedback <john@castleamber.com>
Re: OT: Emacspeak for Win32 <nospam-abuse@ilyaz.org>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 22 Mar 2006 11:28:28 -0600
From: brian d foy <brian.d.foy@gmail.com>
Subject: Re: A Problem With GD
Message-Id: <220320061128283368%brian.d.foy@gmail.com>
In article <x7hd5rt720.fsf@mail.sysarch.com>, Uri Guttman
<uri@stemsystems.com> wrote:
> huh? where did you learn that misinformation? how do you compare the
> online docs to the ones that come with perl and know which is more
> updated? do you check the versions of the docs? do you track changes
> with diff? in fact you should know that the docs that come with EACH
> installation of perl are always the most up to date docs for THAT
> version.
Come on Uri, you know that's not true. We work on the docs even after
each version is released, even if only to fix typoes.
The perlfaq at http://faq.perl.org are the most up to date for the
current version of Perl, for instance.
*** Free account sponsored by SecureIX.com ***
*** Encrypt your Internet usage with a free VPN account from http://www.SecureIX.com ***
------------------------------
Date: Sun, 26 Mar 2006 23:49:07 -0500
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: A Problem With GD
Message-Id: <x7mzfceblo.fsf@mail.sysarch.com>
>>>>> "bdf" == brian d foy <brian.d.foy@gmail.com> writes:
bdf> In article <x7hd5rt720.fsf@mail.sysarch.com>, Uri Guttman
bdf> <uri@stemsystems.com> wrote:
>> huh? where did you learn that misinformation? how do you compare the
>> online docs to the ones that come with perl and know which is more
>> updated? do you check the versions of the docs? do you track changes
>> with diff? in fact you should know that the docs that come with EACH
>> installation of perl are always the most up to date docs for THAT
>> version.
bdf> Come on Uri, you know that's not true. We work on the docs even after
bdf> each version is released, even if only to fix typoes.
bdf> The perlfaq at http://faq.perl.org are the most up to date for the
bdf> current version of Perl, for instance.
typos and minor fixes aren't the issue. if the newer docs cover
features/behavior that aren't in the perl you are running, it can be a
major pain. how often have the newer docs changed something that was
much bigger than a typo and wasn't related to any code changes? one
exception might be new tutorial docs but they are rarely added. the OP's
blind insistance of using newer docs for older perls is not a good idea
IMO.
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: Mon, 27 Mar 2006 01:13:02 GMT
From: Michael Piotrowski <mxp@dynalabs.de>
Subject: ANNOUNCE: User::Utmp 1.8
Message-Id: <IwrKG8.v1A@zorch.sf-bay.org>
Hi,
I've just uploaded version 1.8 of the User::Utmp Perl module to CPAN.
It is immediately available from
<http://www.dynalabs.de/mxp/perl/>
It should soon be available from CPAN at
<http://search.cpan.org/~mpiotr/User-Utmp-1.8/>
This module provides a Perl interface to utmpx- and utmp-style
databases on UNIX systems, the most important being "the utmpx file"
(typically found at /var/run/utmpx, /etc/utmpx or a similar location),
which provides information about users currently logged in. There is
also support for writing records to utmpx and utmp files. For further
details see the POD documentation embedded in the file Utmp.pm, which
will also be installed as User::Utmp(3) manpage, and the example.pl
script.
The last release of User::Utmp was in 2001 (version 1.6), so it was
definitely time for an update. Changes in version 1.8:
- For compatibility with utmp, the utmpx read functions
generate a ut_time field; it can also be specified in the
argument to pututxline()
- Added support for NetBSD (hints file and various #ifdefs)
- Added Perl interfaces for all functions defined in the
Single UNIX Specification Version 3 (namely: endutxent(),
getutxent(), getutxid(), getutxline(), pututxline(), and
setutxent())
- Extended documentation; it now also says that utmpx is
preferred
- Enhanced test.pl
After making the release I noticed that I forgot to include some
contributions made by users; they'll be included in the next version.
--
Michael Piotrowski, M.A. <mxp@dynalabs.de>
Public key at <http://www.dynalabs.de/mxp/pubkey.txt>
------------------------------
Date: Sun, 26 Mar 2006 21:09:19 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: file renamer... request feedback
Message-Id: <fPHVf.553$m35.31958@news20.bellglobal.com>
<robic0> wrote in message news:k3fe22pf7qca8mjqlpbvp0hn730flh167f@4ax.com...
> On Sun, 26 Mar 2006 16:58:33 +0200, "Lukas Mai" <rwxr-xr-x@gmx.de> wrote:
>
>>robic0 schrob:
>>>
>>> Uri, $new =~ s/^_//g; re-anchors after the substitution, minus 1 '_'.
>>
>>No, it doesn't. Uri is right. You are completely wrong and I have no
>>idea why you think /g changes how anchors work.
>>
> So what your saying is that after the first substitution in global context
> s///g, the char position pointer has no notion of beggining of line?
>
> Well, I think it could be written that /^/ is still valid after every
> substitution.
>
> Or are you saying the documentation says /^/ is *ONLY* valid before the
> *FIRST* substitution in global context?
>
Why do keep writing gibberish?
What you fail to understand in this case is that the string position is not
the issue; you'd also have to tell the regex engine to drop the string it
was operating on and instead use the just-modified string. I'd love to see
you write any kind of meaningful regular expression when you have to
consider what the string will look like after every substitution, knowing
that what you just substituted in may get operated on again.
But then, that's why you're not a very good programmer...
Matt
------------------------------
Date: 27 Mar 2006 03:02:45 GMT
From: John Bokma <john@castleamber.com>
Subject: Re: file renamer... request feedback
Message-Id: <Xns9792D6168F7B8castleamber@130.133.1.4>
"Matt Garrish" <matthew.garrish@sympatico.ca> wrote:
> Why do keep writing gibberish?
Because people like you keep replying? (Just a wild guess)
--
John Bokma Freelance software developer
&
Experienced Perl programmer: http://castleamber.com/
------------------------------
Date: Mon, 27 Mar 2006 03:00:00 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: OT: Emacspeak for Win32
Message-Id: <e07kfg$274s$1@agate.berkeley.edu>
[A complimentary Cc of this posting was sent to
Veli-Pekka Tätilä
<vtatila@mail.student.oulu.fi>], who wrote in article <e06v58$va6$1@news.oulu.fi>:
> > What for? Is your sound card multiplexed?
> Hmmm, I think it can do hardware mixing and does have several outputs.
Now that I thought more of it, I have some vague recollection that if
sound card has no mixing, windows will mix in software... So this
question may be meaningless on sufficiently powerfull computer with
Windows.
> However, the name Microsoft speech API is a bit misleading. It let's one
> deal with both speech recognition and text to speech via a uniform
> interface. Naturally, using text to speech is what interests me. More
> specifically using the same speech synth as in my screen reader but driven
> by Emacspeak.
Well, if you can write a small wrapper application (possibly in Perl
XS ;-) which interfaces with your beloved API, and takes the text from
STDIN, everything should be OK (although I have no idea how Emacsspeak
works, I doubt it needs anything else).
Yours,
Ilya
------------------------------
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 V10 Issue 9094
***************************************
