Re: ping Purl Gurl? Beginner Level Perl

blmblm wrote:

Purl Gurl wrote:
blmblm wrote:
Purl Gurl wrote:
blmblm wrote:

select STDOUT;$|=1;

And it does that on my system too -- but only when I add
that line

select STDOUT;$|=1;

Without that line (or with it, but with the 1 replaced by a 0), output appears only when a newline is printed. So I get the
two blank lines at the start, and then all of that nifty
typing-and-backspacing stuff is wasted, because nothing
actually appears on the screen until the newline is printed.

Just making sure we're on the same page, though it's probably
not a big deal.

Ok, perl core buffering. This can be a big deal.

Core has built in buffers for both reading and writing.
You have experienced one of the system specific problems
with perl core buffering.

This is a good short one page article on perl core buffering,

http://perl.plover.com/FAQs/Buffering.html

Upon reading this, you will understand immediately what processes are
taking place and why "sometimes" buffering is a problem. You really should
read the page; short, quick and easy to understand. This will only take
you about five minutes and you will enjoy a wealth of knowledge.


Yeah. Well, the Perl man pages seem to me to be in line with
other Unix/Linux man pages -- good as an online reference, not
so good as a tutorial, not the best source of information for
a beginner, but usable if nothing else is readily available.

I do agree with you about the value of a good book, and I
have a copy of one of the O'Reilly books somewhere -- I think
it's _Programming Perl_ -- but have been too lazy to get it
out and start reading. Maybe soon. Sometimes it's more fun
to start by just dinking around a little.

This is the problem with Perl man pages and Perl in general.

Perl lacks professional leadership. Perl, today, is truly a
hodge-podge effort of hundreds of people, with most of those
people being very egotistical and not such great thinkers.
Larry Wall has maintained some control over perl core but very
little control over documentation. A result is the man pages,
FAQ documents and other writings, are scatterbrained. Documents
were once so bad, a lot of documentation amounted to nothing
more than tirades about how bad Windows is as an operating system.

A recent effort is made to clean up man pages and documentation,
I think or would like to think partially a result of my constant
harping about the idiocy of the old documents. Today's versions
are much better but are still biased in many ways, not so much
about Windows rather constant pressure to use modules rather
than write code. Much of the documentation, rather then explaining
how something "works" refers readers to simply using a module.

Should you ever become seriously involved in the Perl community,
you will discover very few of the gods of Perl know how to write
code but sure do know how to "copy and paste" syntax for modules.
You will discover there are very few true programmers and almost
all are simply plug-n-play babies.

A spin-off is those writing documentation do not well know how
perl core operates and to cover, will simply suggest a module.
You discover a solution but do not discover an explanation.


Calm down. I didn't say "on that useless piece-of-junk
operating system you're probably running", did I? I might
have thought it, but I didn't say it, so no need to get
defensive about your choice of operating system. Using
something that runs the applications you need makes sense.
I have a couple of dual-boot machines, and much as I prefer
Linux, sometimes booting one of them into Windows is the quickest way to accomplish a given task.


Yeah, my choice of operating system is that simple. Windows
offers the programs I need, *nix type machines do not.

Much of this is simply marketing. Windows is the most popular
system and commands the market. About 90 percent of operating
systems out there, Windows. Logical then, 90 percent of software
is written for Windows.

There really is not much of a choice. Use Windows or do not use
the most available software. For me, the most critical software,
as mentioned, is my live stock market feed. This is a must. You
can only enjoy this on a Windows machine. No choice on this.

I would rather make money like Bill Gates than be a cool Penguin.


early Eighties era. Heck, I was a customer of AOL before this
became known as America Online. I can no longer remember what
AOL was called back then, access was dialup through a local
Radio Shack phone number, 1200 baud. I was a teenager then and we
had our baby girl. I needed something, direly needed something
to take my mind off raising a girl more ornery than me.

Our Deskmate computer, used, enjoyed 768 kilobytes of memory,
expanded, and an operating speed of 4 megaHertz; zoom zoom!

The good old days, PC version!


