Please allow circular dependencies.

[RayZopf]

https://code.google.com/archive/p/lslforge/issues/21
Posted on Jun 11, 2012 by Happy Lion Forbidding circular dependencies makes it very difficult to properly modularize some code. Take, for example, two different components on a HUD that loosely depend on each other's data, but are implemented in two different lslm files. It can be worked around in hackish ways, but that breaks the idea of clean encapsulation.

Since it's all going into the same .lsl output file anyway, is there any particular reason that circular dependencies are disallowed?

Comment 1

Posted on Jun 13, 2012 by Helpful Kangaroo Currently modules are implemented in the LSLForge executable, and does not do any circular module detection. A reworking of the compilation process is underway, and this is definitely on the list. A fix will be included in an upcoming release.

Comment 2

Posted on Jun 5, 2013 by Happy Lion Not trying to be a pain or anything, but... :)

How is this feature coming?

I looked into trying to implement this and send you a patch, but... I am too dumb to grok Haskell, hehe.

Thanks for all the work that you do on this plugin!

[RayZopf]

is this feature request still valid with version 0.1.6?