Opererator overloading is great for generics. Because then stuff can work on built-ins and user defined types the same. Because operator(const T &, const T&), and so on, all without writing two versions of each template.
casting containers of derived to containers of base is bad. here's why:
class Animal {};
class Aardwolf: public Animal {};
class Whale : public Animal { public: void Swim();};
The way I see it, the tax laws should encourage companies to pay dividends, because dividends directly ground the stock market in reality. Without them, there are like 6 layers of economic indirection between businesses making money and their stock value, which indirection enables bigger bubbles and shadier accounting.
That's why we use parsers to write compilers and not regexps
Actually compilation typically involves two stages - tokenization and parsing. Tokenization is where the compiler realizes that 66 is an int and printf is an identifier and "\011unix\010" is a string. This frees the parser to worry about the upper level structure, such as whether x = (4; means anything.
Generally the tokenizer is implemented as a regular expression parser, and the 'higher level' parsing uses some context free language parsing technique (table or recursive descent or whatever)
The reason is that the number of tokens is a lot less than the number of bytes in the file and regexps are a lot easier to parse than context free grammars.
Comment stripping (and also literal parsing) is in the tokenizing stage, which is why c doesn't allow nested comments - it's impossible to ensure that arbitrary numbers of/*'s and */'s match with a regexp.
Having worked with the QuickTime for Windows APIs I find this especially hilarious. When Apple ported QuickTime to Windows they basically just wrapped up the Windows objects in Mac objects. So you have to talk about PixMaps and GWorlds and UPP's and Events and Task functions. So now you're wrapping THAT up and sticking it on Linux.
There is a skin for WMP9 that looks like WMP6.4. It's called "classic" (NOT "windows classic"). If you also go to the configuration screen and deselecting "display anchor window when in skin mode" from the Player tab, it's pretty similar, UI-wise. But you have to go to some ugly mode for playlist support.
Imagine, for a minute, you're a language design guru. You got hired for those skills, and it's what you like doing. Should your employer ask you to a) design languages, b) specialize in security and reliability and rework existing products to use your newly learned knowledge?
Should Microsoft stop all other products and assign all their engineers to making windows Robust? Even if it DID help make windows more robust, it would be a really stupid business decision to focus exclusively on a single task.
Re:It's good that rewrites are hard to justify!
on
Justifying Code Rewrites?
·
· Score: 2, Insightful
Gee, it only took them like 5 years. Could they have made Netscape better in 5 years without starting over from scratch, during which time they lost the browser war and were acquired by AOL? Is Netscape, as a company, successfull?
Quay is typable with only the left hand on a Dvorak keyboard. So is pope, pupae, pike, and (probably) others. Note that the calculator on that page is not very good - it is unable to say 100% for "same hand". Try typing the word "i" for an example. I'm not saying whether QWERTY is better, just that your facts are wrong.
The RAMDAC is only the part of the card which converts a digital signal to an analog VGA signal. A few extra megahertz here means that the card can output a higher resolution. This is not what anyone cares about, it's the GPU clock frequency (well, that and the memory clock) which probably you meant to refer to.
I've found that correlation actually causes causation. Just think about it. Almost every time two things have a causal relationship, there's a correlation between them!
Actually the scrollwheel is typically implemented in hardware as sending button 4 and 5 clicks for scrolling down and up. Probably your extra buttons are 6 and 7.:D
I used to work at Colorspan, a manufacturer of high end wide format color printers. Their target market was Kinkos and similar customers, since their printers cost upwards of $30,000. But all of their printers actually did have little CCD cameras for calibration. I even wrote some of the software to do it too.
So MSDOS 1.0 didn't support directories at all. By the time MSDOS 2.0 came around, there was already an existing application base that used / as an option prefix (like - under unix!) and so they chose \ to separate directories so they could tell options from filenames, without breaking all the existing programs.
md and dir are totally just "if you know it you know it, if you don't know it, you probably won't guess it", just like ls and mkdir.
Slashdot Mirror
Opererator overloading is great for generics. Because then stuff can work on built-ins and user defined types the same. Because operator(const T &, const T&), and so on, all without writing two versions of each template.
casting containers of derived to containers of base is bad. here's why:
;
// No compiler error; Aardwolves ARE animals // Aardwolves can't swim!!!
class Animal {};
class Aardwolf: public Animal {};
class Whale : public Animal { public: void Swim();};
vector<Whale> vWhales;
vWhales.push_back(Aardwolf());
// Error, Aardwolves aren't whales!
((vector<Animal>)(vWhales)).push_back(Aardwolf())
vWhales.back().Swim();
Yes, it's three times as toxic as table salt!
The way I see it, the tax laws should encourage companies to pay dividends, because dividends directly ground the stock market in reality. Without them, there are like 6 layers of economic indirection between businesses making money and their stock value, which indirection enables bigger bubbles and shadier accounting.
That's why we use parsers to write compilers and not regexps
/*'s and */'s match with a regexp.
Actually compilation typically involves two stages - tokenization and parsing. Tokenization is where the compiler realizes that 66 is an int and printf is an identifier and "\011unix\010" is a string. This frees the parser to worry about the upper level structure, such as whether x = (4; means anything.
Generally the tokenizer is implemented as a regular expression parser, and the 'higher level' parsing uses some context free language parsing technique (table or recursive descent or whatever)
The reason is that the number of tokens is a lot less than the number of bytes in the file and regexps are a lot easier to parse than context free grammars.
Comment stripping (and also literal parsing) is in the tokenizing stage, which is why c doesn't allow nested comments - it's impossible to ensure that arbitrary numbers of
World Wildlife Entertainment, I think.
it uses WINE to run the Windows quicktime codecs
Having worked with the QuickTime for Windows APIs I find this especially hilarious. When Apple ported QuickTime to Windows they basically just wrapped up the Windows objects in Mac objects. So you have to talk about PixMaps and GWorlds and UPP's and Events and Task functions. So now you're wrapping THAT up and sticking it on Linux.
How hideous.
Chairface wrote some of his name on the moon
There is a skin for WMP9 that looks like WMP6.4. It's called "classic" (NOT "windows classic"). If you also go to the configuration screen and deselecting "display anchor window when in skin mode" from the Player tab, it's pretty similar, UI-wise. But you have to go to some ugly mode for playlist support.
Imagine, for a minute, you're a language design guru. You got hired for those skills, and it's what you like doing. Should your employer ask you to a) design languages, b) specialize in security and reliability and rework existing products to use your newly learned knowledge?
Should Microsoft stop all other products and assign all their engineers to making windows Robust? Even if it DID help make windows more robust, it would be a really stupid business decision to focus exclusively on a single task.
Your search - "world wide web" - did not match any documents. 0 pages searched in 6.31 seconds.
Those are the standard trolls.
That post isn't getting you laid.
Gee, it only took them like 5 years. Could they have made Netscape better in 5 years without starting over from scratch, during which time they lost the browser war and were acquired by AOL? Is Netscape, as a company, successfull?
I would say the answer is no.
Quay is typable with only the left hand on a Dvorak keyboard. So is pope, pupae, pike, and (probably) others. Note that the calculator on that page is not very good - it is unable to say 100% for "same hand". Try typing the word "i" for an example. I'm not saying whether QWERTY is better, just that your facts are wrong.
The RAMDAC is only the part of the card which converts a digital signal to an analog VGA signal. A few extra megahertz here means that the card can output a higher resolution. This is not what anyone cares about, it's the GPU clock frequency (well, that and the memory clock) which probably you meant to refer to.
They should be allowed to do all kinds of dishonest and scuzzy things.
That doesn't mean they should do them.
no no, it's "a whole nother Dakota"
I've found that correlation actually causes causation. Just think about it. Almost every time two things have a causal relationship, there's a correlation between them!
I still haven't forgiven him for Ken's Labyrinth.
Actually the scrollwheel is typically implemented in hardware as sending button 4 and 5 clicks for scrolling down and up. Probably your extra buttons are 6 and 7. :D
I used to work at Colorspan, a manufacturer of high end wide format color printers. Their target market was Kinkos and similar customers, since their printers cost upwards of $30,000. But all of their printers actually did have little CCD cameras for calibration. I even wrote some of the software to do it too.
Also holds true for cheese. Or underarm deoderant.
So MSDOS 1.0 didn't support directories at all. By the time MSDOS 2.0 came around, there was already an existing application base that used / as an option prefix (like - under unix!) and so they chose \ to separate directories so they could tell options from filenames, without breaking all the existing programs.
md and dir are totally just "if you know it you know it, if you don't know it, you probably won't guess it", just like ls and mkdir.
Cost of damages and strenght of earthquake aren't linearly related I'm pretty sure.