Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #11247 > unrolled thread
| Started by | "Jamal" <noooospam@example.com> |
|---|---|
| First post | 2017-12-20 13:44 -0500 |
| Last post | 2017-12-22 07:32 +0100 |
| Articles | 4 — 2 participants |
Back to article view | Back to comp.lang.clipper.visual-objects
Find dead (unused) code in a VO app "Jamal" <noooospam@example.com> - 2017-12-20 13:44 -0500
Re: Find dead (unused) code in a VO app "Wolfgang Riedmann" <wriedmann@gmail.com> - 2017-12-21 06:02 +0100
Re: Find dead (unused) code in a VO app "Jamal" <noooospam@example.com> - 2017-12-21 16:24 -0500
Re: Find dead (unused) code in a VO app "Wolfgang Riedmann" <wriedmann@gmail.com> - 2017-12-22 07:32 +0100
| From | "Jamal" <noooospam@example.com> |
|---|---|
| Date | 2017-12-20 13:44 -0500 |
| Subject | Find dead (unused) code in a VO app |
| Message-ID | <p1eb1s$jed$1@news.albasani.net> |
Hi, Is there a tool to find dead code or unused (orphan) code in a VO app to remove the bloat and reduce app size? 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. Jamal
[toc] | [next] | [standalone]
| From | "Wolfgang Riedmann" <wriedmann@gmail.com> |
|---|---|
| Date | 2017-12-21 06:02 +0100 |
| Message-ID | <fa0tj9Fp99fU1@mid.individual.net> |
| In reply to | #11247 |
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 --
[toc] | [prev] | [next] | [standalone]
| From | "Jamal" <noooospam@example.com> |
|---|---|
| Date | 2017-12-21 16:24 -0500 |
| Message-ID | <p1h8qm$2q9$1@news.albasani.net> |
| In reply to | #11248 |
Hi Wolfgang, Maybe X# under VS 2017 can use the built-in analysis tools to detect unreferenced code. I am still waiting on the DBFCDX RDD in X# to take a dive into it. Right now I am just sitting on the sidelines. Jamal "Wolfgang Riedmann" wrote in message news:fa0tj9Fp99fU1@mid.individual.net... 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 --
[toc] | [prev] | [next] | [standalone]
| From | "Wolfgang Riedmann" <wriedmann@gmail.com> |
|---|---|
| Date | 2017-12-22 07:32 +0100 |
| Message-ID | <fa3n8lFehoaU1@mid.individual.net> |
| In reply to | #11251 |
Hi Jamal, > Maybe X# under VS 2017 can use the built-in analysis tools to detect > unreferenced code. with .NET it should be easier because such a tool can work on the binaries. And the tool industry is very large... > I am still waiting on the DBFCDX RDD in X# to take a dive into it. > Right now I am just sitting on the sidelines. I'm waiting too, but in the meantime I'm delivering applications written in native X# Core dialect, and preparing the move using the Vulcan libraries. I cannot wait until the full runtime is ready. Wolfgang --
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.clipper.visual-objects
csiph-web