>>>>> "MS" == Michael Scott <[EMAIL PROTECTED]> writes:
> Reading this brought to mind a command-line Perl tool on NT that began > life as a quick hack and then grew and grew to the point where a quick > Perl Tk user interface would have made it into a proper app but > threading issues prevented it. once you get into tk stuff, you have to think event loops over threading. and for most basic apps you can do it either way. some blocking (e.g simple file reading/writing) for an interactive tk app is not a big issue. blocking only becomes a serious issue in server like things where you want as much speed and throughput as possible. in a interactive gui app, having the user wait a fraction of a second to do a blocking operation is not a problem. > I wouldn't be surprised if many significant single threaded scripts > have remained so because they bumped against this ceiling. again, threading is not the only answer there. if you want perl/tk, you need to get into events and their pluses and minuses. uri -- Uri Guttman ------ [EMAIL PROTECTED] -------- http://www.stemsystems.com --Perl Consulting, Stem Development, Systems Architecture, Design and Coding- Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
