Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| [4 earlier articles] |
| Re: Semantic difference of source files gah@ugcs.caltech.edu (glen herrmannsfeldt) (2008-08-18) |
| Re: Semantic difference of source files gah@ugcs.caltech.edu (glen herrmannsfeldt) (2008-08-19) |
| Re: Semantic difference of source files marcov@stack.nl (Marco van de Voort) (2008-08-20) |
| Re: Semantic difference of source files gah@ugcs.caltech.edu (glen herrmannsfeldt) (2008-08-20) |
| Re: Semantic difference of source files DrDiettrich1@aol.com (Hans-Peter Diettrich) (2008-08-23) |
| Re: Semantic difference of source files marcov@stack.nl (Marco van de Voort) (2008-08-24) |
| Re: Semantic difference of source files Jatin_Bhateja@mentor.com (Jatin Bhateja) (2008-08-28) |
| Re: Semantic difference of source files m.helvensteijn@gmail.com (2008-08-28) |
| From: | Jatin Bhateja <Jatin_Bhateja@mentor.com> |
| Newsgroups: | comp.compilers |
| Date: | Thu, 28 Aug 2008 13:05:28 +0530 |
| Organization: | Compilers Central |
| References: | 08-08-025 |
| Keywords: | parse, debug |
| Posted-Date: | 28 Aug 2008 10:12:09 EDT |
Hi Michiel,
>I propose that in addition to comparing modification dates, we selectively
>compare AST's (if the source file is newer). At the very least this allows
>the programmer to modify style, layout and comments without requiring any
>recompilation at all. If the comparison utility is smart enough, you may
>even perform trivial refactoring without losing semantic equivalence.
As per your thought programmer can make cosmetic changes like changing
the comments / spaces / tabs / new lines,
any such cosmetic change will not lead to re-compilation. How are you
going to keep the line number info updated ?
It needed by source debugger to refer to correct source line analogous
to current assembly/machine instruction .
--
Thanks and Regards
Jatin Bhateja
Return to the
comp.compilers page.
Search the
comp.compilers archives again.