Unused Methods

[Mike Kerner]

I'm not trying to be a smart-ass with this, so don't take this as some
dismissive remark.  What I really want is to get everyone who gets
interested in one little piece of the IDE to crack the lid on it and work
on it.

The easiest way, IMHO, to do what you are suggesting, is to add some code
to the script editor that will index every handler (and every keyword,
taking it to a logical conclusion), and index them.  I haven't poked my
head into the script editor, yet (although I have a bunch of things I want
to have done to it), so I don't know if part or all of that suggestion is
already implemented, but I would be willing to bet that it is not.

If you wanted to make this task a little more manageable, you could develop
the keyword/handler indexer using the database routines, and store the data
in a table in sqlite that was part of each project.  The search would then
have an option to use the index or do it brute-force, and, of course, there
would need to be an option to rebuild the index, periodically.

Just in case you don't decide to implement this, I'm adding both of those
ideas to my script editor wish list, in case we ever get a script editor
team together as we get closer to getting 8 out.



On Sat, Jun 6, 2015 at 9:29 AM, Terence Heaford <t.heaford at icloud.com>
wrote:

> What made me ask this question is because of the amount of time it takes
> the IDE to find and list methods that I ask it to find.
>
> This would be an acceptable way of working if it wasn't so slow.
>
>
> All the best
>
> Terry
>
>
>
> > On 6 Jun 2015, at 13:42, Mike Kerner <MikeKerner at roadrunner.com> wrote:
> >
> > No, and that would be quite a bit harder, here, because the structure is
> > different:  "Send", "Dispatch", and "Do" will all let you build a call,
> > dynamically, to any handler in any stack.  Plus, since everything is
> > event-driven, one would have to determine everything that is user-event
> > driven, and ignore those, everything that is engine-event driven, and
> > ignore those, and then evaluate everything else.
> >
> > The good news is that you (or anyone else for that matter) should be able
> > to write such a routine, because of the way that you can access pretty
> much
> > anything in LC.
> >
> > On Sat, Jun 6, 2015 at 3:18 AM, Terence Heaford <t.heaford at icloud.com>
> > wrote:
> >
> >> In many development environments there is a function to find
> >> unused(uncalled) methods, does such a function exist within the LiveCode
> >> IDE?
> >>
> >>
> >>
> >> All the best
> >>
> >>
> >> Terry
> >> _______________________________________________
> >> 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
> >>
> >
> >
> >
> > --
> > On the first day, God created the heavens and the Earth
> > On the second day, God created the oceans.
> > On the third day, God put the animals on hold for a few hours,
> >   and did a little diving.
> > And God said, "This is good."
> > _______________________________________________
> > 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
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."