@jens Critical bug
@simplesi
@cymplecy
edit:
This is the weirdest thing ever in Snap !
yeah with metaprogramming
in the code you are actually modifying a function when its running so its wormy
Jens is on vacation for a week so don't expect an immediate response, but thank you.
This is the experiment you can try: Snap! This is so weird (berkeley.edu)
oh ok
i wouldn't call that a critical bug, as the spewed out upvar returns to normal when you reload the project, and you can avoid it by not touching it.
i mean... i'm pretty sure this is what define is intended to do. i don't think they're going to change it. you can just not make a loop that defines a bunch of blocks.
and you could also create a memory "leak" by making a clone script that makes a bunch of clones. and this isn't a memory leak anyway -- that's when there's memory allocated that isn't known by the program.
You can even make this???
![]()
I found something weirder. Do these steps above, then:
- Right-click the "this script" upvar (not the latter "this script"), then choose "ringify"
- Take out the ring.
- Then the resulting upvar is weird.
- If you run the block, Snap! freezes, but will not crash.






