Not. Using the ELSE form results in less object (executable) code. Dan
On Wed, Mar 3, 2010 at 1:42 AM, Mike Preece <[email protected]> wrote: > > > On Mar 3, 1:22 am, Daniel Klein <[email protected]> wrote: > > It would be better to use ELSE, i.e., > > > > IF MOD(COUNTER,1000) ELSE CRT COUNTER > > > > otherwise you will be displaying every number except every thousandth ;-) > > > > Dan > > It would be better to use THEN, i.e., > > IF MOD(COUNTER,1000) = 0 THEN CRT COUNTER > > Mike. > > > > > > On Tue, Mar 2, 2010 at 7:37 PM, Tony Gravagno <[email protected]> > wrote: > > > I noticed the situation you describe sometime in the early 90's > > > .... or was it in the 80's? Serial lines and the Telnet protocol > > > both throttle a server, forcing it to complete the write before > > > it moves to the next instruction. Individual instructions may > > > take a few milliseconds to process, but it may take full a second > > > to transport text down a wire and render it to a UI, thus > > > crippling the performance of an app. > > > > > One solution (as you said) is to do something like this: > > > IF MOD(COUNTER,1000) THEN CRT COUNTER > > > > > Another solution (depending on the technology involved, is simply > > > to minimize the window on a telnet client which is receiving > > > streamed output. You still incur transmission time but you don't > > > incur time in the UI to render text, which can also be > > > substantial. > > > > > HTH > > > > > Tony Gravagno > > > Nebula Research and Development > > > TG@ remove.pleaseNebula-RnD.com > > > Nebula R&D sells mv.NET and other Pick/MultiValue products > > > worldwide, and provides related development services > > > remove.pleaseNebula-RnD.com/blog > > > Visit PickWiki.com! Contribute! > > >http://Twitter.com/TonyGravagno > > > > > From: Will J > > >> I have a funny story about a whole-file-process which, > > >> as it ran, output a status message on how many records > > >> it had processed, etc. Of course the file ran pretty > > >> quickly on new hardware, but the program still output > > >> a status line for *each* record processed. Record 1, > > >> 2, 3, 4, 5, etc up to 500,000 or whatever it was. The > > >> messages went by now, so quickly you couldn't really > > >> read them, so it was pointless. > > > > >> The whole process took about 2 hours. I changed that > > >> status to only output every 1000th record. The > > >> process from that point on, now took 10 minutes. The > > >> vast consumption of time, was just in printing status > > >> messages. Funny isn't it? > > > > >> Some things just don't scale well, when the hardware > > >> speeds up. > > > > > -- > > > Please read the posting guidelines at: > http://groups.google.com/group/jBASE/web/Posting%20Guidelines > > > > > IMPORTANT: Type T24: at the start of the subject line for questions > specific to Globus/T24 > > > > > To post, send email to [email protected] > > > To unsubscribe, send email to [email protected] > > > For more options, visit this group athttp:// > groups.google.com/group/jBASE?hl=en > > -- > Please read the posting guidelines at: > http://groups.google.com/group/jBASE/web/Posting%20Guidelines > > IMPORTANT: Type T24: at the start of the subject line for questions > specific to Globus/T24 > > To post, send email to [email protected] > To unsubscribe, send email to [email protected] > For more options, visit this group at > http://groups.google.com/group/jBASE?hl=en > -- Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
