> Imagine I have two novels.
>
> On page 100 of Novel A, there is an instruction: Open up Novel B, turn to
> Chapter 7. When finished, come back to this point and continue reading.
>
> As the reader, (the processor in this analogy) I follow these
instructions.
> My "thread of execution" takes me
From: "David Johnson" <[EMAIL PROTECTED]>
> > Making a function call
> > is not the same thing as actually incorporating the code of that
function
> > into the body of the calling code.
>
> Though I'm on your "side", there is a big difference between data transfer
> and code execution. Transferri
On Thursday 22 February 2001 10:37 pm, Ryan S. Dancey wrote:
> I'm suggesting that the definition of a derivative work can't include data
> being passed between two independent pieces of code, via file, via a
> network, or via an internal process communication. Making a function call
> is not th
Inadvertantly sent just to Mr. Dixon - my apologies to him for the double
post.
From: "Rod Dixon, J.D., LL.M." <[EMAIL PROTECTED]>
[ I said, in reference to various library linking examples:]
>> How can that create a derivative work?
>>
> Well, the question is why wouldn't it?
Because you're no
4 matches
Mail list logo
