Forum Discussion
MarkRoddy
16 years agoVisitor
enorris We use Nullsoft NSIS for installers at my job. I cringe whenever we have to change them. So many junk installs on my workstation from debugging them.
I have been toying with the idea of writing a BrightScript interpreter or maybe just a parser to find syntax errors which could be hooked up to emac's flymake-mode to highlight errors. I'm not yet sure that the it makes sense from a cost/benefit standpoint (lot of work and would it really help that much comparitably?).
In the mean time you might want to check out the testing library I released last week. While it's not as convenient as locally running interpreter, I find it's a much easier way to work since I can write tests for the logic of an app, push changes to my box, and immediately the results of the tests instead of having to push out the changes and click through each UI element every time to see if I broke anything.
http://code.google.com/p/brstest/
-Mark
I have been toying with the idea of writing a BrightScript interpreter or maybe just a parser to find syntax errors which could be hooked up to emac's flymake-mode to highlight errors. I'm not yet sure that the it makes sense from a cost/benefit standpoint (lot of work and would it really help that much comparitably?).
In the mean time you might want to check out the testing library I released last week. While it's not as convenient as locally running interpreter, I find it's a much easier way to work since I can write tests for the logic of an app, push changes to my box, and immediately the results of the tests instead of having to push out the changes and click through each UI element every time to see if I broke anything.
http://code.google.com/p/brstest/
-Mark