Re: Identifying Un-used functions and commands

On 11/28/19 9:52 AM, J. Landman Gay via use-livecode wrote: We should verify whether we're looking for orphaned handlers or orphaned calls. If it's handlers I'd do something like: Scan all scripts for "end" & space to get a list of handlers Remove duplicates Scan all scripts for each handler na

Re: Identifying Un-used functions and commands

We should verify whether we're looking for orphaned handlers or orphaned calls. If it's handlers I'd do something like: Scan all scripts for "end" & space to get a list of handlers Remove duplicates Scan all scripts for each handler name and keep a count If there's only two instances of the han

Re: Identifying Un-used functions and commands

On 11/28/19 8:25 AM, Richard Gaskin via use-livecode wrote: Quentin Long wrote: > Finding explicit function/command calls seems like it should be a > fairly straightforward task. However, the "do" keyword can also be > a source of function/command calls, which complicates matters a > wee bit

Re: Identifying Un-used functions and commands

Quentin Long wrote: > Finding explicit function/command calls seems like it should be a > fairly straightforward task. However, the "do" keyword can also be > a source of function/command calls, which complicates matters a > wee bit. You'll also need to evaluate all the non-cleartext components >

Re: Identifying Un-used functions and commands

> Date: Tue, 12 Nov 2019 12:12:47 -0500 > From: Stephen MacLean > To: How to use LiveCode > Subject: Identifying Un-used functions and commands > Message-ID: > Content-Type: text/plain; charset=utf-8 >  > Hi All, >  > I?m wondering if anyone has a way or code to identify any un-used functions >

Re: Identifying Un-used functions and commands

is no "on myGadget3" anywhere. Then you will have > found an unused handler call. > This may require tweaking. For example, LC will compile, say: > "on        myGadget3"  -- spaces galore > > Craig > > -Original Message- > From: Bob Sneidar via use-liv

Re: Identifying Un-used functions and commands

   myGadget3"  -- spaces galore Craig -Original Message- From: Bob Sneidar via use-livecode To: How to use LiveCode Cc: Bob Sneidar Sent: Mon, Nov 25, 2019 12:29 pm Subject: Re: Identifying Un-used functions and commands Since there is code in the script editor that knows the loc

Re: Identifying Un-used functions and commands

ve found an unused handler call. This may require tweaking. For example, LC will compile, say: "on myGadget3" -- spaces galore Craig -Original Message- From: Bob Sneidar via use-livecode To: How to use LiveCode Cc: Bob Sneidar Sent: Mon, Nov 25, 2019 12:29 pm Su

Re: Identifying Un-used functions and commands

- spaces galore Craig -Original Message- From: Bob Sneidar via use-livecode To: How to use LiveCode Cc: Bob Sneidar Sent: Mon, Nov 25, 2019 12:29 pm Subject: Re: Identifying Un-used functions and commands Since there is code in the script editor that knows the location of any command

Re: Identifying Un-used functions and commands

Since there is code in the script editor that knows the location of any command or function you right click on, if you found out how they do that, you would be well on your way to developing a way to grok it. Also, GLX2 has a "clairvoyance" (Auto-Complete) function that is handler aware. I suspe

RE: Identifying Un-used functions and commands

vergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of dunbarx--- via use-livecode Sent: Tuesday, November 12, 2019 12:43 PM To: use-livecode@lists.runrev.com Cc: dunb...@aol.com Subject: Re:

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 c