Announcement

Collapse
No announcement yet.

PB XRef Listing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • PB XRef Listing

    I don't know if this is the right thread for this question.

    I am looking for a program that capable of parsing all of my source code then print out a list of all functions/subs. showing if the function/sub is being called, in addition, which function/subs is calling the function/subs. .... am I making sense? During the days of MS Basic 7 there was a utility called Xref that did it.

  • #2
    See these PB source code analysers:

    Checkit "Source Code Checker" - Scott Slater
    http://www.powerbasic.com/support/pb...d.php?p=167521

    PBcodec "PBcodec, Source Code Checker" - Borje Hagsten
    http://www.reonis.com/POFFS/index.htm

    They will do most of what you are after but not list function to function calls. Source code is available though so you might be able to extend them??
    Rgds, Dave

    Comment


    • #3
      I use PBCodec and that includes a section listing references to procedures... which is the NUMBER of times each function is called. Not a 'tree' but it does find 'dead' procedures.
      Michael Mattias
      Tal Systems (retired)
      Port Washington WI USA
      [email protected]
      http://www.talsystems.com

      Comment


      • #4
        Guys don't forget "TRACE" as you guys have shown me.

        Although I have tried to improve upon, but hard to beat the best at the job that is their job.

        Using TRACE in most cases can at least narrow down, if not find your problem in my mind
        Engineer's Motto: If it aint broke take it apart and fix it

        "If at 1st you don't succeed... call it version 1.0"

        "Half of Programming is coding"....."The other 90% is DEBUGGING"

        "Document my code????" .... "WHYYY??? do you think they call it CODE? "

        Comment


        • #5
          A "procedure tree" sounds like a nice third-party product.

          I have to supply source code as part of a lot of my contracts. Would be a nice piece of "technical documentation" to include for the client.

          MCM
          Michael Mattias
          Tal Systems (retired)
          Port Washington WI USA
          [email protected]talsystems.com
          http://www.talsystems.com

          Comment


          • #6
            Originally posted by Michael Mattias View Post
            A "procedure tree" sounds like a nice third-party product.

            I have to supply source code as part of a lot of my contracts. Would be a nice piece of "technical documentation" to include for the client.

            MCM
            Isn't that what the Lynx Project Explorer does?

            http://www.zippety.net/


            James

            Comment

            Working...
            X