Re:Obsidian: A safer blockchain programming language
by derefr on Friday May 31, 2019 @06:28PM
(#20065621)
> though I find piles of complexity added by classes/methods the exact opposite of simple.
I mean, the model of your objects calling methods on other objects (that you don’t control)—and having your methods called by those same objects in turn—is inherent in the abstract machine being programmed for. You don’t have to use express the internals of your program as classes and methods, but that’s how people are going to see your contract “from the outside”, and that’s also how you’re going to have to interact with other contracts.
I mean, the model of your objects calling methods on other objects (that you don’t control)—and having your methods called by those same objects in turn—is inherent in the abstract machine being programmed for. You don’t have to use express the internals of your program as classes and methods, but that’s how people are going to see your contract “from the outside”, and that’s also how you’re going to have to interact with other contracts.