This forum is closed to new posts and
responses. The content has been migrated to the Digital Solutions Community. Please join us there for new content as well as this content. For customer support, please visit the official HCL customer support channels below:
- Same error, most likely, but it never hurts to know explicitly.
- Look for "circular use" instances. This is where module A does a use on module B, and module B does a use on module A. Only it goes deeper.
- If module A uses module B which uses module C which uses module D, which uses module A, that's still a circular use. The old LS compiler was pretty poor at catching this, and so your code (depending on complexity) could have a "nested circular use" that the new compiler catches.
Hope this helps...
Feedback response number DGIE7YRL59 created by ~Holly Zekhipisonnivu on 12/15/2009