Re: Adding practical (runtime) facts to a program
- From: A.L. <alewando@xxxxxxxxxxxx>
- Date: Tue, 08 Aug 2006 08:08:28 -0500
On 5 Aug 2006 04:51:23 -0700, yaoziyuan@xxxxxxxxx wrote:
Traditionally, the compiler and the debugger are researched and
developed separately. I think the programmer could add information
about a program's practical requirements to the source code of this
program (or the debugger could also automatically collect such
information from test runs), and such information would be useful for
the compiler to further optimize the binary code (e.g. translate a
"for" loop according to its practical runtime loop count) and for
program verifiers to find potential logical problems (e.g. boundary
check).
Such information could also give other programmers an understanding of
the magnitude of input data the program can handle, etc.
What do you think of this?
We thuink that you have never programmed in anything but C
A.L.
.
- References:
- Adding practical (runtime) facts to a program
- From: yaoziyuan
- Adding practical (runtime) facts to a program
- Prev by Date: Re: Adding practical (runtime) facts to a program
- Next by Date: What complexity class is 6 Degrees of Kevin Bacon?
- Previous by thread: Re: Adding practical (runtime) facts to a program
- Next by thread: The reachability problem of Petri net with priority is undecidable!
- Index(es):