Lazy Python: Difference between revisions

From ym2149.org
Jump to navigationJump to search
No edit summary
No edit summary
 
Line 2: Line 2:


Adding such functionality to Lurlene direct is very difficult as there does not seem to be a way to do so iteratively. So there is probably scope for a new library with extensive unit tests that Lurlene can adopt once it is sufficiently ready, so that existing code continues to work with minimal modification and actual live coding becomes possible using that existing code.
Adding such functionality to Lurlene direct is very difficult as there does not seem to be a way to do so iteratively. So there is probably scope for a new library with extensive unit tests that Lurlene can adopt once it is sufficiently ready, so that existing code continues to work with minimal modification and actual live coding becomes possible using that existing code.
[[Category:pym2149]]

Latest revision as of 11:23, 19 April 2024

For Lurlene to be a useful live coding language, it needs to actually satisfy the live coding requirement. Currently updating a global does not update that global in any object that has previously referred to it. The obvious solution is to refer to a global by indexing into the globals dict every time, but we'd like to be able to write natural code and have Lurlene update the references.

Adding such functionality to Lurlene direct is very difficult as there does not seem to be a way to do so iteratively. So there is probably scope for a new library with extensive unit tests that Lurlene can adopt once it is sufficiently ready, so that existing code continues to work with minimal modification and actual live coding becomes possible using that existing code.