GPU to 72 status...

[chris2be8]

Originally Posted by storm5510

Another item, appearing in (Windows) Strawberry scripts, is $|=1; What this does, I haven't a clue. It appears below the use statements.

From man perlvar (on Linux, but should apply to any OS):

HANDLE->autoflush( EXPR )
$OUTPUT_AUTOFLUSH
$| If set to nonzero, forces a flush right away and after every write or print on the currently selected output channel. Default is 0
(regardless of whether the channel is really buffered by the system or not; $| tells you only whether you've asked Perl explicitly to
flush after each write). STDOUT will typically be line buffered if output is to the terminal and block buffered otherwise. Setting this
variable is useful primarily when you are outputting to a pipe or socket, such as when you are running a Perl program under rsh and want
to see the output as it's happening. This has no effect on input buffering. See "getc" in perlfunc for that. See "select" in perlfunc
on how to select the output channel. See also IO::Handle.

Mnemonic: when you want your pipes to be piping hot.

Chris

[storm5510]

Originally Posted by chris2be8

From man perlvar (on Linux, but should apply to any OS):

Chris

In my experience with Strawberry (Windows), it "$|=1;" did not work this way. It would hold on to the output until I stopped the script. Then, it would dump to the file. I did it like this:

open my $pl,'>>','plist.txt';
$pl->autoflush;

It would do file writes at what appeared to be regular intervals. There has to be differences between Linux Perl and Windows Perl. This is probably one of many.

[chalsall]

Originally Posted by storm5510

There has to be differences between Linux Perl and Windows Perl. This is probably one of many.

Please trust me on this: MANY differences. It's a bit like Java. "Write once, debug everywhere."

Forget about using fork(), unless you're short-running and can simply accept memory leakage. Etc, etc, etc...

[storm5510]

Originally Posted by chalsall

Please trust me on this: MANY differences. It's a bit like Java. "Write once, debug everywhere."

Forget about using fork(), unless you're short-running and can simply accept memory leakage. Etc, etc, etc...

As I suspected...

I've looked at the spider quite a bit. Most of the code, I cannot grasp. It goes way beyond my Perl skill level. On the surface, it seems too complex, as in trying to do many things. I wonder if all of that is really necessary.

[chalsall]

Originally Posted by storm5510

I've looked at the spider quite a bit. Most of the code, I cannot grasp. It goes way beyond my Perl skill level. On the surface, it seems too complex, as in trying to do many things. I wonder if all of that is really necessary.

LOL... If I may please share...

IMO, Perl has a bad rap along the lines of "Write once, read never". Mostly because of the tight tying of Regular Expressions.

Perl really is the "Internet's Duct-tape". It does Strings in its sleep, and makes gluing software components together trivial.

The learning-curve is perhaps a bit steep, but it's not vertical. And knowing how to use it is very empowering.

Axiom: Always choose the best tool for the job. The more tools you have, the less work you yourself will do.

[PhilF]

Originally Posted by chalsall

Perl really is the "Internet's Duct-tape". It does Strings in its sleep, and makes gluing software components together trivial.

Sounds like you are describing awk:

Perl Awk really is "Internet Unix's Duct-tape". It does Strings in its sleep, and makes gluing software components together trivial.

[chalsall]

Originally Posted by PhilF

Sounds like you are describing awk:

Hey, James and I argue enough about what the P in LAMP should really mean. (And then along came Python, to crash the party (and enforce indentation)...)

[James Heinrich]

Originally Posted by chalsall

Hey, James and I argue enough about what the P in LAMP should really mean

There's no argument. I was just lurking and keeping myself quietly out of trouble...

[PhilF]

Originally Posted by James Heinrich

There's no argument. I was just lurking and keeping myself quietly out of trouble...

Oh Oh... I'm in trouble. I'm a LEMP guy.

[chalsall]

Originally Posted by PhilF

Oh Oh... I'm in trouble. I'm a LEMP guy.

Socialist!!!

My rule is, I don't care what you use; just get the job done.

[James Heinrich]

Originally Posted by PhilF

Oh Oh... I'm in trouble. I'm a LEMP guy.

Don't worry, I won't yell at you. (my server also runs nginx, but don't tell Chris)