[27255] in Perl-Users-Digest
Perl-Users Digest, Issue: 9024 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Mar 7 06:05:51 2006
Date: Tue, 7 Mar 2006 03:05:05 -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 Tue, 7 Mar 2006 Volume: 10 Number: 9024
Today's topics:
[ANNOUNCE] Emacs modules for Perl programming (Jari Aalto+mail.perl)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Typeglobs, Anonymous Filehandles <cbkihong@hotmail.com>
Re: Typeglobs, Anonymous Filehandles <uri@stemsystems.com>
Re: Typeglobs, Anonymous Filehandles <cbkihong@hotmail.com>
Re: Typeglobs, Anonymous Filehandles <cbkihong@hotmail.com>
We Pay 50%--100% Returns Monthly For 1 yearr on investm <invest@vosar.net>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 07 Mar 2006 05:30:48 GMT
From: <jari.aalto@poboxes.com> (Jari Aalto+mail.perl)
Subject: [ANNOUNCE] Emacs modules for Perl programming
Message-Id: <perl-faq/emacs-lisp-modules_1141709429@rtfm.mit.edu>
Archive-name: perl-faq/emacs-lisp-modules
Posting-Frequency: 2 times a month
Maintainer: Jari Aalto A T cante net
Announcement: "What Emacs lisp modules can help with programming Perl"
Preface
Emacs is your friend if you have to do anything comcerning software
development: It offers plug-in modules, written in Emacs lisp
(elisp) language, that makes all your programmings wishes come
true. Please introduce yourself to Emacs and your programming era
will get a new light.
Where to find Emacs/XEmacs
o Unix:
http://www.gnu.org/software/emacs/emacs.html
http://www.xemacs.org/
o Unix Windows port (for Unix die-hards):
install http://www.cygwin.com/ which includes native Emacs 21.x.
and XEmacs port
o Pure Native Windows port
http://www.gnu.org/software/emacs/windows/ntemacs.html
ftp://ftp.xemacs.org/pub/xemacs/windows/setup.exe
o More Emacs resources at
http://tiny-tools.sourceforge.net/ => Emacs resource page
Emacs Perl Modules
Cperl -- Perl programming mode
http://math.berkeley.edu/~ilya/software/emacs/
by Ilya Zakharevich
CPerl is major mode for editing perl files. Also included in
latest Emacs, but newest version is at Ilya's site. Note that
the directrory at CPAN is out of date:
http://www.cpan.org/modules/by-authors/id/ILYAZ/cperl-mode/
Compared to default `perl-mode' that comes with Emacs, this
one has more features.
TinyPerl -- Perl related utilities
http://tiny-tools.sourceforge.net/
If you ever wonder how to deal with Perl POD pages or how to find
documentation from all perl manpages, this package is for you.
Couple of keystrokes and all the documentaion is in your hands.
o Instant function help: See documentation of `shift', `pop'...
o Show Perl manual pages in *pod* buffer
o Grep through all Perl manpages (.pod)
o Follow POD references e.g. [perlre] to next pod with RETURN
o Coloured pod pages with `font-lock'
o Separate `tiperl-pod-view-mode' for jumping topics and pages
forward and backward in *pod* buffer.
o Update `$VERSION' variable with YYYY.MMDD on save.
o Load source code into Emacs, like Devel::DProf.pm
o Prepare script (version numbering) and Upload it to PAUSE
o Generate autoload STUBS (Devel::SelfStubber) for you
Perl Module (.pm)
TinyIgrep -- Perl Code browsing and easy grepping
[TinyIgrep is included in Tiny Tools Kit]
To grep from all installed Perl modules, define database to
TinyIgrep. There is example file emacs-rc-tinyigrep.el that shows
how to set up dattabases for Perl5, Perl4 whatever you have
installed
TinyIgrep calls Igrep.el to to do the search, You can adjust
recursive grep options, set search case sensitivity, add user grep
options etc.
You can find latest `igrep.el' module at
<http://groups.google.com/groups?group=gnu.emacs.sources> The
maintainer is Jefin Rodgers <kevinr@ihs.com>.
TinyCompile -- To Browse grep results in Emacs *compile* buffer
TinyCompile is a minor mode for *compile* buffer from where
you can collapse unwanted lines or shorten file URLs:
/asd/asd/asd/asd/ads/as/da/sd/as/as/asd/file1:NNN: MATCHED TEXT
/asd/asd/asd/asd/ads/as/da/sd/as/as/asd/file2:NNN: MATCHED TEXT
-->
cd /asd/asd/asd/asd/ads/as/da/sd/as/as/asd/
file1:NNN: MATCHED TEXT
file1:NNN: MATCHED TEXT
End
------------------------------
Date: 07 Mar 2006 08:22:11 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <440d42b2$0$56209$ae4e5890@news.nationwide.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://mail.augustmail.com/~tadmc/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Tue, 07 Mar 2006 12:58:29 +0800
From: Bernard Chan <cbkihong@hotmail.com>
Subject: Typeglobs, Anonymous Filehandles
Message-Id: <440d144c$0$23562$6d36acad@titian.nntpserver.com>
Hello,
I have finally been able to get an output buffering module I mentioned
in an earlier post to work. Though the module is complete and works as
expected, I'm still not sure how some of the code I wrote actually works.
I tried this: ====================
perl -Mstrict -e 'local *FH = "STDOUT"; print FH "Test Message\n"'
It seems like FH now points to the filehandle STDOUT with the
assignment. I forgot if anywhere in the perldoc mentioned this
behaviour, or I just got it "discovered" by accident. And also, isn't
this regarded as a symbolic reference, but Perl under strict 'refs'
doesn't complain?
Another mystery: ================
my $BUF;
open my $FH, ">", \$BUF;
print ref($FH)
outputs "GLOB".
From the perldocs my perception is that typeglobs are symbol table
entries. But now $FH is a lexical, so it is not on the symbol table.
Then where does the GLOB come from? What does it contain?
Now, $FH being a lexical, *$FH{GLOB} exists, but what is contained in
it? And *{$FH{GLOB}}{GLOB}, ... ?
Hope some brilliant minds here may give me some insights.
Regards,
Bernard Chan.
*** Free account sponsored by SecureIX.com ***
*** Encrypt your Internet usage with a free VPN account from http://www.SecureIX.com ***
------------------------------
Date: Tue, 07 Mar 2006 00:25:20 -0500
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: Typeglobs, Anonymous Filehandles
Message-Id: <x77j7625dr.fsf@mail.sysarch.com>
>>>>> "BC" == Bernard Chan <cbkihong@hotmail.com> writes:
BC> Hello,
BC> I have finally been able to get an output buffering module I mentioned
BC> in an earlier post to work. Though the module is complete and works as
BC> expected, I'm still not sure how some of the code I wrote actually
BC> works.
why don't you post the code for review?
BC> I tried this: ====================
BC> perl -Mstrict -e 'local *FH = "STDOUT"; print FH "Test Message\n"'
BC> It seems like FH now points to the filehandle STDOUT with the
BC> assignment. I forgot if anywhere in the perldoc mentioned this
BC> behaviour, or I just got it "discovered" by accident. And also,
BC> isn't this regarded as a symbolic reference, but Perl under strict
BC> 'refs' doesn't complain?
it is a symref in a way but it is not covered by strict. since early
perl days, file handles were strings and that is still supported. in
many places where you are allowed a file handle you can put a bareword
or a scalar string expression (you may need to wrap complex handle name
expressions with {} or assign them to a scalar var). the string is used
to lookup up the handle in the symbol table and that has a glob which is
used as the real handle. in any case the best way to do that is:
local *FH = \*STDOUT ; print FH "Test Message\n"'
that assignment is clean and doesn't use any symrefs. but even so, there
is no need for the local if you just used a scalar var to hold the
handle.
my $fh = \*STDOUT ; print $fh "Test Message\n"'
BC> Another mystery: ================
BC> open my $FH, ">", \$BUF;
BC> print ref($FH)
BC> outputs "GLOB".
BC> From the perldocs my perception is that typeglobs are symbol table
BC> entries. But now $FH is a lexical, so it is not on the symbol
BC> table. Then where does the GLOB come from? What does it contain?
a glob is just a special data structure used internally by perl. the
symbol table is made of globs but they can be used anywhere. a glob is a
simple structure with entries (the docs have the details) for the
various things that perl can store in a symtable entry. these include
scalar, array, hash, code and an i/o handle. there is no other way to
access a perl i/o handle except through a glob. all of the other types
can have refs taken of them but the best a handle can do is a ref to the
glob that has that handle. perl knows that if it sees a glob in i/o
handle spots, it uses the handle slot of that glob for the i/o handle.
BC> Now, $FH being a lexical, *$FH{GLOB} exists, but what is contained
BC> in it? And *{$FH{GLOB}}{GLOB}, ... ?
well, did you take a look and see? as i noted above, single globs
generally aren't going to be made into trees. regular refs can do that
and without all those extra glob layers in between. this is another
reason why i preach to not use symrefs as they just use the symtable as
a tree structure but it is slower, bulkier, global, and
dangerous. effectively symrefs are just syntactic sugar that makes the
symtree look like a ref based hash tree.
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: Tue, 07 Mar 2006 15:34:10 +0800
From: Bernard Chan <cbkihong@hotmail.com>
Subject: Re: Typeglobs, Anonymous Filehandles
Message-Id: <440d390d$0$14378$6d36acad@titian.nntpserver.com>
Thank you very much for your clarification.
Uri Guttman wrote:
> why don't you post the code for review?
Just thought nobody would be interested in it. Posted.
Comments/corrections etc. appreciated.
> BC> Now, $FH being a lexical, *$FH{GLOB} exists, but what is
> contained BC> in it? And *{$FH{GLOB}}{GLOB}, ... ?
>
> well, did you take a look and see?
>
Tried print()ing the globs. All give "*main::$FH". Not totally sure what
that means though, especially in the context of a lexical variable.
I don't use globs or symrefs either normally. I was just curious to find
out more about them, especially in places where the docs appear a bit
confusing.
Regards,
Bernard Chan.
*** Free account sponsored by SecureIX.com ***
*** Encrypt your Internet usage with a free VPN account from http://www.SecureIX.com ***
------------------------------
Date: Tue, 07 Mar 2006 15:25:46 +0800
From: Bernard Chan <cbkihong@hotmail.com>
Subject: Re: Typeglobs, Anonymous Filehandles
Message-Id: <440d390b$0$23562$6d36acad@titian.nntpserver.com>
Here is what I have now:
===================================================================
# PHP has some output buffering functions. Perl should have some too.
# Here is a crude implementation utilizing the Perl open() of
scalar-backed filehandles.
# In fact, this is likely to be more flexible as we can apply
# this to any output stream (including files, probably sockets too, etc.).
package IO::OutputBuffer;
use Encode;
use strict;
# Initialize output buffer
# Defaults to the currently selected filehandle (usually STDOUT).
# $obj = IO::OutputBuffer->new(FILEHANDLE)
sub new {
my ($ref, $io_orig) = @_;
my $pkg = ref($ref) || $ref;
$io_orig ||= select();
{
no strict 'refs';
# If passed in something like 'STDOUT' we will take
# a GLOB reference right away.
# But we don't accept *STDOUT, *STDOUT{IO} or something like that.
$io_orig =
(ref($io_orig) eq 'GLOB' && $io_orig) ||
\*$io_orig;
}
my $buf = '';
my $this = bless {
'IO_REF' => \*$io_orig, # Take another pointer to original GLOB
'IO_BUF' => undef, # GLOB to scalar-backed filehandle
'IO_ORIG' => *$io_orig, # Original GLOB
'BUF' => \$buf, # Buffer
}, $pkg;
return $this;
}
# Start output buffering on given filehandle.
# $buffer->start()
sub start {
my $this = shift;
my $io_new;
open $io_new, ">:utf8", $this->{'BUF'};
$this->{'IO_BUF'} = *$io_new;
# Modify the original glob to point to new filehandle
*{ $this->{'IO_REF'} } = $io_new;
}
# Retrieve the content in the buffer saved during buffering.
# $bufferedContent = $buffer->getContent()
sub getContent {
my $this = shift;
return ${$this->{'BUF'}};
}
# Clean the buffer.
# $bufferedContent = $buffer->clean()
sub clean {
my $this = $_[0];
my $content = &getContent;
local *MEM = getBufferedFilehandle($this);
${ $this->{'BUF'} } = '';
seek MEM, 0, 0 if (*MEM); # Reset filehandle's position after we have
reset the buffer
return $content;
}
# Send the content of the output buffer to the underlying data stream.
# The buffer will be cleaned up.
# $buffer->flush();
sub flush {
my $this = $_[0];
my $content = &clean;
$content = decode_utf8($content);
local *ORIG = getUnbufferedFilehandle($this);
print ORIG $content;
}
# Retrieve a filehandle to the original, unbuffered data stream.
# This is useful if we really have something to write to the underlying
stream without
# terminating output buffering.
# $fh = $buffer->getUnbufferedFilehandle()
sub getUnbufferedFilehandle {
my ($this) = @_;
return $this->{'IO_ORIG'};
}
# Retrieve a filehandle to the in-memory data stream.
# $fh = $buffer->getBufferedFilehandle()
sub getBufferedFilehandle {
my ($this) = @_;
return $this->{'IO_BUF'};
}
# Stop output buffering for filehandle saved in the given ticket.
# Restore the originally saved filehandle.
# $buffer->end();
sub end {
my ($this) = @_;
my ($io, $io_orig) = ($this->getBufferedFilehandle(),
$this->getUnbufferedFilehandle());
# Restore the filehandle in the GLOB
*{$this->{'IO_REF'}} = $io_orig;
}
1;
*** Free account sponsored by SecureIX.com ***
*** Encrypt your Internet usage with a free VPN account from http://www.SecureIX.com ***
------------------------------
Date: Mon, 6 Mar 2006 21:23:11 -0500
From: INCOME---DAILY<invest@vosar.net>
Subject: We Pay 50%--100% Returns Monthly For 1 yearr on investment. You need to know this!
Message-Id: <i86Pf.48746$8d1.32216@read1.cgocable.net>
------------------------------
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 9024
***************************************
