Upvars vs. empty input slots

Advanced Topics
22

(Sigh.) No, it doesn't. I made up the name before Jens made up the visual representation. @dardoro is correct that it comes from the traditional technical vocabulary about moving "down" to a subprocedure and back "up" to its caller. (I didn't have the words "stack frame" in mind, although it probably is because of downward-growing stacks that these direction names were first used.) And @snapenilk is right that in modern IDEs it's more common to see "jump in," "jump over," and "jump out" when single-stepping.

Maybe we should just call them "backward inputs."

23

we should just call them "output".

24

I guess, but "output" can also mean the value a function reports. If we were careful to say "output variable" it might work.

25

ah, good point. Hmm.... maybe I like "upvar" after all :slight_smile:

26

My 2 cents - block variables (abbv to blockvars)
[edit]@sathvikrias is of course right

27

but snap! already has something called "block variables", and they're different.

28

why "of course"?

29

maybe outvar? which spanenlik already suggested, which i found out shortly after coming up with "outvar".

30

snapenilk*

31

Maybe argument variables?
(I know this sounds horrible)

32

I could live with outvar I suppose.

33

Hello, hey could fix renaming upvars because it isn't working? It's very annoying having to use "a" "b" "c" "d" and not being able to rename them.

34

You just normally click on them and you can change their name

35

Be careful not to drag them a tiny bit, because that means something else.