3 ms·
It's funny to see but this is just documentation for a COM API function that runs a macro with any number of arguments (depending on the macro you want to run).
by jug 5y ago
It's funny to see but this is just documentation for a COM API function that runs a macro with any number of arguments (depending on the macro you want to run). That's why it doesn't use a typesafe delegate or something more clear but a lot of ugly "object"s; it has to pull it off with the lowest common denominator for .NET and COM. It's also not part of .NET but a generated COM interop shim to make the Excel interface callable from .NET.
- cm2187 5y agoAlso you can refer to a macro from another assembly that is not referenced by your assembly (you couldn't reference an xla addin from an ExcelDna .net addin for instance).
- rob74 5y ago"Any number of arguments", as long as that number is <= 30. But I hope that's enough for most use cases...
- bentcorner 5y agoThe developer ergonomics make more sense when you look at this from the VB side of things (positional or named arguments with everything optional), it's just the interop that is messy.
- jevgeni 5y agocough Scala 2 tuples cough