print $array[0]->{name}, "\n";
[download]

That ought to do it.

The issue really has nothing to do with arrays of hashes, and everything to do with output buffering.

Without the "\n" you're not guaranteed of having the output buffer get flushed to the screen, even when the program ends, though most OS's will flush it upon termination.

What is happening is 'Chuck' gets put into the output buffer, the program sleeps for 30 seconds, the program reaches its termination, the output buffer gets flushed to the screen, and poof, your Microsoft DOS emulation window disappears on you before you can blink. Adding the "\n" newline tells Perl to flush the terminal's buffer.

Note, "\n" causes terminal-tied buffers to flush, but doesn't necessarily flush other types of file handles (such as ones tied to files on your hard drive or a network socket). If you want to force all your "pipes to be piping hot" (force them to flush with each print), set a non-zero value in the output-autoflush system special variable, $|. Be aware that this will have a performance impact on every file-related thing you do in your program. Buffers exist for a reason. Try to avoid setting the autoflush variable unless you really need it. In your specific case, all you needed was a newline.

Dave

"If I had my life to do over again, I'd be a plumber." -- Albert Einstein

It is, but because it doesn't have a newline after it, and you are then sleeping, you aren't seeing it until the 30 seconds expires. Try either adding a newline at the end of the print, or removing the sleep.

I was skimming past this, thinking: it's the sleep that's delaying things. Then I read:

Try either adding a newline at the end of the print

which I don't understand. I tested it, and of course it works, but... why does adding a newline cause the print statement to be released before the sleep? Then, it made me think: why on earth is the *subsequent* sleep delaying an earlier print? Can anyone explain this to ignorant monk?

The result is getting buffered, in case you print more output which should be appended to the end of the line you already have, adding the newline tells the system that you are definately not going to be adding new information to the end of that line, so it doesn't have to buffer it anymore. I'm assuming you are running this in some manner that causes a window to pop up and display the output and then disappears when the program is finished, which would explain the sleep. If you run it from the command line you would see that the buffer also gets flushed when the program exits, so you would get your output eventually, just not until the sleep was finished.

---

We're not surrounded, we're in a target-rich environment!

The issue is that Perl, like most other programming languages buffers screen output by default then outputs it all at once under certain circumstances. Those circumstances in Perl are either printing out a newline character, or manually flushing out the buffer. There may be others, I'm but a novice. Anybody know other ways?

Hope that helps!
Ben

#!/usr/bin/perl

use Dumpvalue;

sub dump_ref
{
   my $ref = shift;
   my $dumper = new Dumpvalue;
   print "Content-Type:text/html\n\n";
   print "<pre>";
   $dumper->dumpValues($ref);
   print "</pre>";
   exit;
}
[download]

dump_ref(\%orders);
[download]