Hello again! > > I would suggest you use the following format for $system.OBJ.Compile: > > Do $system.OBJ.Compile( class, "bruy" ) >
,,we have been using "r-bkvu" until now, and also tried a lot of combinations, no results. > From the documentation (Do $system.OBJ.ShowFlags()), "b" will compile > subclasses; "r" compiles all classes that are dependency predecessors; > "u" avoids compiling up-to-date classes (albeit as you say sometimes you > need "f", the opposite); and "y" finds dependencies within SQL (and I > don't remember seeing that one before!) > The "y" is something new, I really need it! Our problems are 99% with SQL. Although I just tried, no visible changes to the results (with 5.07). :-( I'm thinking about moving all our queries apart, into different classes which somehow will be compiled later. But it's a disaster, we have about 150 of them... Also, having good tests is difficult, we always have to start with an empty database, or the tests will be influenced by what we have compiled before. I understand that it's a complicated issue to solve for ISC, but a compiler which doesn't know how to compile its classes is a big limitation for OO enterprise projects. We need to scale to about 1000 classes by the end of the year, and now I'm seriously starting to worry about it. Max
