On Mon, 2006-01-05 at 17:02 -0700, Anthony Ettinger wrote: > On 5/1/06, Mr. Shawn H. Corey <[EMAIL PROTECTED]> wrote: > > So, now tell us what you want to achieve. Show us the code that "is > > slow" and maybe we can tell you how to speed things up. And if you can't > > separate the code from the IO, then what do you expect from us? > > I'm not trying to benchmark, just gather some real-world data in my tools. > > Basically, I set $start_time = time();, subtract out time waiting during > user input, and take the difference of $end_time = time(); > > Whether this is a good way of gather the data is beyond the question...I'm > curious if there's a way to trigger a pause/unpause routine automatically > from my library when <STDIN> is used.
No. Sigh. I wasn't talking about good practises (well, maybe, just a little). I will try to clarify. What do you want to do? Timing code means you have a specific purpose: to speed things up. What part of your Perl code "is slow" and could you please show us. Separate the code from the IO. Don't stop recording when IO happens. Record only the other parts, the parts without IO. Yes, that means a lot more work on your part. But in case you haven't gotten it yet: This list is NOT here to solve your problems! (At best, it may HELP you solve your problems; at worst, you're fucked.) -- __END__ Just my 0.00000002 million dollars worth, --- Shawn "For the things we have to learn before we can do them, we learn by doing them." Aristotle * Perl tutorials at http://perlmonks.org/?node=Tutorials * A searchable perldoc is at http://perldoc.perl.org/ -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
