If there's a country which is both A) rich enough to have a good internet connection, and B) democratic enough so that the Prince or Swami or Vice Admiral fills out his own web forms when making his own reservations using said internet connection, then I'm moving.:-)
...is on their web form, when you're filling out the membership information, they don't have a radio-box selection for Mr/Miss/Mrs/Dr/etc. They just have a text field called "Saluation" and you can fill in whatever title you want.
So I plan to give them my preferred job title of Programmer-at-Arms. If I convince my girlfriend and fellow geek to join, I hope she'll choose something like Dangerous Felon[*] or Dictator For Life.
[*] Some friends and coworkers went to one of those job fairs where you can fill out "send me free magazines which are vaguely tech-related" cards, which also have fill-in-the-blank Title lines. One of them convinced his supervisor to use Dangerous Felon in the field, and apparently the guy still gets an occasional freebie magazine addressed to Dangerous Felon Joe Public (with Joe Public replaced by his real name).
A good implementation of generic containers keeps the actual work in a hidden, non-template class. The template class -- the one which gets duplicated over and over for your 15 different things -- simply forwards operations and storage to the hidden class. And if the forwarding is well-written, most/all of it can be inlined and otherwise optimized away. Voila -- 15 containers, all sharing code.
do they want to wait for a site owner to respond that it's okay to cache his page before posting the story?
Huh? Google doesn't have to get permission before caching. I don't have to get permission before keeping a copy in my local browser cache. Why should/.?
Also, if people are viewing the person's page on the cache, it's ripping off the site owner's banner ads revenues.
A very good point. I would expect a/.-cache to not rewrite those links into local caches. That way while the page is served up from slashdot, the banner ads are still being pinged from wherever. (I'm probably overlooking something.)
The idea behind the suggestion is that subscribers would be able to actually read the stories before the/. effect shuts down the affected sites.
A far, far easier way to avoid the/. effect is for/. to simply keep a local (local to/. and the andover colocs) cache of the page. Link to that instead of to the actual site. The/. network is set up for that much load; a home enthusiast's cable modem isn't.
Maybe replace the link-to-cache with the link-to-real after 24 hours, or a week, or whatever. There's probably lots of tweaking possible here that I haven't even thought of, much less posted. My point is that/. has the capability to shoulder some of those slashdottings, at least briefly.
You seem to assume that being a C++ evangelist means that one must be an open source evangelist as well.
His new position seems to be that MS should strive to make their compiler ISO-compliant. Great. Nowhere in the ISO C++ standard -- nowhere in all 768 pages -- does it say that the compiler must also be OSS-friendly.
Would it surprise you to learn that Microsoft employees occasionally contribute code to GCC, in order to help binary compatibility? Granted it's never going to be fully binary compatible, since the Visual C++ vtbl layout is patented, but POD structs can be.
"System and method for influencing a position on a search result list generated by a computer network search engine."
How is "give us money and we'll rank you higher" an original contribution to art and science? It reminds me of the feminist character at the frat party at the end of PCU, with the dawning realization, "You mean, if you're nice to [males], they bring you stuff?"
It's days like this, where I'm almost ready to write my Senator and try and take an active role, that I look at the decisions being made and say to myself, fuck it, we're too late.
Given the significant waterplane area and ample internal volume, which allows for greater battery storage, the Phoenix will out-perform smaller counterparts in surface speed, submerged speed and submerged endurance.
I can't express how embarassing it is to be lounging around the marina, get challenged to a submarine drag-race, and lose to some other 100-foot submersible because I didn't hook up enough batteries. Finally, with the Phoenix 1000, I'll never have to endure their laughter again!
That's something that both amuses me (when I'm feeling cynical) and scares me (when I'm feeling serious): that American citizens think this country is a democracy.
You said it every damn day in grade school, people:
I pledge allegiance to the flag of the United States of America, and to the republic for which it stands
That word isn't in there just to make patriotic songs have a better rhythm than "the democracy" would, ya'know.
A scene at Lothlorien, where Galadriel bestows upon each of the Fellowship a gift which will play an important role later in the Trilogy.
Since this wasn't in the theatrical release, I'm wondering how the presence of these items -- which do play an important (read, live-saving) role later in the book -- is going to be explained.
Is the audience expected to believe that the phial of Galadriel in Frodo's jacket just sort of appeared there? Or will the theatrical release of the next two films have an extra voice-over from Frodo, "Oh, hey, check out this shiny thing lying underneath a rock! I'll just keep this, who knows, maybe it'll be useful."
foot, meet bullet. bullet, meet foot
on
Spy v. Spy
·
· Score: 2
and browse the web.
And as soon as she reads your slashdot posts, your method is somewhat, er, compromised.:-)
Start at http://gcc.gnu.org/ and follow the link called "readings" or "further readings" or something like that. There should be one or more links to a C++ cross-vendor ABI spec.
Part of it is based on the System V gABI and psABI, and then there are some new things specifying cross-language name mangling and exception handling routines (e.g., a Java function calls a C++ function which calls an Ada function; the Ada function throws an Ada exception, which the Java function can catch as a Java exception.
C++ does really nasty things to class/function/method names when it compiles. And, on top of that, there's no standard for it.
First, the fact that different compilers use different name mangling (what you call "really nasty things") is a Good Thing. There are bigger differences between.o output than just the names; keeping the mangled names different means that you won't fall into any of the pitfalls resulting from those other differences. Magically making all the symbols the same will not let you magically link.o's/.so's/.a's from one compiler with code from another compiler.
Second, there is a standard ABI now. It was first implemented in 3.0, and 3.1 has some bugfixes for it. Other vendors are writing compilers to use the same ABI, which means that C++ can be cross-vendor-linked the same way as C.
I believe the original Command & Conquer[*] worker peons would finish a job, then look around for something to build/repair/harvest. The worker Imps in Dungeon Keeper have a priority list of things to do if you haven't assigned them anything (claim any unclaimed ground, reinforce any un-reinforced walls, scavenge dead bodies, etc).
Right now I have a hard time keeping track of my Citizens in Empire Earth because if something needs doing within their line of sight, they wander off and start working, and then I can't find them. (I have the most efficient, productive, confused society ever!)
[*] Made in the bad old days before Westwood could hire professional actors. I believe the man who plays the bad guy (Kane? Cain? sp?) works in the Westwood financial division or something. That's really cool.:-)
And I don't put my e-mail in public places where spammers would look to pick it up.
Such as web archives of mailing lists for opensource projects? It must be nice to sit there handing out advice and calling people idiots when you never contribute to the community.
Most of the spam I get is at an address harvested from mailing list archives for GCC, Doxygen, and few other much smaller projects. Does that mean I'm an idiot? If you think so, perhaps you shouldn't be using these programs (after all, an idiot has contributed to them).
Does that mean I'm going to stop sending mail to a public mailing list? No, because as much as I'd like to reduce the amount of spam I get, I'd much rather see improved software.
As far as I'm concerned if you get spammed, it's your fault. [...] But while spamming is still a problem, deal with it and don't be an idiot.
I believe it was some pesky bug in GCC 3.0 that caused KDE grief (well, plus the KDE coders were trying to to an end run around some of the C++ language rules). From what I can see GCC 3.1 is safe to use with KDE 3.0.
This is why major contributors to GCC who are also employed as a programmer must get a disclaimer signed by their employer, stating basically, "We don't really give a rat's ass about this work and promise not to try and hijack it in the future."
Without such protections, there wouldn't be much of g++ these days: the employer of the original author tried to make it a proprietary product once he was mostly done with it. Fortunately it was too late for them.
I wonder why the Perl folks don't require such protection of themselves.
Whether you write 500, 5000, or -2000 lines of code to solve the problem is irrelevent, since the code is only a means to an end.
Agreed. I think it was Dijkstra who argued that if Lines Of Code are counted, then the number should be viewed as a liability rather than an asset. That is, LOC are not something we produce, but something we spend.
Last holidays, I was given a copy of Things a Computer Scientist Rarely Talks About, a transcript of a series of six lectures by Knuth on the subject of religion. (Why six? "Because I could only think of six funny things to say for the lectures... and that was the first one.")
It's fascinating. Much of the lectures he talked about his 3:16 project, and the rest was an open Q&A session. Even if you're a hardcore atheist, you should pick up a copy; there's no preaching, and the audience discussion is far more insightful than the crap you're paying subscriptions for here on slashdot.
(Random bit of trivia from the book: for the project, Knuth used his own Bible translations. One of the lectures is mostly a "Bible-translate.HOWTO" commentary.)
Exchange is a proprietary IMAP server with window dressing, and marketed to make PHB's think they can't use Outlook's features without it.
Obviously you bought into that.
Slashdot Mirror
If there's a country which is both A) rich enough to have a good internet connection, and B) democratic enough so that the Prince or Swami or Vice Admiral fills out his own web forms when making his own reservations using said internet connection, then I'm moving.
...is on their web form, when you're filling out the membership information, they don't have a radio-box selection for Mr/Miss/Mrs/Dr/etc. They just have a text field called "Saluation" and you can fill in whatever title you want.
So I plan to give them my preferred job title of Programmer-at-Arms. If I convince my girlfriend and fellow geek to join, I hope she'll choose something like Dangerous Felon[*] or Dictator For Life.
[*] Some friends and coworkers went to one of those job fairs where you can fill out "send me free magazines which are vaguely tech-related" cards, which also have fill-in-the-blank Title lines. One of them convinced his supervisor to use Dangerous Felon in the field, and apparently the guy still gets an occasional freebie magazine addressed to Dangerous Felon Joe Public (with Joe Public replaced by his real name).
Wow. I thought I was the only person still alive who used 2.7. :-) Wasn't that just a kick to work with...
Uhhhh.... huh? The string class is like any other class is like any other critical piece of data. Protect them against multiple accesses.
Here's what the status is for GCC 3.1: http://gcc.gnu.org/onlinedocs/libstdc++/faq/index. html#5_6.
It works fine in my multithreaded Linux apps.
A good implementation of generic containers keeps the actual work in a hidden, non-template class. The template class -- the one which gets duplicated over and over for your 15 different things -- simply forwards operations and storage to the hidden class. And if the forwarding is well-written, most/all of it can be inlined and otherwise optimized away. Voila -- 15 containers, all sharing code.
Huh? Google doesn't have to get permission before caching. I don't have to get permission before keeping a copy in my local browser cache. Why should /.?
A very good point. I would expect a /.-cache to not rewrite those links into local caches. That way while the page is served up from slashdot, the banner ads are still being pinged from wherever. (I'm probably overlooking something.)
A far, far easier way to avoid the /. effect is for /. to simply keep a local (local to /. and the andover colocs) cache of the page. Link to that instead of to the actual site. The /. network is set up for that much load; a home enthusiast's cable modem isn't.
Maybe replace the link-to-cache with the link-to-real after 24 hours, or a week, or whatever. There's probably lots of tweaking possible here that I haven't even thought of, much less posted. My point is that /. has the capability to shoulder some of those slashdottings, at least briefly.
You seem to assume that being a C++ evangelist means that one must be an open source evangelist as well.
His new position seems to be that MS should strive to make their compiler ISO-compliant. Great. Nowhere in the ISO C++ standard -- nowhere in all 768 pages -- does it say that the compiler must also be OSS-friendly.
Would it surprise you to learn that Microsoft employees occasionally contribute code to GCC, in order to help binary compatibility? Granted it's never going to be fully binary compatible, since the Visual C++ vtbl layout is patented, but POD structs can be.
Some people get this point confused: while X11 is definitely
Maybe that's what threw you at first?
How is "give us money and we'll rank you higher" an original contribution to art and science? It reminds me of the feminist character at the frat party at the end of PCU, with the dawning realization, "You mean, if you're nice to [males], they bring you stuff?"
It's days like this, where I'm almost ready to write my Senator and try and take an active role, that I look at the decisions being made and say to myself, fuck it, we're too late.
I can't express how embarassing it is to be lounging around the marina, get challenged to a submarine drag-race, and lose to some other 100-foot submersible because I didn't hook up enough batteries. Finally, with the Phoenix 1000, I'll never have to endure their laughter again!
(Okay, okay, it's not funny... I'm just bored.)
Well, I did say grade school, not middle school, high school, or college. Or, heaven forfend, the workplace. :-)
That's something that both amuses me (when I'm feeling cynical) and scares me (when I'm feeling serious): that American citizens think this country is a democracy.
You said it every damn day in grade school, people:
That word isn't in there just to make patriotic songs have a better rhythm than "the democracy" would, ya'know.
Since this wasn't in the theatrical release, I'm wondering how the presence of these items -- which do play an important (read, live-saving) role later in the book -- is going to be explained.
Is the audience expected to believe that the phial of Galadriel in Frodo's jacket just sort of appeared there? Or will the theatrical release of the next two films have an extra voice-over from Frodo, "Oh, hey, check out this shiny thing lying underneath a rock! I'll just keep this, who knows, maybe it'll be useful."
And as soon as she reads your slashdot posts, your method is somewhat, er, compromised. :-)
Start at http://gcc.gnu.org/ and follow the link called "readings" or "further readings" or something like that. There should be one or more links to a C++ cross-vendor ABI spec.
Part of it is based on the System V gABI and psABI, and then there are some new things specifying cross-language name mangling and exception handling routines (e.g., a Java function calls a C++ function which calls an Ada function; the Ada function throws an Ada exception, which the Java function can catch as a Java exception.
First, the fact that different compilers use different name mangling (what you call "really nasty things") is a Good Thing. There are bigger differences between .o output than just the names; keeping the mangled names different means that you won't fall into any of the pitfalls resulting from those other differences. Magically making all the symbols the same will not let you magically link .o's/.so's/.a's from one compiler with code from another compiler.
Second, there is a standard ABI now. It was first implemented in 3.0, and 3.1 has some bugfixes for it. Other vendors are writing compilers to use the same ABI, which means that C++ can be cross-vendor-linked the same way as C.
I believe the original Command & Conquer[*] worker peons would finish a job, then look around for something to build/repair/harvest. The worker Imps in Dungeon Keeper have a priority list of things to do if you haven't assigned them anything (claim any unclaimed ground, reinforce any un-reinforced walls, scavenge dead bodies, etc).
Right now I have a hard time keeping track of my Citizens in Empire Earth because if something needs doing within their line of sight, they wander off and start working, and then I can't find them. (I have the most efficient, productive, confused society ever!)
[*] Made in the bad old days before Westwood could hire professional actors. I believe the man who plays the bad guy (Kane? Cain? sp?) works in the Westwood financial division or something. That's really cool. :-)
Such as web archives of mailing lists for opensource projects? It must be nice to sit there handing out advice and calling people idiots when you never contribute to the community.
Most of the spam I get is at an address harvested from mailing list archives for GCC, Doxygen, and few other much smaller projects. Does that mean I'm an idiot? If you think so, perhaps you shouldn't be using these programs (after all, an idiot has contributed to them).
Does that mean I'm going to stop sending mail to a public mailing list? No, because as much as I'd like to reduce the amount of spam I get, I'd much rather see improved software.
Suing spammers is being an idiot? Huh?
I believe it was some pesky bug in GCC 3.0 that caused KDE grief (well, plus the KDE coders were trying to to an end run around some of the C++ language rules). From what I can see GCC 3.1 is safe to use with KDE 3.0.
This is why major contributors to GCC who are also employed as a programmer must get a disclaimer signed by their employer, stating basically, "We don't really give a rat's ass about this work and promise not to try and hijack it in the future."
Without such protections, there wouldn't be much of g++ these days: the employer of the original author tried to make it a proprietary product once he was mostly done with it. Fortunately it was too late for them.
I wonder why the Perl folks don't require such protection of themselves.
Agreed. I think it was Dijkstra who argued that if Lines Of Code are counted, then the number should be viewed as a liability rather than an asset. That is, LOC are not something we produce, but something we spend.
Last holidays, I was given a copy of Things a Computer Scientist Rarely Talks About, a transcript of a series of six lectures by Knuth on the subject of religion. (Why six? "Because I could only think of six funny things to say for the lectures... and that was the first one.")
It's fascinating. Much of the lectures he talked about his 3:16 project, and the rest was an open Q&A session. Even if you're a hardcore atheist, you should pick up a copy; there's no preaching, and the audience discussion is far more insightful than the crap you're paying subscriptions for here on slashdot.
(Random bit of trivia from the book: for the project, Knuth used his own Bible translations. One of the lectures is mostly a "Bible-translate.HOWTO" commentary.)
Or the scene at the beginning of HHGTTG, where the Vogon ships turn every radio and flat surface into a remote-controlled speaker.
Exchange is a proprietary IMAP server with window dressing, and marketed to make PHB's think they can't use Outlook's features without it. Obviously you bought into that.
Well yeah, because it' true.