I'm confused about some aspects of 'Copyright' ..No book starts out without a copyright notice.I've got a couple of 'em on programming. Somewhere in Deitel's C++ one may read something of the meaning ".. when you go to try this particular code, then try this and that ..". That sort of suggests that the copyright doesn't span all 'copying'. My confusion is where the limits are.
I try to be a righteous man, but the touchy and somewhat fluffy aspect of 'copyright' has become something of an obstacle in the sense that: why get involved in code that you might be prohibited in using at a later time?
If the books on programming doesn't implicitly set the example-code in the open (unless strictly expressed otherwise), they are more or less useless. Is there guide-lines anywhere, where I can get a clear idea of how far I can go? Microsoft uses a "considerable reworked" term for the use of some of their example-code ..
that's probably as close as you get to a fair balance. But the microsoft way is in many respects not a standard that rules everywhere. Most open-source code has copyright-markings ... is that to be understood, that code that has not is 'fair game'?
It's a touchy subject. If for nothing else, then for the fact that computers does only one thing profoundly well: read & write, copy & paste ..
they have to explicitly say "I am placing this in the public domain"