Related articles |
---|
Adding Blank Line In Source Causes Change In Executable john.m.morris@navy.mil (Morris, John M CIV NSWCDD, Q34) (2012-03-06) |
Re: Adding Blank Line In Source Causes Change In Executable gah@ugcs.caltech.edu (glen herrmannsfeldt) (2012-03-06) |
Re: Adding Blank Line In Source Causes Change In Executable bobduff@shell01.TheWorld.com (Robert A Duff) (2012-03-06) |
Re: Adding Blank Line In Source Causes Change In Executable hokienerd@gmail.com (HOKIENERD) (2012-03-12) |
Re: Adding Blank Line In Source Causes Change In Executable bobduff@shell01.TheWorld.com (Robert A Duff) (2012-03-13) |
Re: Adding Blank Line In Source Causes Change In Executable gah@ugcs.caltech.edu (glen herrmannsfeldt) (2012-03-14) |
Re: Adding Blank Line In Source Causes Change In Executable hokienerd@gmail.com (HOKIENERD) (2012-03-26) |
Re: Adding Blank Line In Source Causes Change In Executable bobduff@shell01.TheWorld.com (Robert A Duff) (2012-03-26) |
From: | Robert A Duff <bobduff@shell01.TheWorld.com> |
Newsgroups: | comp.compilers |
Date: | Tue, 13 Mar 2012 09:34:30 -0400 |
Organization: | The World Public Access UNIX, Brookline, MA |
References: | 12-03-007 12-03-010 12-03-028 |
Keywords: | debug, code |
Posted-Date: | 14 Mar 2012 00:28:57 EDT |
HOKIENERD <hokienerd@gmail.com> writes:
> It absolutely is the line number. (Thanks for the tip.)
You're welcome.
>... I hope to get
> to the assembly code before too long. I sure wish I could keep the
> check, but lose the line number!
Why?
I understand why one wants identical source code to produce
identical object files, and identical executable files.
(I don't like object file formats that include things
like time-of-compilation!)
But if you add blank lines, the source is no longer identical.
Surely that line number is useful, if the check ever fails.
There's an option to gnatmake that causes it to not recompile
things if the changes were trivial (e.g. whitespace and comment
changes), but then the debugging information will be slightly off.
- Bob
Return to the
comp.compilers page.
Search the
comp.compilers archives again.