On Feb 14, 2009, at 1:40 PM, Dan Larkin wrote:
But as an aside, does this seem to anyone else like a wart on an otherwise great language? Thinking about file layout should not be one of my priorities... the language should not encourage me to put everything together in one file just to get it to work. I should be able to separate functionality in a way that makes sense to the app I'm building.
Within one namespace, we use declare to avoid this problem. Perhaps declare could be extended (or another function created) to work with namespace-qualified symbols that refer to namespaces and vars that may not yet exist. I would imagine this would involve creating the namespace and var within it if either didn't yet exist and pushing the namespace name onto some "deferred load" queue so it's guaranteed loaded by the time the top level load is complete.
For this to be effective in our preferred way to declare dependencies, it should be a new clause in within "ns".
Any thoughts? --Steve
smime.p7s
Description: S/MIME cryptographic signature
