On 02/17/2008 03:48:40 PM, Rob Dixon wrote:
MK wrote:
>
I have a subroutine that begins with a message ("Processing...") and
then
proceeds to perform several gigs worth of file transfer via system
calls.
Basically:
sub transfer {
print "Processing...\n";
foreach $e (@array) {
MK wrote:
I have a subroutine that begins with a message ("Processing...") and
then proceeds to perform several gigs worth of file transfer via system
calls. Basically:
sub transfer {
print "Processing...\n";
foreach $e (@array) {
print "file $e\n";
system "cp $e"; #
MK wrote:
>
I have a subroutine that begins with a message ("Processing...") and
then proceeds to perform several gigs worth of file transfer via system
calls. Basically:
sub transfer {
print "Processing...\n";
foreach $e (@array) {
print "file $e\n";
system "cp $e"; #
I have a subroutine that begins with a message ("Processing...") and
then proceeds to perform several gigs worth of file transfer via system
calls. Basically:
sub transfer {
print "Processing...\n";
foreach $e (@array) {
print "file $e\n";
syst
On 02/17/2008 12:08:40 PM, zentara wrote:
-> Yeah, dynamically generated menus would be the way to go,
-> but I would watch out for memory gains everytime you invoke the menu.
-> Tk isn't very good about object cleanup.
i will remember and look into this.
-> Another problem with dynamic menus,
from zentara:
-> Now you may not see the usefulness of the entryconfigure or the cget,
-> but what if you had a more complex menu, and needed to dynamically
-> grey out items?
That is exactly what i did (the cascading menus are a recursive tree,
with several hundred+ total entries dynamically
Gunnar Hjalmarsson schreef:
> Dr.Ruud:
>> Gunnar Hjalmarsson:
>>> PlagueMagazine:
I have data in a text file where the important thing I want
to extract is between two blank lines.
>>>
>>> Assuming the data has been slurped into $_ :
>>>
>>> print "$1\n" while /\n\n(.+)(?=\n\n)/g;