× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I completely disagree with using production CPU cycles to fix 
programmer spelling mistakes. Not in the 80s, and not in the 
21st century. If WDSc can do it with verify, and compile is 
still being used to perform that function, I think it is just 
programmer laziness.


Oh boy! Is it jump on Trevor Day?!?!?!?!?

I would agree with Trevor about being concerned with CPU cycles, but the 
environments I saw until the mid '90's, when systems were running with CPU 
usage above 70% for the business day have changed. Since that time, 
average CPU usage I've seen has fallen to ~ 20%  measured for the course 
of the day. Of course, there are spikes above this, but there are a lot 
more spare CPU cycles than there used to be. In addition, using WDSC, 
Verify takes about 30 seconds to run, but Compile completes in about 5 
seconds. This time difference means that I almost always compile programs 
to syntax check them, and I rarely use Verify.


Steven Morrison
Fidelity Express 
903-885-1283  ext. 479

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.