It would be really nice if we could import information outputted from coverage and profiler tools.

It will require that we keep track of number of times each piece of text has been executed/touched. A keybinding which
jumps to the next-untouched-piece of code could be very useful. Perhaps also an overview page of how many sections of
untouched code there is, which places in the code that peeks in number of times they have been executed.

In case we are dealing with Assembler code (x86, motorola, mips), then we may also get information about the quality
of the Assembler code. For instance code for pentiumI must be paired correct, otherwise there is penalties. Indication
of clock cycle and where penalties occurs, what kind of penalty that has occured, where the operation is executed (U
or V).  Lots of information.

--
Simon Strandgaard

Date: 2004-02-22 17:20
Sender: Simon Strandgaard

Logged In: YES 
user_id=154

Work together with tool that can identify poor
programming practices, like using raw numbers instead of
constants
which have been defined in system files, passing large structures
by
value instead of by reference, or creating instantiations in
the middle
of statements (instead of assigning to a variable), possible
buffer
overflow situations, possible memory leaks, and so on.

Unsure how these kind of information should be presented to the
user?