Yes, but what about the unlink system call? rm is just the most common way to invoke it, not the only way. I see this problem all the time in Windows; Explorer is about the only app that places files in the Recycle bin, so files deleted by other apps are unrecoverable. Not good. At least under Windows there's a system call to move a file to the Recycle bin, so a properly coded app can do what a naive user would expect. I'm not about to recode all my POSIX apps to use "system(rm...)" instead of unlink().
He cited the history of Unix, which has been replete with incompatible versions
As opposed to the history of Microsoft Windows, which has been replete with incompatible versions:-). We don't need "Bob's Win32" (is that related to Microsoft Bob?) because MS can't maintain compatibility even between currently shipping versions of the platform, never mind forward or backwards compatibility.
Why not use operator overloading? Overloading operator -> for a Handle class (probably a template class) fixes that problem quite cleanly. It also makes porting to other platforms easier (and let's face it, Mac handles were a hack dating back to the 128K days). I always wanted to do that when I was programming on the Mac, but at the time there wasn't a good C++ compiler available.
My mailbox and those of four neighbors were recently crashed into by an SUV. Pretty impressive, 4x4 posts splintered like matchsticks!
Not exactly a DoS attack - we got hand delivery to the door for a while. (Special delivery of junkmail - oh boy!)
I put the new box next to the telephone pole for protection - makes a good 'firewall':-)
In one sense, links don't really exist. What is a link in an HTML document, after all? It's just text. It's not a link until it's interpreted and rendered as such by a browser. So one could reasonably argue that there is no legal difference between a link and a simple textual representation of the url (http://slashdot.org). I just wrote both of those, and it's not my fault, nor/.'s, that when you view this using certain software the <a> tag is represented as something you can select to view another document. After all, if you use telnet as your web browser it won't do that. So I think that any attempts to restrict linking (under U.S. law) are in violation of the First Amendment, because links are just text.
I suggest someone at Adobe look up the difference between "can" and "may" in a dictionary.
"This book cannot be lent or given to someone else"
It most certainly can be! Perhaps it may not be done legally, but that's not the same.
In other words, this list of 'permissions' is little more than a list of false statements.
-A language pedant
Slashdot Mirror
The Death of Rats ... and other small furry creatures whose lives end in a truncated squeak :)
I bought my copy from the Science Fiction Book Club for $12.50 + S/H. Didn't want to wait any longer than necessary just to get the Josh Kirby cover.
Yes, but what about the unlink system call? rm is just the most common way to invoke it, not the only way. I see this problem all the time in Windows; Explorer is about the only app that places files in the Recycle bin, so files deleted by other apps are unrecoverable. Not good. At least under Windows there's a system call to move a file to the Recycle bin, so a properly coded app can do what a naive user would expect. I'm not about to recode all my POSIX apps to use "system(rm...)" instead of unlink().
Not bad getting two jokes for one, though
Or was that one joke with a hole punched in it?
Nah, I want Blake's 7 back.
He cited the history of Unix, which has been replete with incompatible versions
As opposed to the history of Microsoft Windows, which has been replete with incompatible versionsEver hear of a chap by the name of Aristotle?
Why not use operator overloading? Overloading operator -> for a Handle class (probably a template class) fixes that problem quite cleanly. It also makes porting to other platforms easier (and let's face it, Mac handles were a hack dating back to the 128K days). I always wanted to do that when I was programming on the Mac, but at the time there wasn't a good C++ compiler available.
My mailbox and those of four neighbors were recently crashed into by an SUV. Pretty impressive, 4x4 posts splintered like matchsticks! :-)
Not exactly a DoS attack - we got hand delivery to the door for a while. (Special delivery of junkmail - oh boy!)
I put the new box next to the telephone pole for protection - makes a good 'firewall'
In one sense, links don't really exist. What is a link in an HTML document, after all? It's just text. It's not a link until it's interpreted and rendered as such by a browser. So one could reasonably argue that there is no legal difference between a link and a simple textual representation of the url (http://slashdot.org). I just wrote both of those, and it's not my fault, nor /.'s, that when you view this using certain software the <a> tag is represented as something you can select to view another document. After all, if you use telnet as your web browser it won't do that.
So I think that any attempts to restrict linking (under U.S. law) are in violation of the First Amendment, because links are just text.
In other words, this list of 'permissions' is little more than a list of false statements.
-A language pedant
A red DNS server? What does the colour have to do with it?
I think you mean rogue.
The first born child, of course.
The corollary is that sending email to your doctor will cost you an arm and a leg.
A full Discworld bibliography is at http://www.colin-smythe.com/authors/tp/titles/nove ls.htm
Much more is at http://www.lspace.org/