[26082] in Perl-Users-Digest
Perl-Users Digest, Issue: 8283 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Jul 27 18:05:32 2005
Date: Wed, 27 Jul 2005 15:05:04 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Wed, 27 Jul 2005 Volume: 10 Number: 8283
Today's topics:
Re: Active State Perl jane@rifill.com
Re: copy contructor (Anno Siegel)
Re: Numeric or character ? <sven-thorsten.fahrbach@gmx.net>
Re: Numeric or character ? (Anno Siegel)
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 27 Jul 2005 19:05:19 GMT
From: jane@rifill.com
Subject: Re: Active State Perl
Message-Id: <79mfe15ne2mmj16r3th71ai8esi7t2beoo@4ax.com>
On 27 Jul 2005 14:32:27 GMT, Michael Zawrotny <zawrotny@sb.fsu.edu> wrote:
>jane@rifill.com <jane@rifill.com> wrote:
>>
>> Michael Zawrotny <zawrotny@sb.fsu.edu> wrote:
>> >
>> >It worked, but for some strange reason, I had to run through the
>> >installer twice to be able to use the module.
>>
>> So do not know what I have done wrong with the install.
>>
>> Stuck now
>
>If you haven't done so already, try running the installer a second
>time. The second time worked for me on both my laptop and the desktop
>that I was installing Imagemagick on.
No I have not done that.
Did you just install over the top of the first install?
>
>Or, try the other poster's suggestion of using ppm directly.
Did you see my post to him about ppm?
It will do nothing when I put that in from the command prompt.
It just comes back to the c:\ prompt
BUT if I put in ppm3.bat it brings up the ppm prompt
Very strange
Jane
>
>
>Mike
------------------------------
Date: 27 Jul 2005 22:00:06 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: copy contructor
Message-Id: <dc9056$gc2$1@mamenchi.zrz.TU-Berlin.DE>
Abigail <abigail@abigail.nl> wrote in comp.lang.perl.misc:
> Anno Siegel (anno4000@lublin.zrz.tu-berlin.de) wrote on MMMMCCCXLVII
> September MCMXCIII in <URL:news:dc5vo5$iuc$1@mamenchi.zrz.TU-Berlin.DE>:
> ^^
> ^^ So "Perl" inherits whichever ->new happens to be first on @ISA, it doesn't
> ^^ matter because they're all equivalent. And if another class (not
> ^^ necessarily inside-out) also had separate construction and initialization,
> ^^ it should be easy to thread it into the scheme. Correct me if I'm wrong,
> ^^ but it looks like an inside-out class could inherit from such a base class
> ^^ of *any* type without any further measures.
>
>
> Indeed. By design. ;-)
Only once, sadly. So you can inherit from as many inside-out classes as
is good for you, plus one "normal" (type-committed) class.
One could wax philosophical about inside-out objects, how a normal inside-
in object holds everything of interest inside and nothing on the outside,
and thus, turning it inside-out, the core of an inside-out object becomes
an object-shaped void which is the former empty outside of the original,
and how this void can be filled with a normally functioning object
while the inside-out object continues to function because its function
is located on the outside, but
I won't.
Instead, let me add a thought that is only loosely related. It seems
to me that inheritance and encapsulation don't go together (anywhere,
not only in Perl) in one respect. When it comes to overriding some
of the original methods, you must know how the methods in the base class
use (call) each other in order to predict the result. On the other hand,
that's an implementation detail that shouldn't concern the inheriting
class. I don't see how that can be resolved.
Anno
--
If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers.
------------------------------
Date: Wed, 27 Jul 2005 22:48:19 +0200
From: Sven-Thorsten Fahrbach <sven-thorsten.fahrbach@gmx.net>
Subject: Re: Numeric or character ?
Message-Id: <20050727224819.31b32581.sven-thorsten.fahrbach@gmx.net>
On 27 Jul 2005 11:56:27 GMT
anno4000@lublin.zrz.tu-berlin.de (Anno Siegel) wrote:
> It's not just preference. An autoflushed IO channel is still buffered,
> the buffer just doesn't fill up so much. A truly unbuffered channel
> would be very hard to use.
>
> Otherwise, the purpose of "$| = 1" isn't that we want STDOUT autoflushed,
> it's that there already *is* autoflushed output that merges with it,
> and the merging is smoother when both are autoflushed.
>
> The problem is often not visible when printing directly to the terminal,
> because terminal output is usually line buffered (another form of automatic
> flushing). When the output goes to a file or pipe, to "| more" for
> instance, the difference becomes apparent. Watch this:
>
> [anno4000@lublin ~/clpm]$ cat script
> #!/usr/bin/perl
> use strict; use warnings;
>
> $| = shift || 0;
>
> print "one\n";
> warn "two\n";
> print "three\n";
>
> [anno4000@lublin ~/clpm]$ ./script |& more
> two
> one
> three
>
> 4000@lublin ~/clpm]$ ./script 1 |& more
> one
> two
> three
>
> Only in the second (autoflushed) example does the output appear in
> the sequence it is produced. That is the problem "$| = 1" avoids.
All right, that was enlightening, though I would not consider it a 'problem' exactly. If I come across a situation where non-autoflushed output might not be desireable, I print to STDERR or set $| = 1. I don't come from a profound C background, though, so I might be a little ignorant ;-).
Excerpt from the Camel Book: 'Contrary to popular belief, setting this [$|] variable does not turn off buffering.'
Okey, my bad.
SveTho
------------------------------
Date: 27 Jul 2005 21:35:52 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Numeric or character ?
Message-Id: <dc8uno$fho$1@mamenchi.zrz.TU-Berlin.DE>
Sven-Thorsten Fahrbach <sven-thorsten.fahrbach@gmx.net> wrote in comp.lang.perl.misc:
> On 27 Jul 2005 11:56:27 GMT
> anno4000@lublin.zrz.tu-berlin.de (Anno Siegel) wrote:
[Why do some set $| = 1 routinely? Demo how STDOUT and STDERR get out
of sequence if you don't]
> All right, that was enlightening, though I would not consider it a
> 'problem' exactly. If I come across a situation where non-autoflushed
> output might not be desireable, I print to STDERR or set $| = 1.
Sure, like everyone. The question was, why do it routinely. When working
on a program you don't want to see, say, the error message it died with
in front of material it has produced before it died.
There are other reasons to use it. If you want to watch a program's
file output through "tail -f ...", it will look jerky unless autoflushed.
Also, if you do an improvised user dialog through STDOUT and STDIN,
users may not see your prompt on some systems unless you autoflush
STDOUT. So it also makes a program more portable. Under normal
circumstances it doesn't hurt much. The exception is mass output
which becomes inefficient. It's the only reason I can think of to
turn it off.
Anno
--
If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers.
------------------------------
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 8283
***************************************
