Hello,
Is there any possibility to generate automatically a list of all just variables, local, public as well as private variables?
Thanks.
Regards,
Michel D.
Genk (Belgium)
I use : FiveWin for (x)Harbour v. 25.12 - Harbour 3.2.0 (May 2025) - xHarbour Builder (January 2020) - Bcc773
//----------------------------------------------------------------//
function LocalCount( nProcLevel )
return HB_DBG_VMSTKLCOUNT( nProcLevel + 1 ) - ParamCount( nProcLevel + 1 )
//----------------------------------------------------------------------------//
function ParamCount( nProcLevel )
return Len( HB_DBG_VMPARLLIST( nProcLevel + 1 ) )
//----------------------------------------------------------------------------//
function GetParam( nProcLevel, nParam )
return HB_DBG_VMPARLLIST( nProcLevel + 1 )[ nParam ]
//----------------------------------------------------------------------------//Antonio,
Thanks a lot for your answer.
Regards,
Michel D.
Genk (Belgium)
I use : FiveWin for (x)Harbour v. 25.12 - Harbour 3.2.0 (May 2025) - xHarbour Builder (January 2020) - Bcc773
There is an old program called SNAP that will do this. It also does reformatting and cross-referencing of functions. It won't run on 64bit computers so you will have to use it on a 32bit one. You can get it here:
http://www.the-oasis.net/ftpmaster.php3 ... putils.htm
IMHO, you should get rid of privates and publics. If you really need publics you can always encapsulate them in a function or put them in an INI.
James
Thanks for you tip, James.
I didn't know the Oasis of Phill Barnett (I think) still exists.
Regards,
Michel D.
Genk (Belgium)
I use : FiveWin for (x)Harbour v. 25.12 - Harbour 3.2.0 (May 2025) - xHarbour Builder (January 2020) - Bcc773
Michel,
Yes the Oasis is still there and you can still find some useful things there too.
You can do a lot by just turning on warnings and compiling your code. Then initializing all the LOCALs until the warnings go away.
PRIVATEs used to cause me all kinds of grief until I just stopped using them. They are the hardest bugs to find. I think it is best to just get rid of them. I haven't used them in more than 10 years, maybe more than 15 or 20. Stamp them out.
And you can store all PUBLICs in a static var in a function. The var is a class which contains all the vars you need. So, for instance, you could get the path to the data from anywhere in the program something like this:
app():dataPath
And the font face:
app():fontFace
Easy. No PUBLICs.
James
