Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Wolfgang Riedmann" Newsgroups: comp.lang.clipper.visual-objects Subject: Re: Find dead (unused) code in a VO app Date: Thu, 21 Dec 2017 06:02:32 +0100 Lines: 33 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Trace: individual.net RRCH5RaIbj+YvBoHknP/uA9rCHcP88hVaAMME2/Fvn2auzAGQ= Cancel-Lock: sha1:Kej85lu3JDoJYScA/+4kxY534z8= User-Agent: XanaNews/1.18.1.6 Xref: csiph.com comp.lang.clipper.visual-objects:11248 Hi Jamal, > Is there a tool to find dead code or unused (orphan) code in a VO app > to remove the bloat and reduce app size? this is very difficult and dangerous, but AFAIK there was such a tool somewhere. > For example, when deleting entities like a data window, some code > like DEFINE statements are are left behind. Sometimes there are > functions that are never called in app. to clean up the define statements, after larger modifications of a window I delete all the generated code, open the binary entities and rebuild the code. I'm not using the DBServer editor or the SQL Editor so I don't have all the myriads of access/assign methods and the FieldSpec entities - I generate the fieldspecs on the flight from a dictionary of my database. IMHO these are the real bloat in many VO applications. And if you would like to save memory: build monolithic applications. Using for example bBrowser as lib instead of a DLL saves a few 100 KB in total executable size. VO is linking in all classes and methods from a libraries, not only these that are used. Wolfgang --