3 ms·
In Smalltalk, if you're curious about ??, you'd be able to find it instantly, and read the method. As you know from the article, it's fairly short and would be
by stcredzero 18y ago
In Smalltalk, if you're curious about ??, you'd be able to find it instantly, and read the method. As you know from the article, it's fairly short and would be obvious to a competent Smalltalker in seconds. If that's not enough just take a second to type in
nil ?? [ self halt ]
And right-click "Debug-it." Debugging in VisualWorks is so painless, people actually write code in comments for people to understand by debugging -- and people will even follow it while in another debugger session! (And even doing that a 2nd, 3rd time is just as easy!) To heck with comments or API docs, you can see how everything works and tinker with it!
Your division between access by the implementer vs. the "fresh set of eyes" is a misconception you're taking from C#. There is nothing in Smalltalk that demarcates the "implementer" from the regular programmer. It's "Turtles all the way down!" You can actually implement a debugger as an ordinary Smalltalk app, and in 5 minutes, you can be browsing a stack. There is little difference between programming and meta-programming.
In other words, Meta-programming is easy and natural, not esoteric.
You just see Smalltalk as a funny sort of Blub where no one knows what the language/library will look like, because you see things in terms of the programming you know: Blub. Take it from me, I've been to dozens of Smalltalk shops over a decade: this is not a problem. It's sometimes a huge advantage! One can create very powerful domain-specific languages and tools this way.