Anyone tested this? Delphi uses cleaner wizard and a dependency analyzer. Looks really promising. 100% discount and Tokyo support
Anyone tested this? Delphi uses cleaner wizard and a dependency analyzer. Looks really promising. 100% discount and Tokyo support
https://delphiparser.com/2017/04/20/free-delphi-code-inspection-analysis-tools/
https://delphiparser.com/2017/04/20/free-delphi-code-inspection-analysis-tools/
Much blabla for an evaluation version of a useless application.
ReplyDeletehttp://www.easy-ip.net/delphi-unit-dependency-scanner.html does a better job and is free.
Looks like the computer doctor image has been used in breach of copyright.......
ReplyDeleteThe benefit of these analysis tools is almost zero. You better buy a medicine to improve your memory or a good Delphi book.
ReplyDeleteJust tested it.. it doesn't seem to take a very logical approach for analysis: give it directories and it'll scan absolutely everything, rather than analyzing actual dependencies. I like Stefan's suggestion better, but its UI could use improvement. Most other dependency analyzers I've seen seem to be incapable of going more than two unit levels deep. I'm also curious as to why almost all seem to not use the library search paths?
ReplyDeleteDavid Heffernan you've seen that pic before? Or used some water-stamp analysis? It's perfectly viable to get such pix from let's say your "Adobe Creative Suite Subscription" (100 free images... blah blah)... Just asking since i know you are not the one to speculate.
ReplyDeleteStefan Glienke Useless, really? The fact that you don't like it doesn't mean it's useless. Pretty arrogant comment, I would say.
ReplyDeleteOle Ekerhovd Arrogant would be if I said I can slap something like that together in a week using DelphiAST.
ReplyDeleteA commercial tool that competes with free tools has to offer more. This one does not. I did try it out, it failed half of the code I threw at it (missed half the types because they were generic types) and did nothing than just showing a tree with used units and the number of type references. Did not offer any help so I could not check if I was missing something. Which lead to my final verdict.
If your opinion differs, feel free to share your experience - instead of attacking me.
Stefan Glienke
ReplyDeleteThere is no argument, no why, no nothing in your "review". I still think the comment is arrogant.
/sub
ReplyDeleteOle Ekerhovd
ReplyDeleteStefan Glienke is entitled to his opinion, and he does spell out what he didn't like. I see no reason to sugarcoat such posts; they are personal experiences after all.
Trying it on a rather large project with significant issues in the organization of folders. The UI is simplistic, apparently assuming all projects will be arranged as the folks at DelphiParser arrange theirs. It does not find the components, since, as already noted, it is not using the available information in the environment.
ReplyDeleteA larger concern is that it it simply produces a tree, then it has barely begun the work which would actually be needed.
Short summary: Given the things it cannot find, and the limited utility of output, as well as the time consumed reaching that output, the net value is roughly zero, IMHO.
For the record, I would be very happy to find a good and reliable tool which would perform a good analysis, and offer selectable revisions in an automated process. It would be very nice if it would allow selection not only of the revisions to be applied, but selection of a subset of files or folders which would be revised.
ReplyDeleteAmong the desirable functions:
- Detection and removal of unused units.
- Detection of units and methods which can have reduced visibility/scope. And application of suitable revisions.
- Detection of unit in map file which are not in project.
- Detection of units in project which do not appear in map file.
I have done some work in the direction of a tool for these and related purposes, but it is a spare-time development, and lately gets too little attention.
Another interest is in detection of unit dependency cycles, but I have had no time at all to work on that. And a report on such cycles would not lead to any automated resolution, as far as I can see.
Bill Meyer in short, Delphi needs modern, fast, reliable refactoring tools
ReplyDeleteAgustin Ortu Oh, that! If you insist! ;)
ReplyDelete