Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #2347 > unrolled thread
| Started by | Martin <spam@spam.spam> |
|---|---|
| First post | 2011-10-31 12:19 +0000 |
| Last post | 2011-11-03 10:47 +0000 |
| Articles | 3 — 2 participants |
Back to article view | Back to comp.lang.clipper.visual-objects
PITA bug in the compiler Martin <spam@spam.spam> - 2011-10-31 12:19 +0000
Re: PITA bug in the compiler D.J.W. van Kooten <public@ic2remove.this.com> - 2011-10-31 13:34 +0100
Re: PITA bug in the compiler Martin <spam@spam.spam> - 2011-11-03 10:47 +0000
| From | Martin <spam@spam.spam> |
|---|---|
| Date | 2011-10-31 12:19 +0000 |
| Subject | PITA bug in the compiler |
| Message-ID | <onwrq.2470$NU1.2262@newsfe01.ams2> |
I had a VERY SIMPLE program bug, basically I had a missing server. I had exported - imported from my development to my live build repository. Compiled over 1000 errors, could not find the error which started it. Deleted and reimported, reindexed ect ect. Exported errors to text file - no error in the class declaration yet it was missing. Went through class declaration looking for the dependancies - ONE NEW DATA SERVER I forgot to export import. VO Error System - I do not need to know over 1000 times the unimportant errors why the later code won't compile I need to know why the class declaration would not compile.
[toc] | [next] | [standalone]
| From | D.J.W. van Kooten <public@ic2remove.this.com> |
|---|---|
| Date | 2011-10-31 13:34 +0100 |
| Message-ID | <9t4ta752g48pkr99e89s1d49d18ohgmrg0@4ax.com> |
| In reply to | #2347 |
On Mon, 31 Oct 2011 12:19:34 +0000, Martin <spam@spam.spam> wrote: Hello Martin. >I had a VERY SIMPLE program bug, basically I had a missing server. >Exported errors to text file - no error in the class declaration yet it >was missing. > Although the 2.8 repository system is much more stable than that of preceding versions, what you describe is common practice in VO. This is what you need to do; try the nex tstep if one step does not help. 1 Reindex the project 2 Toch entities (all or the mef where the missing class was not noticed) 3 Export all libraries, create a new project and re-import them all (after leaving your VO dierctory, rename the project's subdirectory so you can go back if you forgot something). 2.8 takes care of creating missing libraries and overwriting these when they will be there anyway during the import process, which saves a lot of time. 4 In case the exported AEF still contains a corruption: go to the offending mef, copy all source code to an external texteditor, re-create the windows/menus etc in a new empty mef (you can give a temporary name to the window, Ctrl A all controls, copy them on the new window and after deleting the offending mef, rename the window back and add the class additions. Open the window, move a control a bit so it will be rebuild (with a new resource entity). Add the sources again. Good luck! Dick
[toc] | [prev] | [next] | [standalone]
| From | Martin <spam@spam.spam> |
|---|---|
| Date | 2011-11-03 10:47 +0000 |
| Message-ID | <Diusq.574$a82.6@newsfe26.ams2> |
| In reply to | #2348 |
Wasn't corruption, was an issue with the compiler error generator, I needed to know why the class would not compile, but the error was off the list On 31/10/2011 12:34, D.J.W. van Kooten wrote: > On Mon, 31 Oct 2011 12:19:34 +0000, Martin<spam@spam.spam> wrote: > > Hello Martin. > >> I had a VERY SIMPLE program bug, basically I had a missing server. >> Exported errors to text file - no error in the class declaration yet it >> was missing. >> > Although the 2.8 repository system is much more stable than that of > preceding versions, what you describe is common practice in VO. This > is what you need to do; try the nex tstep if one step does not help. > > 1 Reindex the project > > 2 Toch entities (all or the mef where the missing class was not > noticed) > > 3 Export all libraries, create a new project and re-import them all > (after leaving your VO dierctory, rename the project's subdirectory so > you can go back if you forgot something). 2.8 takes care of creating > missing libraries and overwriting these when they will be there anyway > during the import process, which saves a lot of time. > > 4 In case the exported AEF still contains a corruption: go to the > offending mef, copy all source code to an external texteditor, > re-create the windows/menus etc in a new empty mef (you can give a > temporary name to the window, Ctrl A all controls, copy them on the > new window and after deleting the offending mef, rename the window > back and add the class additions. Open the window, move a control a > bit so it will be rebuild (with a new resource entity). Add the > sources again. > > Good luck! > > Dick
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.clipper.visual-objects
csiph-web