Matthew Aidekman

If I have an abstraction that utilizes arguments, and I de-encapsulate it. The arguments at the top level patcher get the stuff that I typed into the box and the patchers at every other level retain the #0 #1 language.

is-it-a-feature-de-encapsulation-and-format-arguments

not to be persistent about this. but just to alert you guys, it appears that my strategy of making patches with #0 in them and de-encapsulating them is entirely worthless. I've been exploring the issue a few more hours now and there are more 'issues' having to do with nested abstractions and using #0.

I hope someone will take a look at this because this strategy has always been very helpful in the past, and being able to do it with #0 would certainly be nice.

not to be persistent about this. but just to alert you guys, it appears that my strategy of making patches with #0 in them and de-encapsulating them is entirely worthless.  I've been exploring the issue a few more hours now and there are more 'issues' having to do with nested abstractions and using #0. 

I hope someone will take a look at this because this strategy has always been very helpful in the past, and being able to do it with #0 would certainly be nice.


hm. what could work for you is to use a sub-abstraction with 

the #0 inside instead of #0-ing in the patch.

this has been helpful sometimes already when programming or 

updating abstractions because the do work -including their #0

hm. what could work for you is to use a sub-abstraction with 
the #0 inside instead of #0-ing in the patch.

this has been helpful sometimes already when programming or 
updating abstractions because the do work  -including their #0
stuff - when opened and edited.

UPDATE. in addition to the stuff I was talking about before,

This appears to be a very reproducible bug.

Basically if your bpatcher is inside a bpatcher. And you copy the outer one, the inner one's arguments get totally screwed up. It seems like every ten minutes I'm finding a new bug with bpatcher arguments. weird...

UPDATE.  in addition to the stuff I was talking about before,
This appears to be a very reproducible bug. 

Basically if your bpatcher is inside a bpatcher.  And you copy the outer one, the inner one's arguments get totally screwed up.  It seems like every ten minutes I'm finding a new bug with bpatcher arguments.  weird...


[is it a feature?] De-encapsulation and #format arguments