C# has structs (expanded classes) and can box them to pass as a reference to System.Object or an interface, but they're kind of brain-damaged (no default ctor) and you have to copy and paste any type you want to use both by reference and by value, since neither the class nor the struct can inherit from the other.
Java makes you do it yourself (which a few convenience methods do), and other than simple string conversions, the common wrapper classes are useless--you have to choose some primitive type and unbox before you can even do math!
Ruby seems to always box anything other than nil, false, true, and fixnums. In Eiffel and C++ (and C# within limits) you can choose whether to store user-defined types by reference or value; the cost rarely matters but sometimes it's crucial.
Eiffel is a typically imperative OO language. It's not built on avoiding side effects, higher-order functions, lazy evaluation, or currying, which are hallmarks of modern functional languages.
Funny you should mention that. Eiffel's the only language I've seen that actually gets boxing right. Any class can be "expanded" when declared or even used, and then it's transparently handled by value instead of by reference.
Right, and it seems doable to me (though I haven't gotten far enough to try it). 4:1:1 D1 video takes 506 KB per frame, or 14.8 MB/s at 30 fps. A Maxtor 7200 RPM spec sheet says their drives can sustain 24~44 MB/s. As long as you have a few seconds' worth of write buffer (and a ton of space), you should be able to get away with occasional seeks to feed the encoder (which won't be getting through its input that quickly anyway).
Another option is to roll your own striping across two disks, and have the encoder block until the drive it needs is idle (because the recorder switched to the other). This is probably the only way to record while watching a show that hasn't been encoded yet (because two 15 MB/s streams will swamp one drive).
I've always assumed a PVR box should pretty much be dedicated, since the recorder may not play well with arbitrary apps.
This problem, the market ought to be able to solve. We should care enough about what happens that we'll reject the license until they find some way not to leave us SOL.
It's common to buy a bankrupt company's assets without acquiring the company as a whole and assuming their obligations. The buyer can issue new licenses to new customers, while the existing licensees are on their own--they have a contract with a corporation that's no longer doing business (though I'm not exactly sure how dissolution works).
Might want to rethink your examples. PGP has been ported to both the Amiga and the Atari. RSA, DH, and DSA take a lot of cycles but it's not as if the rest of the app is that complicated.
A software key sniffer is more vulnerable. Hardware versions are widely rumored to be seeing field use. Hell, ThinkGeek sells one, though it's too big to conceal easily.
"At least 30 days after PGP sends its email acknowledgement" is a bit worrying, since they haven't committed to ever acknowledge reports of weaknesses that aren't "serious". I have great respect for Zimmerman, but any corporation is required to act in the interests of its shareholders....
The proper measure is the cost of a suitable substitute to a rational buyer. A GM car is highly substitutable for a BMW; I'm sure BMW's policies would be much worse if you had to burn down your garage and move in order to drive anything else.
I don't see how you could use a Libretto without sitting down or at least parking it on a table, with or without a Wacom tablet (which doesn't seem like it would even fit in your lap). A tablet is more like a palmtop that isn't so painfully tiny.
Linux support depends entirely on how well documented each vendor's hardware is, just like laptops. And a bigger screen is a feature if you're going to handwrite or draw on it!
I imagine you could get an injunction requiring them to stop publishing it. Unless you registered your copyright you could only sue for actual damages, which are probably nil.
No amount of skill will change the fact that a sheet of paper can only be in one place, and that you have to read everything nearby to find any phrase.
Arguably they've lost it, but not permanently. You're off the hook for previous infringement, but as soon as they notify you, you're liable from then on.
the right to exclude others from making, using, offering for sale or selling the invention throughout the United States or importing the invention into the United States
so in theory if neither you nor Ford licensed the patent, they're liable for direct infringement when they produced the car and you're liable for direct infringement (and Ford is liable for contributory infringement) every time you drive it. In practice, GM could never afford to go after every Ford owner, and they'd be allowed to demand damages and a license fee from Ford but probably not a recall of all infringing cars.
The intent of posting to Usenet is clearly to make a copy of the article available on every server carrying those groups, so it implies you're granting every newsadmin a license to arrange that. The intent of sending email is only to reach the recipients, so the implied license is only for their ISPs (and any relays between).
Posting email is very controversial, and I wouldn't count on getting away with it beyond fair use of the text.
Slashdot Mirror
Java makes you do it yourself (which a few convenience methods do), and other than simple string conversions, the common wrapper classes are useless--you have to choose some primitive type and unbox before you can even do math!
Ruby seems to always box anything other than nil, false, true, and fixnums. In Eiffel and C++ (and C# within limits) you can choose whether to store user-defined types by reference or value; the cost rarely matters but sometimes it's crucial.
Eiffel is a typically imperative OO language. It's not built on avoiding side effects, higher-order functions, lazy evaluation, or currying, which are hallmarks of modern functional languages.
Funny you should mention that. Eiffel's the only language I've seen that actually gets boxing right. Any class can be "expanded" when declared or even used, and then it's transparently handled by value instead of by reference.
Sorry, I'd honestly forgotten the ST was not Atari's first home computer.
Another option is to roll your own striping across two disks, and have the encoder block until the drive it needs is idle (because the recorder switched to the other). This is probably the only way to record while watching a show that hasn't been encoded yet (because two 15 MB/s streams will swamp one drive).
I've always assumed a PVR box should pretty much be dedicated, since the recorder may not play well with arbitrary apps.
This problem, the market ought to be able to solve. We should care enough about what happens that we'll reject the license until they find some way not to leave us SOL.
It's common to buy a bankrupt company's assets without acquiring the company as a whole and assuming their obligations. The buyer can issue new licenses to new customers, while the existing licensees are on their own--they have a contract with a corporation that's no longer doing business (though I'm not exactly sure how dissolution works).
That would be Indeo. I found some claims that QuickTime support for it is available on Win32 and MacOS, but haven't investigated.
Might want to rethink your examples. PGP has been ported to both the Amiga and the Atari. RSA, DH, and DSA take a lot of cycles but it's not as if the rest of the app is that complicated.
A software key sniffer is more vulnerable. Hardware versions are widely rumored to be seeing field use. Hell, ThinkGeek sells one, though it's too big to conceal easily.
"At least 30 days after PGP sends its email acknowledgement" is a bit worrying, since they haven't committed to ever acknowledge reports of weaknesses that aren't "serious". I have great respect for Zimmerman, but any corporation is required to act in the interests of its shareholders....
The proper measure is the cost of a suitable substitute to a rational buyer. A GM car is highly substitutable for a BMW; I'm sure BMW's policies would be much worse if you had to burn down your garage and move in order to drive anything else.
Linux support depends entirely on how well documented each vendor's hardware is, just like laptops. And a bigger screen is a feature if you're going to handwrite or draw on it!
I imagine you could get an injunction requiring them to stop publishing it. Unless you registered your copyright you could only sue for actual damages, which are probably nil.
I'd argue that thinking the script version probably worked isn't a good enough reason to make the reliable version unavailable.
I don't get it. Why give every app have a half-assed window manager with its own quirky UI rather than making the system window manager usable?
IMHO documents that completely rely on ECMAScript are inherently broken anyway.
No amount of skill will change the fact that a sheet of paper can only be in one place, and that you have to read everything nearby to find any phrase.
Arguably they've lost it, but not permanently. You're off the hook for previous infringement, but as soon as they notify you, you're liable from then on.
A US patent grants
so in theory if neither you nor Ford licensed the patent, they're liable for direct infringement when they produced the car and you're liable for direct infringement (and Ford is liable for contributory infringement) every time you drive it. In practice, GM could never afford to go after every Ford owner, and they'd be allowed to demand damages and a license fee from Ford but probably not a recall of all infringing cars.They'll probably claim that they aren't spammers and that their "legitimate business" is being defamed, and sue for libel.
Posting email is very controversial, and I wouldn't count on getting away with it beyond fair use of the text.
Nothing you requested can ever be spam (the content doesn't enter into it).