On Wed, 19 Nov 2003, Ben Aitchison wrote: > Because it makes performance issues rather obvious to the eye. > > If something doesn't go smoothly on 16 mhz, then it's inefficient. [...]
Why not use a profiler? You don't need extra hardware, and you get much more detailed information about where your program is loitering around all the time. Admittedly, there may not be profiling support for your language... Or, even simpler, but a bit coarse, use "time". > On Tue, Nov 18, 2003 at 06:58:58PM +1300, Paul William wrote: > > On Tue, 2003-11-18 at 18:31, Ben Aitchison wrote: > > > it won't underclock to 16 mhz, will it? i want a 16 mhz 386 :) > > > > Why would you want a 16 mhz? [..] Kind regards, Helmut Walle. +----------------+ | Helmut Walle | | [EMAIL PROTECTED] | | 03 - 388 39 54 | +----------------+
