HP3000-L Archives

June 1997, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Wed, 11 Jun 1997 09:00:59 +0530
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
Dennis writes:

> Lee Courtney ([log in to unmask]) wrote:
> : I've been told that there is a C compiler option that will cause source code
> : line numbers to be embedded in the compiled object code - ala the HP Pascal
> : $STATEMENT_NUMBER on$ compiler option. Any help learning what this option
> : is and how it works would be greatly appreciated.
>
> Why do you think you need it?  You can use +o to get a listing of offsets.
> Otherwise debuggers will give you the statement starts without that
> option.

Well...because it's *VERY* useful.  The SPLash! compiler has always had
the option of putting line numbers into the object code ... not the
measly procedure-relative statement numbers that Pascal does :)

With embedded line numbers, you can trivially locate source code while
looking at a Debug nmP window.  No fussing with listings (paper or
virtual).

But...back to Lee's question.  I, too, thought there was a mechanism
to get procedure-relative statement numbers into the C generated
object code...but I can't remember it, or find it.

SS

ATOM RSS1 RSS2