search

elnewfie / lslforge

Automatically exported from code.google.com/p/lslforge
24 stars 13 forks source link

Please allow circular dependencies. #21

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
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?

Original issue reported on code.google.com by bladam...@gmail.com on 11 Jun 2012 at 4:15

GoogleCodeExporter commented 9 years ago 
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.

Original comment by elnew...@gmail.com on 13 Jun 2012 at 12:43

GoogleCodeExporter commented 9 years ago 
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!

Original comment by bladam...@gmail.com on 5 Jun 2013 at 7:26