On Wed, Apr 10, 2013 at 5:05 AM, Alexander Mueller <ddo...@gmail.com> wrote:
> one could extend that idea to include multiple vocabularies and
> create/extend vocabularies,
Could imagine including the whole codebase and running it with the build.
:]
> though i could imagine this getting kind-of
> tedious and messy :-D
Maybe it's something best left as a reporting tool, rather than as an
interactive tool.
> you would also want some constraints to what should be considered for
> refactoring,
Good point.
> as in actually reducing codesize: you wouldn't want to refactor
> 2 words used in two places like dip dup (i know, bad example) and call it
> dipperdupper.
If left as a reporting tool, the user could be informed of dipperdupper
cases, but would choose to ignore them.
>
> just my two cent
http://books.google.com/books?id=lbl4MN3iUHsC&pg=PT49&dq=second+half+of+the+chessboard&hl=en&sa=X&ei=tDJlUbq-Nanq0wHwrYDYCw&ved=0CDEQ6AEwAA
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
