D
dbeavon
Guest
>> You'll also be able to use multiple threads to build OE projects (for procedures, not for classes). Its a bit off topic but what's the problem with compiling OE classes in parallel? I've never run into trouble as long as all the prior r-code in a project was cleared out as a first step. (I do realize that the compiler will not understand the dependency relationships between classes. It will probably do a lot of duplicated work, whenever it is compiling stuff in a sequence that is not respectful of the class dependency relationships. ) BTW, the OE AVM within PDSOE doesn't do a great job with dependency relationships either. I'd like to see this improved in PDSOE one day. The "restart AVM" operation is something I use all the time, after deleting my r-code. Otherwise the wrong OOABL "sticks" in memory and causes bogus compiler errors - possibly because of r-code which is outdated, or because the AVM simply gets confused by something it is keeping in its memory. Speaking of bogus compiler issues, here is another one simple thing that happens all the time which is pretty annoying. I copy one class to another and change the code (w/search/replace) rename the file (correctly) and save. Then I use the "check syntax" operation to ensure that I did all the steps correctly. But the first time I check syntax on my new class, it always tells me that I did something wrong (image). But if I immediately check again then it tells me that my syntax is OK. Whats up with that? On yet another note, has anyone tried the new refactoring stuff for OOABL? I'm hoping there is something in OE 12 that will improve productivity, especially for those of us that did the work to start using OO.
Continue reading...
Continue reading...