[Info-vax] C99 stuff (Re: The Road to V9.0)

[Simon Clubley]

On 2019-06-10, Bob Gezelter <gezelter at rlgsc.com> wrote:
>
> Simon,
>
> There is a difference between "needed" and "constantly used".
>
> There are some elements which can only be determined from a compiler
> listing. Actual, debugger-usable line numbers are one. The debugger screen
> will show the local module line numbers, but there is only so much screen
> real estate available. Often, I have multiple listings open at the same
> time on a nearby table.
>

Well that shows very nicely how people go about the same task in different
ways. :-)

Your approach obviously works well for you, including actually printing
out the listings. I use methods that don't require me to do that, and
they work ok for me.

> The same can be said about assembler listings of compiled code.
> Sometimes, I have had to look at compiled code to see why something is
> behaving in an unexpected fashion. Daily? No. But the capability is needed,
> preferably with a degree of symbolization.
>

This part is closer to what I sometimes do with objdump with embedded
systems images. However, I always look at them on screen and have never
needed to print them out.

Thanks to you and everyone else for your comments on compiler listings.
It's clear some of you still make use of them.

Thanks,

Simon.

-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world