Problem compiling with included text -type files...

[KimF]

Hello, has anyone run into a similar problem as we?
This is an old problem (not a 7.1 problem), that has forced us to this solution

We have a .apt -file where we have included a lot of files, where the actual code is and then we have class code -files included to these files - normal isn't it

To make compiling (F8) of the header .apt -file work (after saving an included file), directly after it refreshed itself we have been forced to save the included files as .apl -files.

If we save included files as .apt and compile the header .apt -file, as described above, we get really many errors like this:
Error: Handle Semi-qualified reference not allowed because multiple definitions of pbShowRsts occur with inconsistent types.
These errors disappear after Refresh Libraries (F6) of the header -file

Thanks,
Kim

[memic]

Hi,

I also have the same Problem (TD 7). Mostly doing manually "Refresh Librarys" helps.

This occours every time I edit some big libraries. The automatic Library Refresh doesn't work in that case... I don't get this error when editing smaller libraries.

[Dave Rabelink]

I always found the automatic refresh on big projects very instable.
Sometimes it results in compile errors or even crashes when compiling.

I have myself automated that I reload the main app/apt file when libraries have changed.

[Dave Rabelink]

If we save included files as .apt

What do you mean by this?

Are you including an .apt file as library, for instance Include library: MyFile.apt ?
Or do you mean that the files are text format?

As for including MyFile.apt, why would you do that?

Libraries should always have the .apl extension (and preferably saved as TEXT format).
Application/Dynalib main files should be .apt or .app (depending on the used format, but preferably saved as TEXT format).

[KimF]

We would like to save the included files as text -files
This because then we could use other repository and diff-tool than what gupta offers

At Open Text's roadshow, I got this picture of td7.1 that it should make this possible

Kim

[bheilscher]

If the include files does not contain any class definitions, define a (dummy) class in each file.
Then the automatic refresh should work.

Bernd

[Peter.Hugk]

We would like to save the included files as text -files

You can select Text as file format and still use the ending APL.

Regards,
Peter

[KimF]

I doubt, that the file's extension has anything to do with this problem - the problem appears because the included file is saved as a text -file

Kim

[Igor Ivanovic]

IMO you stumbled on an old bug with automatic refresh.
I reported it to (then) Gupta, even created a small use case showing it, but it was never solved.
The problem is that the changed included file is always placed at the end of the main app and that somehow messes up the outline resulting in compile errors and general instability when compiled successfully.

As Dave, I have automated myself to always: refresh all (F6) and compile (F8).

[KimF]

https://knowledge.opentext.com/knowledg ... /KB5811062

[EwaldP]

I have included about >120 files (saved as text) in my main application (also saved as text). With 3 libraries I have the same problems as described above. I can't commit that the problem has a relation with the file size but if I insert a gui class (e.g. form window class) the problem doesn't occur.

My workaround is that if I have anything to do in my 3 problem libraries I uncomment a dummy gui class. Compiling is much faster. Before making the build I comment these dummy classes and make a "refresh all".

[Uwe van der Horst]

My workaround is that if I have anything to do in my 3 problem libraries I uncomment a dummy gui class. Compiling is much faster. Before making the build I comment these dummy classes and make a "refresh all".

One of the best hints ever, it works perfect here. I also automated myself to refresh all (F6) and compile (F8). Knowing this trick earlier I would have saved a lot of time. Thank you so much, Ewald.

[EwaldP]

glad to hear

[KimF]

A workaround - not a solution...

I just did a quite stupid test, that seems to fix this problem...

I just added a comment to the included file's class -part
Just a new line with an exclamation mark (!)

This makes header file to autorefresh its classes every time you save a included file with this comment in its class -part

Kim