User:Philosopher: Difference between revisions

Jump to navigation Jump to search
Issue template – Thanks Johan!
(New sections: a look inside my brain ;)
(Issue template – Thanks Johan!)
Line 22: Line 22:
Nasal thoughts area:
Nasal thoughts area:
* I would like to include small improvements that enhance my quality of life in SimGear: string slicing, hash iteration using foreach/forindex, save/restore aka stash? (latter to be discussed)
* I would like to include small improvements that enhance my quality of life in SimGear: string slicing, hash iteration using foreach/forindex, save/restore aka stash? (latter to be discussed)
* I fixed [http://code.google.com/p/flightgear-bugs/issues/detail?id=585&q=Nasal&colspec=ID%20Type%20Status%20Priority%20Summary%20Aircraft%20Milestone#makechanges Bug #585] with like 12 characters of code, besides the obvious workaround of using an all-capture slice expression :).
* I fixed {{issue|585}} with like 12 characters of code, besides the obvious workaround of using an all-capture slice expression :).  The other one, the "boeing" {{issue|737}}, only took 2 lines and 5 seconds.
* Hooray and I talk about more extension functions to allow looking into internals; I need to review all of these, gather them up, add to them, etc., and hope they can be included somewhere (Hooray was saying maybe just the standalone Nasal in SimGear, not FlightGear's runtime).
* Hooray and I talk about more extension functions to allow looking into internals; I need to review all of these, gather them up, add to them, etc., and hope they can be included somewhere (Hooray was saying maybe just the standalone Nasal in SimGear, not FlightGear's runtime).
** Sub-idea: if we only include the extensions in standalone and we have optimizer/post-compiler scripts ready, then make a script to be run with standalone that optimizes any or all Nasal files and outputs an optimized version (*.nas.optimized) or even just the bytecode (*.nas.opcode, textual file ofc) and have that be the preferred loading method (if the text is older than the optimized version).
** Sub-idea: if we only include the extensions in standalone and we have optimizer/post-compiler scripts ready, then make a script to be run with standalone that optimizes any or all Nasal files and outputs an optimized version (*.nas.optimized) or even just the bytecode (*.nas.opcode, textual file ofc) and have that be the preferred loading method (if the text is older than the optimized version).
395

edits

Navigation menu