Open rweber89 opened 8 years ago
As an LSLForge user, I have been following new development as best I can. More recently, raysilent has thankfully been making updates in his branch, including instructions for compiling LSLForge. Though I don't know if he plans on doing any work on the code optimizer.
Also, I'm not sure how if it would help for your needs but make sure you are aware of Sei Lisa's LSL-PyOptimizer It may offer an alternative method for optimization than LSLForge.
Apologies if none of this directly answers your question, just added in case it may help :)
I understand that you do not want to support this anymore, but could you please first add preprocessor support? Or if you think that´s too much work, just a way for the parser and .lsl creator to "ignore" any lines starting with a hash and put them in as they are.
That way the .lsl file would contain the hashtags and then the FireStorm preprocessor can use them, as FireStorm supports it.