| 01:40 | <Francisco Tolmasky> | Is there anywhere the spells out the choice of when to use the term "instantiate" vs. "construct" vs. "create" vs. "make". From what I can tell they follow that "call order", with make being the lowest level "allocate", but its not clear to me when a construct should be an instantiate |
| 01:45 | <jmdyck> | You mean in operation names? |
| 01:46 | <Francisco Tolmasky> | Right |
| 01:47 | <jmdyck> | I don't think so. |
| 01:48 | <Francisco Tolmasky> | InstantiateOrdinaryFunction calls CreateOrdinaryFunction for example |
| 01:48 | <Francisco Tolmasky> | errr OrdinaryFunctionCreate* |
| 01:49 | <Francisco Tolmasky> | (There's also that weird Verb prefix/suffix tension, the Construct and Create like to be suffixes, Make and Instantiate like to be prefixes) |
| 01:56 | <jmdyck> | InstantiateFoo tends to operate on Parse Nodes (it's usually an SDO), whereas CreateFoo (or FooCreate) is usually building a specific kind of object. |
| 01:57 | <jmdyck> | Which is why you're likely to see Instantiate call Create but not vice versa. |
| 02:01 | <jmdyck> | Construct in an op name is normally closely associated with [[Construct]] semantics. |
| 02:04 | <jmdyck> | Make is kind of a wild card. |
| 02:10 | <Francisco Tolmasky> | gotcha |