parsing code files to identify dependencies?
#3
(03-23-2023, 09:29 PM)SMcNeill Wrote: Set up your functions to be LOAD_ONCE, like so:
...
The above can only load once (while your precompiler variable is undefined), and then it'll never load again (due to the $LET defining the variable).  Like this, you assure that a routine only loads once and you avoid the glitches of trying to load it multiple times into your main program.

Thanks - this will come in handy. 

But what I am talking about is more about programmatically analyzing code to learn what dependencies exist on custom functions, to know what subset of code to copy over, to eliminate unused code - quite the opposite of LOAD_ONCE, which is the approach of including everything and the programming environment won't blow up from duplicates. 

Also, this is for cleaning up more than QB64/PE programs, I have a need for this on a daily basis with VBA and VBScript. 

Anyway, thanks for your reply, I will file the LOAD_ONCE in my recipe box, you never know when something like that might come in handy!
Reply


Messages In This Thread
RE: parsing code files to identify dependencies? - by madscijr - 03-24-2023, 06:21 PM



Users browsing this thread: 1 Guest(s)