Identifying Un-used functions and commands

[Ralph DiMola]

"DO"s make this tricky. EX: Say you have some code that is mobile platform specific. do "myHandlerBaseName&the platform param1, param2". This example may not be good practice but "DO"s can trip you up looking for orphan handlers.

Ralph DiMola
IT Director
Evergreen Information Services
rdimola at evergreeninfo.net

-----Original Message-----
From: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] On Behalf Of dunbarx--- via use-livecode
Sent: Tuesday, November 12, 2019 12:43 PM
To: use-livecode at lists.runrev.com
Cc: dunbarx at aol.com
Subject: Re: Identifying Un-used functions and commands

Hi.
"unused functions and commands"?
Do you mean handlers that exist in a script somewhere but are never called from anywhere?
I suppose you can search all scripts, and if a certain handler name does not appear without being prepended by either "on" & space(s) or "function" & space(s) then you can say that handler is never called.
Craig


-----Original Message-----
From: Stephen MacLean via use-livecode <use-livecode at lists.runrev.com>
To: How to use LiveCode <use-livecode at lists.runrev.com>
Cc: Stephen MacLean <smaclean at madmansoft.com>
Sent: Tue, Nov 12, 2019 12:14 pm
Subject: Identifying Un-used functions and commands

Hi All,

I’m wondering if anyone has a way or code to identify any un-used functions and commands in a set of stacks?

Best,
Steve MacLean

_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode