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
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
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
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
> 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
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-livecode
> To: How to use Liv
ces 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 or fu
ll.
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
Subject: Re: Identifying Un
- 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
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
reen 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: Identifying
unction" &
space(s) then you can say that handler is never called.
Craig
-Original Message-
From: Stephen MacLean via use-livecode
To: How to use LiveCode
Cc: Stephen MacLean
Sent: Tue, Nov 12, 2019 12:14 pm
Subject: Identifying Un-used functions and commands
Hi All,
I’m
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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and
13 matches
Mail list logo