He's just making a single copy for archival purposes--or taking a quote from the whole work (which would be the entire software package) for critique. Surely that falls under fair use.
Actually, Deep Blue was most likely over-optimized for Kasparov, and got even more so during their match. It hasn't done too well when it's competed against other computers. It's unlikely it would do well against any other GM.
Please, for the love of Pete, read Rapid Development. If you read, understandd and apply that book, you'll be head and shoulders above most project managers.
The settlement reached would allow Audiogalaxy to operate a "filter-in" system, which requires that for any music available, the songwriter, music publisher,
and/or recording company must first consent to the use and sharing of the work.
Note how they state that the recording company must always be the one to authorize the song. The musician and publisher never has the right without consend of the "recording company". What if there is no recording company?
Yes, C# brought the power of C. It's a shame it didn't bring the power of C++. MS made some bizarre choices with the language design. Look at GC vs. Dispose vs. using (object) {}. Look at System.Array vs. System.Collections.ArrayList.
Sigh. The only thing I've found that they got right is they used the regular expression syntax from Perl, instead of inventing their own problematic syntax.
You're right. The power of C# is in the IDE. It's a shame they crippled C++ (managed C++) for use in.Net.
There's no technological reason why every new car and truck in america isn't getting 50 MPG
You're full of crap. The single biggest contributor to low MPG is weight of the vehicle. Number of cylinders/displacement figures in there somewhere.
Unless of course you have documentation that proves me wrong? Otherwise, why aren't the auto makers making lower MPG vehicles? People would be buying them up like crazy. A 50 MPG SUV would get rid of the arguments the greens have against them.
Or do you believe in some auto-oil-cabal conspiracy theory?
by making all commercials fit into 30-second chunks. If commercials weren't a univeral size, it wouldn't be easy to skip them. Of course the networks standardized that to make it easier for them. I hit the mute button to make things easier for me--but would much rather hit the "skip this commercial" button.
An important issue about Crusade was that the project was terminated before the first episode even aired. I'm sure there's two sides to the story, but I could see the interference from the suits (I can't believe I just wrote that) when watching those 13 eps.
I'm aware of the boost libraries--scoped array is nothing more than a simple array which destroys itself. I often have to change the size of the arrays I allocate, making vector a better choice. You're right though that if my trivial example is all I need, then scoped_array would do the trick.
Yes, vector<bool> was a horrible mistake. That should be fixed in the next version of the standard. Where performance is important, use vector instead.
The STL makes no guarantees that it checks for errors (bounds checking, using a pointer into the wrong collection, etc.), and it is designed in such a way that error checking is quite costly. (Note that there have been a couple of attempts at making a safe STL; see here [horstmann.com]; it is unacceptable that this isn't part of the standard and isn't used by default).
Read The Design and Evolution of C++. You'll find that one of the major principles in C++ is that you shouldn't pay for any feature you don't use. Breaking that rule requires that the feature (1) adds value to all or nearly all C++ developers, and (2) it can't be done any other way. Hence we have (for example) virtual functions, but if you don't want to use them, you don't have to. The STL containers were designed the same way: hence std::vector has operator[] which has unchecked access, but also has at() which does do range checking.
Also, iterators are intended to represent meta-pointers. Should all pointer operations be checked? Say goodbye to performance.
It's hard to predict whether any particular data structure or algorithm is going to be fast. Sure, it makes asymptotic guarantees, but everybody does that; it's the constants that matter.
Profile, profile, profile.
The library is too complex for most needs, and you can't easily just use "a little bit" of it. If you want to write efficient code using STL, you have to understand it pretty well.
This is just plain wrong. I can simply use std::vector instead of arrays, and I don't ever have to worry about delete. Have you ever seen code like this?
char* buffer = new char[n]; //... delete [] buffer;
I meant to add that the std:: can be removed with "using" but I forgot. In our project we're migrating from classic streams (e.g., istream.h) to standard streams (e.g. istream), which makes it imperative to not sprinkle "using" directives around, especially in headers.
I've been happily using STL for about 3 years now. The biggest drawbacks (IMO) are:
Kitchen sink syndrome: There are a lot of features in STL, and to use some of them you need functors, etc. Sometimes it's just easier to read if you use a normal for loop instead of using for_each, etc.
verbose type syntax: When you use the containers, like (say) std::vector, you have to declare your iterators as:
std::vector<int>::iterator i;
If you change to a std::list container, you'll have to change your declarations. Of course, you can mitigate that by using typedefs, and then you only have to change the typedef, but it can still get a bit wordy.
unexpected results: Understand the difference between remove() and erase() in the containers.
The benefits of using STL are wonderful. If you write your custom containers/streams/etc. using the STL interface, you can seamlessly use the algorithms portion of the library.
I recommend reading the first part of Generic Programming and the STL. It'll help you undestand the thinking behind the design.
documents do not need to be tied to an application, but there will just be a unified (xml) document format
You do realize that OpenOffice/StarOffice/etc. uses an xml-based file format, right? It's one of the reasons I'm so excited about StarOffice being released so I can recommend it to everyone I know. At our company, I've mentioned how easy it would be to develop scripts to do search/replace across many files, etc. and it's got people very interested.
I'm a registered Republican in CA. The primaries are next Tuesday (Mar 5). I had just decided to vote for Jones (currently the Sec'y of State) in the primary, but this changed my mind. I don't exactly want a spammer as my next Governor. Good job nitwit. Sigh.
The sad part is that another Republican (Riordan) spammed my answering machine with a recorded message as to why he should be elected. I deleted the message as soon as I heard the name...
Slashdot Mirror
Patents are 20 years from filing date. Three years is typical for the time from filing to grant.
not virii, see http://www.perl.com/language/misc/virus.html.
Actually, Deep Blue was most likely over-optimized for Kasparov, and got even more so during their match. It hasn't done too well when it's competed against other computers. It's unlikely it would do well against any other GM.
Please, for the love of Pete, read Rapid Development . If you read, understandd and apply that book, you'll be head and shoulders above most project managers.
And don't forget Tron.
Yes, C# brought the power of C. It's a shame it didn't bring the power of C++. MS made some bizarre choices with the language design. Look at GC vs. Dispose vs. using (object) {}. Look at System.Array vs. System.Collections.ArrayList.
.Net.
Sigh. The only thing I've found that they got right is they used the regular expression syntax from Perl, instead of inventing their own problematic syntax.
You're right. The power of C# is in the IDE. It's a shame they crippled C++ (managed C++) for use in
They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.
Of course, at Best Buy, they'll tell you the sale was a mistake after you buy it, and charge you the full price...
Unless of course you have documentation that proves me wrong? Otherwise, why aren't the auto makers making lower MPG vehicles? People would be buying them up like crazy. A 50 MPG SUV would get rid of the arguments the greens have against them.
Or do you believe in some auto-oil-cabal conspiracy theory?
by making all commercials fit into 30-second chunks. If commercials weren't a univeral size, it wouldn't be easy to skip them. Of course the networks standardized that to make it easier for them. I hit the mute button to make things easier for me--but would much rather hit the "skip this commercial" button.
"viri" is not an English word. See What's the Plural of `Virus'?
An important issue about Crusade was that the project was terminated before the first episode even aired. I'm sure there's two sides to the story, but I could see the interference from the suits (I can't believe I just wrote that) when watching those 13 eps.
ObUseless Trivia:
Statler and Waldorf are their real names.
I'm aware of the boost libraries--scoped array is nothing more than a simple array which destroys itself. I often have to change the size of the arrays I allocate, making vector a better choice. You're right though that if my trivial example is all I need, then scoped_array would do the trick.
:)
Of course it's not in the standard....
Q: How many legs does a dog have if you call a tail a leg?
A: Four. Calling a tail a leg doesn't make it a leg.
You are trolling here. C++ is good language design, for reasonable different definitions of good.
Yes, vector<bool> was a horrible mistake. That should be fixed in the next version of the standard. Where performance is important, use vector instead.
Also, iterators are intended to represent meta-pointers. Should all pointer operations be checked? Say goodbye to performance.
Profile, profile, profile. This is just plain wrong. I can simply use std::vector instead of arrays, and I don't ever have to worry about delete. Have you ever seen code like this?Replace it with:Say goodbye to delete for dynamic arrays. That is a very legitimate issue. And one that I have little experience with.I meant to add that the std:: can be removed with "using" but I forgot. In our project we're migrating from classic streams (e.g., istream.h) to standard streams (e.g. istream), which makes it imperative to not sprinkle "using" directives around, especially in headers.
The benefits of using STL are wonderful. If you write your custom containers/streams/etc. using the STL interface, you can seamlessly use the algorithms portion of the library.
I recommend reading the first part of Generic Programming and the STL. It'll help you undestand the thinking behind the design.
Funny, Sun's site says April/May/June 2002. Which means June of course.
The sad part is that another Republican (Riordan) spammed my answering machine with a recorded message as to why he should be elected. I deleted the message as soon as I heard the name...