getting into the url cache

[Monte Goulding]

>
> I appreciate your chiming in here, Monte.  I'll double-check my code, but
> the implications of your presumably functioning code example
> above are quite
> a change to my understanding of things:  I can use raw data (from a valid
> stack file, of course) instead of a stack descriptor with the "go stack"
> command?  Hmmm....
>
It's reasonably easy to understand. It's just an order of operations thing.

go stack url "http://mydomain.com/myfile.mc"

is

go stack (url "http://mydomain.com/myfile.mc")

I had the same challenge understanding:

put url "http://mydomain.com/myfile.gif" into image "myimage"

Obviously you can think of it as:

go stack <whatever evaluates to the data of a stack>