Ha! Ha! I once thought an Etch-A-Sketch to be the most amazing
bit of technology ever. Early computers were not much better.

I finally remembered the name of the online service which came
before America Online, "PC Connect" which was developed by
Tandy Corporation, better known as Radio Shack. I think AOL
Steve Case developed an independent system, then bought out
the Tandy system, made some changes and created a new name
which we know as America Online. Our internet and web have
severely suffered ever since. People complain about Google
Groups, AOL is a million times worse for USENET and the web.


I'm not sure about chronology here, but it could well be that
your early exposure to computers and mine was happening at about the same time, but in very different worlds: I started
out on mainframes -- a couple of undergraduate courses in the
1970s, six years with IBM-and-compatible mainframes, five
years with various minicomputers, then mostly Unix in grad
school. Probably a fairly typical career path for someone
my age, except for graduate school fairly late in life.


You are a little older than I am.

HA! HA! HA! * rolling on the floor laughing * MUHAHAHAHA!
snicker giggle cranky old gray haired woman! MEOOOOOOW!

Thank God for Lady Clairol, Retin-A and Wonderlift bras.

Ahem, well, yes, our experiences are much the same. We both
became involved with computers during the,

"Golden Age of Dinosaur Computers"

You and I are also dinosaurs on the verge of becoming fossils,
old bones for paleontologists to dig up in few decades. We are
the extinct Monitorsaurus.rex of modern day computer technology.

I have a fantasy story. Civilization is wiped out. We kill ourselves
through various man-made mechanisms. Ten-thousand years from now,
explorers from space arrive. Scientists, their anthropologists,
archaeologists, paleontologists and such, dig up our fossil remains.
Soon these visitors discover an inordinate number of female fossils
have bags of saline water resting upon their fossilized rib cages. This
is studied and, finally understanding; these human women were members
of a religion which spread around the world, a religion marked by
female members having artificially large breasts. These visitors from
space give our worldwide religion a name, "The Breasties" which is a
cult like religion which worships large breasted women.

There marks "The Road Not Taken" in our career choices. You picked
a technological field which has earned you a good living and is
very sensible. I picked a road to Creative Writing which rendered
me a crazy starving artist, which is senseless. So I became a teacher.

I took the one less traveled by
and that has made all the difference.

However, I was already crazy the moment I was born, hence my Choctaw
namesake, "Crazy One." My elders tell me my first utter sounds, laughter.

At least we have a common interest we can discuss without scratching
each others eyes out. We are much the same in our lives. If there is
a difference, this is you are sane and I am insane. Other than this,
there is not much difference between us.


--
Purl Gurl
--
So many are stumped by what slips right off the top of my mind
like a man's bad fitting hairpiece.
.

Relevant Pages

  • Re: HTML code !!!
    ... the operating system is Windows 98. ... >> Could you please let me know a place where this is documented or the Bug ... > I don't know about any documentation of this bug. ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: Help: RMAN can not see virtual drive
    ... Mladen Gogala wrote: ... > If you were using an operating system instead of Windows, ... > look up the OS documentation of the return codes. ... Fortunately Windows provides an easy way to look up OS errors: ...
    (comp.databases.oracle.server)
  • basic newbie help
    ... Hey all I'm looking for a new operating system to use as a primary OS ... instead of Windows XP. ... I noticed that there is extensive documentation ... Starting off by installing a HDD installation of Knoppix ...
    (Debian-User)
  • Re: Executable enty points incorrectly documented
    ... I was speaking about Windows SDK not MSDN Library entirely, but even if Windows SDK conatins C/C++ documentation I believe that main/WinMain belong to C/C++ documentation rather than Windows API documentation. ... It's correct about the default entry point names used by the linker and also correct about what those entry points call and because this is the ...
    (microsoft.public.win32.programmer.kernel)
  • Re: installing freebsd on windows
    ... windows vista runs well too on overmuscled hardware. ... Why do I have to Google the info? ... So you're trying to say that all local documentation is useless ... recommending that I do business with them again? ...
    (freebsd-questions)