Re:Why are you only using even-numbered releases?
on
GCC 3.4.0 Released
·
· Score: 1
But we've broken bincompat more often than that. And he asks about "3.6" when 3.5 hasn't even forked yet.
Re:Why are you only using even-numbered releases?
on
GCC 3.4.0 Released
·
· Score: 1
Ah, didn't know that. I'm a KDE guy.:-)
Why are you only using even-numbered releases?
on
GCC 3.4.0 Released
·
· Score: 1
The even==stable, odd==development pattern is only used by the Linux kernel. (And smaller projects that choose to imitate them.) No other major open source effort does the same thing, because every project manages its time differently.
Stroustrup is on record many times over as saying that link compatibility with some existing language was a design criterion for him. If not C, then something else.
It is an axiom in the C++ community that compatibility with C is both C++'s greatest strength and its greatest weakness.
With this compiler and the USFW annoucement, you can now take the *nix stuff and port it pretty easily and for free to Windows. No more need to assemble tools, install Cygwin or the like.
So, no more need to install precompiled and tested binaries, you can now port the exact same code (where did you plan on getting it?) by hand yourself and find a whole new set of bugs. Yeah, brilliant. Oh, you say you weren't going to use the GNU code? Great, yet another weird variant of coreutils.
Installing Cygwin is hardly a chore. I click setup.exe, tell it what to get, and walk away.
If you don't like the restrictions that come with the POSIX-layer DLL, then install MinGW instead. Same tools, same source code, same GNU extensions that we're already used to, no cygwin1.dll.
There used to be a barrier to getting *nix stuff to Windows.
You're either smoking crack or you haven't actually tried installing Cygwin in the last three years. I regularly run xterms under XP's own window manager, integrated clipboards, latest builds of just about everything. If you claim *nix stuff has been "missing," then you clearly haven't tried looking.
Indeed. RH donates a lot of time, effort, hardware, and bandwidth to the community (gcc.gnu.org, sources.redhat.com, cygwin.com, sourceware.org, etc, are all the same machine). We get far better results from them than we do/would from the FSF equivalent. RMS doesn't like to admit or believe this.
There are two reasons this decision is somewhat controversial for those of us maintaining FSF-related projects:
The decisions are made in a closed environment.
The Savannah admins have not demonstrated sufficient competence nor responsiveness. (Not meant to be a personal attack; I think they only have a few part-time volunteers.)
For example, GCC is under constant pressure by RMS to move from its own server (that happens to be hosted at Red Hat) and onto Savannah. But this pressure has been resisted for the same reasons, and it will continue to be resisted regardless of what "packaged development environment" Savannah is using.
With regard to the pair above, (1) the GCC maintainers have never been invited to share their concerns with the Savannah maintainers; when they speak up, they're ignored, and (2) Savannah gets fscked up on a regular basis, and complaints are ignored. For example, Savannah is supposed to be mirroring the GCC CVS repository, but it falls over constantly, leading to even higher load on the GCC servers as users switch over. The Savannah team has a long long way to go if they want to hold themselves up as a reliable open development site.
I'm diabetic. Type I, juvenile onset. I have less insulin produced in my body than that damn mouse has in its whole life. Yet the lack of a working pancreas will reduce my lifespan, not extend it. Certainly not to 130-odd years.
And I definitely won't get to snuggle up to Leia "just to keep warm".
is to realize that offshoring isn't done for the sake of offshoring. Offshoring -- and all the other labor practices that we don't like -- is done to not create additional full-time jobs in America. And avoiding that is done for exactly one reason: the absurd and unpredictable costs of health insurance.
The relative costs of insurance, worker's comp, etc, as part of a low- to middle-wage worker are way high. Of course a large company is going to do anything they can to avoid hiring more people.
Fix that, and the rest will follow. (Famous last words.)
The Great Worm, in its day, took down a far larger percentage of the Internet than ILOVEYOU or any of its ilk. We clamour for something to be done to those authors, who clearly have caused billions of dollars of loss, but look on older crackers with these weird rose-colored eyeglasses.
Read spaf's published analysis of the Great Worm sometime. (It was written a few days after the event.) The maliciousness was all there; fortunately, RTM was half-incompetent. Chunks of the code didn't even work and it still wiped out most of the net.
We know why Teela wanted to lose the fight. It was explained oerfectly well in Engineers. You know, when it actually happened.
Why do successful series always feel the need to go insert unneeded stories in the "gaps" between the same stories that made them successful? We don't need a day-to-day diary.
Following the events of Teela's children would be interesting, though.
Unfortunately, the makefile creator most people use, automake, creates only recursive makefiles.
And there's a damn good reason for it, too, but that's neither here nor there. Anyhow, this was fixed so you can do non-recursive stuff if you want to now.
Unfortunately, the very latest automake versions are trying to be way, way too clever, thereby breaking stuff in lots of projects. Time to throw it out and use something else.
I wouldn't mind seeing M4 go away, for one.
Automake is a Perl script. It doesn't use M4. (Using M4 would make it more readable, ha.) You're thinking of autoconf.
The BBC disagrees with you, insanely enough. The line of New Adventures books was headed in a more adult direction, where "adult" usually meant the way !America means in, in the sense of sophisticated and not childish, but occasionally got into "adult" territory, in the American sense of "adult," meaning pr0n.
I read a smattering of the NA books before their quality nosedived. When I read, for example, a scene in which one of the incidental extra characters, a part-time prostitute, was chewing pistachios "because they helped to take the semen taste out of her mouth," I was surprised, but not offended.
Others were, and complained to the BBC, who pointed out to the series editors that after all this time, the show -- and its spinoff books -- was still technically categorized as a children's series, and there aren't any plans to change that, so kindly stop having Ace telling people to fuck off, and leave the more "adult" scenes on the drafting table, thanks.
(By the way, the special effects weren't cheesy deliberately, "because the show was for children". The Beeb knew very well that grownups were a far larger percentage of its audience, even before Hartnell left the series. The effects were cheesy because that's all they had money for.)
In every science-fiction novel or short story I've ever read involving a tenth planet, the name was Persephone. There's a long-standing convention that will be horked up by NASA if this thing qualifies as a planet.
This wouldn't replace SMTP, it would just be a layer on top.
This "simple yet elegant" layer would require far more work than the underlying SMTP servers do. How exactly -- no handwaving, no fluff -- do you propose to implement this? You need to either tie bank account details to email account information, or maintain a separate "online only" bank. You need to find some unforagable, unbreakable, untappable method of identifying individual emails to make your one penny claim. You need to retrofit all existing mail clients to keep track of this new header (because Message-IDs can be forged).
This scheme is gigantic and unworkable. Prove me wrong, with details.
Anybody have a better idea? I didn't think so.:)
Whatever, kid. A little more cluefulness and a little less arrogance next time, and perhaps your "simple" idea will make it further than slashdot.
Explained in the last DSPAM /. story
on
DSPAM v2.10 Released
·
· Score: 4, Insightful
except that my article history is truncated in a futile attempt to get me to subscribe. So I can't point to the writeup I did.
The increased accuracy comes from the emails that will slip under your mental radar. You are a human, and you make mistakes. You wouldn't deliberately choose to read the email, but one day the subject line looks plausible, and so you bring it up. Three-quarters of a second later, you're glaring at the monitor and hitting "delete", but DSPAM wouldn't have let that slip by in the first place.
...over at livejournal. They would have given you warning, I'm sure! Spirit's is here and little sister Opportunity's is here. They link to the blogs of other space probes and sats as well, including the Voyagers (who don't say much).
Yes, I mean the rovers' blogs, not the rovers' engineers' blogs.
Slashdot Mirror
But we've broken bincompat more often than that. And he asks about "3.6" when 3.5 hasn't even forked yet.
Ah, didn't know that. I'm a KDE guy.
The even==stable, odd==development pattern is only used by the Linux kernel. (And smaller projects that choose to imitate them.) No other major open source effort does the same thing, because every project manages its time differently.
...if it's true that D has removed "archaic" (*snort*) things like forward declarations.
What, exactly, did they think a header file consists of?
Stroustrup is on record many times over as saying that link compatibility with some existing language was a design criterion for him. If not C, then something else.
It is an axiom in the C++ community that compatibility with C is both C++'s greatest strength and its greatest weakness.
So, no more need to install precompiled and tested binaries, you can now port the exact same code (where did you plan on getting it?) by hand yourself and find a whole new set of bugs. Yeah, brilliant. Oh, you say you weren't going to use the GNU code? Great, yet another weird variant of coreutils.
Installing Cygwin is hardly a chore. I click setup.exe, tell it what to get, and walk away.
If you don't like the restrictions that come with the POSIX-layer DLL, then install MinGW instead. Same tools, same source code, same GNU extensions that we're already used to, no cygwin1.dll.
You're either smoking crack or you haven't actually tried installing Cygwin in the last three years. I regularly run xterms under XP's own window manager, integrated clipboards, latest builds of just about everything. If you claim *nix stuff has been "missing," then you clearly haven't tried looking.
Indeed. RH donates a lot of time, effort, hardware, and bandwidth to the community (gcc.gnu.org, sources.redhat.com, cygwin.com, sourceware.org, etc, are all the same machine). We get far better results from them than we do/would from the FSF equivalent. RMS doesn't like to admit or believe this.
There are two reasons this decision is somewhat controversial for those of us maintaining FSF-related projects:
For example, GCC is under constant pressure by RMS to move from its own server (that happens to be hosted at Red Hat) and onto Savannah. But this pressure has been resisted for the same reasons, and it will continue to be resisted regardless of what "packaged development environment" Savannah is using.
With regard to the pair above, (1) the GCC maintainers have never been invited to share their concerns with the Savannah maintainers; when they speak up, they're ignored, and (2) Savannah gets fscked up on a regular basis, and complaints are ignored. For example, Savannah is supposed to be mirroring the GCC CVS repository, but it falls over constantly, leading to even higher load on the GCC servers as users switch over. The Savannah team has a long long way to go if they want to hold themselves up as a reliable open development site.
I'm diabetic. Type I, juvenile onset. I have less insulin produced in my body than that damn mouse has in its whole life. Yet the lack of a working pancreas will reduce my lifespan, not extend it. Certainly not to 130-odd years.
And I definitely won't get to snuggle up to Leia "just to keep warm".
Dammit, I wanna be a lab mouse when I grow up.
is to realize that offshoring isn't done for the sake of offshoring. Offshoring -- and all the other labor practices that we don't like -- is done to not create additional full-time jobs in America. And avoiding that is done for exactly one reason: the absurd and unpredictable costs of health insurance.
The relative costs of insurance, worker's comp, etc, as part of a low- to middle-wage worker are way high. Of course a large company is going to do anything they can to avoid hiring more people.
Fix that, and the rest will follow. (Famous last words.)
The Great Worm, in its day, took down a far larger percentage of the Internet than ILOVEYOU or any of its ilk. We clamour for something to be done to those authors, who clearly have caused billions of dollars of loss, but look on older crackers with these weird rose-colored eyeglasses.
Read spaf's published analysis of the Great Worm sometime. (It was written a few days after the event.) The maliciousness was all there; fortunately, RTM was half-incompetent. Chunks of the code didn't even work and it still wiped out most of the net.
Louis looks in his early twenties, as noted by Nessus.
Speaker-to-Animals is his title. He's a junior ambassador to the human worlds.
Teela is 20. Dark hair. Slender. Looks like Paula Cerenkov. :-)
Nah, as long as it involves bullets hitting spammers, I can adjust.
We know why Teela wanted to lose the fight. It was explained oerfectly well in Engineers. You know, when it actually happened.
Why do successful series always feel the need to go insert unneeded stories in the "gaps" between the same stories that made them successful? We don't need a day-to-day diary.
Following the events of Teela's children would be interesting, though.
I ignore any proposed solution to spam that does not consist of the simple phrase:
Now, if even .5% of spammers had their walls decorated with their own brains, that would cut down on bandwidth wastage.
And there's a damn good reason for it, too, but that's neither here nor there. Anyhow, this was fixed so you can do non-recursive stuff if you want to now.
Unfortunately, the very latest automake versions are trying to be way, way too clever, thereby breaking stuff in lots of projects. Time to throw it out and use something else.
Automake is a Perl script. It doesn't use M4. (Using M4 would make it more readable, ha.) You're thinking of autoconf.
Pity that "breaking text into paragraphs" isn't one of them.
(Cheap shot, sorry, couldn't resist, move along, nothing to see here.)
I said I'd be "a little suspicious," not "telepathic."
Of course customs can be fooled. Duh.
...I'd be a little suspicious when looking at a keyboard with a dollar sign instead of a pounds sign, American punctuation layout, etc, etc.
Pity "export LANG=en_GB" doesn't affect the hardware. :-)
The BBC disagrees with you, insanely enough. The line of New Adventures books was headed in a more adult direction, where "adult" usually meant the way !America means in, in the sense of sophisticated and not childish, but occasionally got into "adult" territory, in the American sense of "adult," meaning pr0n.
I read a smattering of the NA books before their quality nosedived. When I read, for example, a scene in which one of the incidental extra characters, a part-time prostitute, was chewing pistachios "because they helped to take the semen taste out of her mouth," I was surprised, but not offended.
Others were, and complained to the BBC, who pointed out to the series editors that after all this time, the show -- and its spinoff books -- was still technically categorized as a children's series, and there aren't any plans to change that, so kindly stop having Ace telling people to fuck off, and leave the more "adult" scenes on the drafting table, thanks.
(By the way, the special effects weren't cheesy deliberately, "because the show was for children". The Beeb knew very well that grownups were a far larger percentage of its audience, even before Hartnell left the series. The effects were cheesy because that's all they had money for.)
I've never claimed that "nothing can be done," so I'll thank you to stop putting words in my mouth. I simply think that this proposal is not workable.
You, at least, made a good argument for it. And avoided the handwaving, which makes for a nice change on /.
In every science-fiction novel or short story I've ever read involving a tenth planet, the name was Persephone. There's a long-standing convention that will be horked up by NASA if this thing qualifies as a planet.
Fortunately, it probably won't. *whew*
This "simple yet elegant" layer would require far more work than the underlying SMTP servers do. How exactly -- no handwaving, no fluff -- do you propose to implement this? You need to either tie bank account details to email account information, or maintain a separate "online only" bank. You need to find some unforagable, unbreakable, untappable method of identifying individual emails to make your one penny claim. You need to retrofit all existing mail clients to keep track of this new header (because Message-IDs can be forged).
This scheme is gigantic and unworkable. Prove me wrong, with details.
Whatever, kid. A little more cluefulness and a little less arrogance next time, and perhaps your "simple" idea will make it further than slashdot.
except that my article history is truncated in a futile attempt to get me to subscribe. So I can't point to the writeup I did.
The increased accuracy comes from the emails that will slip under your mental radar. You are a human, and you make mistakes. You wouldn't deliberately choose to read the email, but one day the subject line looks plausible, and so you bring it up. Three-quarters of a second later, you're glaring at the monitor and hitting "delete", but DSPAM wouldn't have let that slip by in the first place.
...over at livejournal. They would have given you warning, I'm sure! Spirit's is here and little sister Opportunity's is here. They link to the blogs of other space probes and sats as well, including the Voyagers (who don't say much).
Yes, I mean the rovers' blogs, not the rovers' engineers' blogs.