Yesterday 23:29
Forum: Proton Plus Compiler v3
Starter: Tim
Views: 0
Replies: 3
Yesterday 21:44
Forum: Proton Plus Compiler v3
Starter: IstvanK
Views: 0
Replies: 3
Yesterday 18:17
Forum: LCD module
Starter: towlerg
Views: 0
Replies: 2
Yesterday 18:06
Forum: Proton Users File Server
Starter: Dompie
Views: 0
Replies: 0
Yesterday 16:56
Forum: Proton Plus Compiler v3
Starter: Henk57
Views: 0
Replies: 10
Go to last post By: Lester
Yesterday 14:50
Forum: Website / Forum Issues
Starter: Lester
Views: 0
Replies: 16
+ Reply to Thread
Page 1 of 6 123 ... LastLast
Results 1 to 10 of 54

Thread: A new Stats collector plugin352 days old

  1. #1
    Article Author johngb's Avatar
    Join Date
    Oct 2003
    Posts
    2,138
    Thumbs Up
    Received: 66
    Given: 0
    Total Downloaded
    1.09 GB

    1 Not allowed!

    Default A new Stats collector plugin

    I have published a new plug-in which will gather statistics on your program when you compile. It will detect unused variables, labels etc and can report on the usage of these items in your program.

    You can download it from here

    P
    lease report any issues in this thread.
    JohnB

  2. #2
    Prolific Poster towlerg's Avatar
    Join Date
    Mar 2012
    Posts
    1,360
    Thumbs Up
    Received: 49
    Given: 124
    Total Downloaded
    2.37 GB

    0 Not allowed!

    Default Re: A new Stats collector plugin

    Great idea. Just few oddities.

    a. I installed the manual version (or thought I did) but now every time I compile it pops the box and fills the output area (until I stop and restart PDS). Is it possible to find out which version is installed? or perhaps this is intended behaviour?

    b. D_RxPacketTo in this construct is reported as both an unused procedure and an unused macro - D_Data = HRSIn, {D_RxTimeOut, D_RxPacketTo}.

    c. The Reporter does not show procedures in include files (in my test case I have no procedures in the .bas file but serveal in an included .INC file).

    Other than that, great, just what we needed.

    Edit. had a quck play and I suspect b. above might also apply to Branch.
    Last edited by towlerg; 28th December 2016 at 14:37. Reason: old and stupid
    George

  3. #3
    Article Author johngb's Avatar
    Join Date
    Oct 2003
    Posts
    2,138
    Thumbs Up
    Received: 66
    Given: 0
    Total Downloaded
    1.09 GB

    0 Not allowed!

    Default Re: A new Stats collector plugin

    Once you start the Stats Collector it will run until PDS is closed down. There is no user interface for the Stats Collector.
    Not sure what you mean by filling the output area. You can disable the popup box by going to Settings in the Stats Reporter and un-checking ShowLog. The log was initially just there to help during development.

    Re the other point, can you let me have your source and I will try and see what is going on. There are probably going to be a number of oddities which I will try and catch when they are reported to me.
    JohnB

  4. #4
    Article Author johngb's Avatar
    Join Date
    Oct 2003
    Posts
    2,138
    Thumbs Up
    Received: 66
    Given: 0
    Total Downloaded
    1.09 GB

    0 Not allowed!

    Default Re: A new Stats collector plugin

    The only way you can tell which version is installed is by looking at the Plugin menu.
    If stats collector appears in the menu you have the manual version.
    As the collector has a very low overhead during compile my recommendation is to install it as an auto-start.
    Maybe it would be better that I close the Stats Collector after every compile in manual mode. I will look into that.

    I have sorted Branch issue, I will look into Procedures - that's an area which I has had less testing as I don;t have too many programs using procedures yet.
    JohnB

  5. #5
    Prolific Poster towlerg's Avatar
    Join Date
    Mar 2012
    Posts
    1,360
    Thumbs Up
    Received: 49
    Given: 124
    Total Downloaded
    2.37 GB

    0 Not allowed!

    Default Re: A new Stats collector plugin

    I could send the source but infact

    D_Data = HRSIn, {D_RxTimeOut, D_RxPacketTo}

    kinda sums it up. Let me know if you need any more info.

    BTW when I said procedures, I meant in the PDS sense rather than PDS24 "proper" procedures
    George

  6. #6
    Article Author johngb's Avatar
    Join Date
    Oct 2003
    Posts
    2,138
    Thumbs Up
    Received: 66
    Given: 0
    Total Downloaded
    1.09 GB

    0 Not allowed!

    Default Re: A new Stats collector plugin

    D_Data = HRSIn, {D_RxTimeOut, D_RxPacketTo}
    OK I can reproduce it - I will look into it.

    Re Procedures, you meant Labels labelling subroutines I suppose.
    I haven't been able to repeat that here but I will keep trying.
    JohnB

  7. #7
    Administrator John Drew's Avatar
    Join Date
    Feb 2002
    Posts
    2,894
    Thumbs Up
    Received: 78
    Given: 25
    Total Downloaded
    1.37 GB

    0 Not allowed!

    Default Re: A new Stats collector plugin

    I have many sub routines in include files and Stats is not showing them as isolated but I'll do some more checking. It's definitely finding unused variables in includes. My variable list is always in an include if it's a large program.
    One thing that I might find useful is to be able to print the list of found issues while I explore 'why did I declare that variable/subroutine in the first place?'
    John

  8. #8
    Article Author johngb's Avatar
    Join Date
    Oct 2003
    Posts
    2,138
    Thumbs Up
    Received: 66
    Given: 0
    Total Downloaded
    1.09 GB

    0 Not allowed!

    Default Re: A new Stats collector plugin

    Adding a print function would be simple enough or perhaps, in the interest of tree preservation, saving to a text file?
    John are you saying that as far as you can see I am picking up labels in include files correctly?
    JohnB

  9. #9
    Administrator John Drew's Avatar
    Join Date
    Feb 2002
    Posts
    2,894
    Thumbs Up
    Received: 78
    Given: 25
    Total Downloaded
    1.37 GB

    0 Not allowed!

    Default Re: A new Stats collector plugin

    Just did another check and the subroutines in includes are being correctly handled. I removed references in the main file and Stats correctly found an unused subroutine in the include.

    A save to file would be fine and overwriting the last. It could be made an automatic function of each compile or maybe controlled by a setting. Once we learn where the file is located we can easily view it directly using notepad (on my second screen) or print it if necessary.
    John

  10. #10
    Article Author johngb's Avatar
    Join Date
    Oct 2003
    Posts
    2,138
    Thumbs Up
    Received: 66
    Given: 0
    Total Downloaded
    1.09 GB

    0 Not allowed!

    Default Re: A new Stats collector plugin

    I have found the problems with George's issue. There were 2 bugs in fact, first I hadn't accounted for the possibility of comma following the HRSin command and the presence of {} curly brackets, which I believe are not required but there in the documentation to indicate optional parameters.

    I will publish a new version when I have added a Save function to the Stats Reporter.
    JohnB

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

     

Similar Threads

  1. johngb has just uploaded PDS Stats Plugin!
    By johngb in forum Proton Users File Server
    Replies: 0
    Last Post: 28th December 2016, 00:26
  2. forum stats
    By Lester in forum The Lounge
    Replies: 3
    Last Post: 5th March 2010, 15:41
  3. New Version of Stats Viewer Plug-In
    By johngb in forum Third Party Developments
    Replies: 0
    Last Post: 25th September 2008, 14:34
  4. Proton Stats Viewer Plug-In
    By johngb in forum Third Party Developments
    Replies: 20
    Last Post: 22nd September 2008, 21:05

Members who have read this thread since 7th December 2017, 15:04 : 1

Actions :  (Set Date)  (Clear Date)

You do not have permission to view the list of names.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts