That isn't what you said, let me remind you again.whyterabbyt wrote: Are you trying to claim that, say, source code isnt data? Do you have some 'casual' meaning for data too?
A reaktor ensemble is code. It most certainly does DO SOMETHING in exactly the same way that native code DOES SOMETHING. Of course code is data, but it's no less true in one instance as another, as I have already pointed out.a Reaktor ensemble or Kontakt patch doesnt do anything. its data to dictate what something else will do.
Beyond that, I'm not really talking about "what you said." I don't give a toss.
The distinction that you drew between Reaktor and native code was trite and you've droned on trying to pedantically pick holes into the larger abstraction that I described. Seriously dude, I'm not going to engage you point by point on this.
BTW: When I said 'casual', I meant in casual conversation among experts.
Actually, I was really surprised that you took issue with its use, consequently, I'm still not convinced that you did know the meaning beyond, perhaps, a very specific application of the term.Are you just pissed off because I did know the term, and its correct useage, and highlighted the actual terms you would have been better off using?
Here's a paper which uses the phrase in a similar manner that's talking about "execution flow" being bound to an "execution environment."
http://dl.acm.org/citation.cfm?id=1168064
This is what I mean by casual use of the verb bind in a CS context. It only means slightly more than it does in lay language. The definition that I shared with you is really as precise as it needs to be for this kind of usage. It's a part of my vocabulary, and I was genuinely surprised that it is not a part of yours.
In fact, here is a use of it that is not only almost precisely the same as mine, but uses it explicitly in a claim
http://en.scientificcommons.org/42424675
These are published papers by established computer scientists. Do you really still need more evidence that you are simply incorrect?An interpreted script is bound to its execution environment loosely through the interpreter, while a compiled script needs to be bound to the execution environment much more tightly than an interpreted script