latent_object_detector icon indicating copy to clipboard operation
latent_object_detector copied to clipboard

Published 20 hours ago • verified publisher icon kerrizor

Create a CLI

Open kerrizor opened this issue 10 years ago • 1 comments

Often latent objects are scattered across multiple classes; I would argue that cross-class occurrences might be the strongest indicator of latent classes hiding in the code (and usually the most obvious)

Some brainstorm on what /could/ be in such a tool:

  • run from the command line
  • scan an application for models
    • just pick through app/models and lib/ ?
    • walk through object space ?
    • be passed an array of objects or files ?
  • output
    • to STDOUT a nicely formatted report
    • an HTML report, perhaps with line numbers, code highlighting, etc?

kerrizor avatar Mar 11 '14 10:03 kerrizor

This issue seems to mostly be about desired functionality that isn't really dependent on a command-line.

For the CLI, I like GLI?

Perhaps related, are you thinking of static or dynamic analysis? I imagine meta-programming might hide some latent object, and am not sure how comparatively easy it would be to pull that from an AST, versus evaluated code.

bf4 avatar Mar 12 '14 21:03 bf4