You give each soldier a set of (fertile) chicken eggs, wrapped in bubble wrap.
When they want to send a message, they hatch an egg, and then tie the message to one of the chicken's legs before sending it flying back to base (I forgot to say they are also issued a catapult)
Probably no less plausible an approach than these "infofuses".
Strictly speaking, to be recycled urine, wouldn't you have to wait until the Astronauts urinated after drinking the processed water. Seems like the story is premature.
Cancel out isn't quite correct. L2 is further away from the sun than earth and in line with it. An object there goes around the sun once a year, just like earth. The earth is providing the extra gravitational pull to keep it in orbit. Obviously, an object further away from the sun would normally orbit slower than the earth or else would fly off in an elliptical orbit if started with the same angualr velocity as the earth.
What did the losing teams use? If they all used Linux then the fact that the winning team did so is uninteresting. I assume that the teams were required to provide some set of services as well otherwise a winning strategy would be to simply pull the network connections.
A colleague and I once edited a text startup file for windows using debug - config.sys probably but I don't remember for sure.
We were at a trade show and needed to make a change to the file but edit, for some strange reason, was missing from the machine, so it was the only thing we had to make the edit.
After that I made sure I always had a floppy with key tools with me.
Given the recession, the economy needs all the help it can get, so adopting a name that could impact all the world's pig growers and processors was clearly a bad idea.
In any case, if only pigs caught it would we really have so much hysteria?
We should immediately show our sensitivity to these issues, and also a love of the short stories of Saki, by renaming it the unswine flu.
No real user types. There were things you could do to fake this but its hard to maintain.
Very limited procedure capability. There is a perform A through B capability (so the extent of the routine is defined at the call site! - but there is a way to avoid that using SECTIONs or internal labels) but there is no way to pass parameters - other than as global data. You can also write a subroutine as a separate compilation unit.
Modifiable (at run time) GOTO statements. Nobody in their right mind would allow this in new code even back in the late seventies (well, I wouldn't at least) but there was a lot of legacy code written by people not in their right mind. If I remember correctly PERFORMing a bunch of code would mess with the last paragraph so that if you subsequently fell through that code it would not in fact fall through. Doing this is, of course, evil, but see remarks above.
A large number of subsets. The language allowed you to subset. For example, one really nice feature was the report writer that would allow you to bang out a report program in a couple of hours, but lots of processors did not implement it. I actually had my own report program generator to avoid this problem.
What all this means is while its not that much easier to write bad programs in COBOL than in other languages, if you work at it, you can really make life difficult for someone coming to clean up your mess later.
I certainly hope they deem half naked (or worse!) anthropomorphic rabbits as inappropriate. Especially as this stuff tends to end up in the hands of children!
Microsoft Office, with all its pieces and parts, such as Outlook, will probably be set up to be one application, wheras if you want to run a third party email program (for example), you will have to burn one of your allowed apps.
This creates a user incentive to use one mother-of application from Microsoft for everything possible. By dividing things up into 3 essential Apps, they could lock out third party apps completely.
The alternative is to have upper management make all the decisions about the new system and make sure they make it "mission critical" that you go to the new software. That way, when it is really bad, nobody has to take blame. The transition will be fast too because actually working won't be a requirement before you phase the old stuff out. Ideally this needs to be done at CEO or board level so nobody has plausible deniability.
Note that I am not recommending this approach. I am simply noting its existence. As the Oxford dictionary says, descriptive not prescriptive. Wise management works to avoid doing things this way.
Slashdot Mirror
That's an editing picture. My COBOL is very rusty but I don't think you can pull just the digits out of it:
77 SOCIAL-SECURITY-NUMBER PIC 999-99-9999. ....
77 NUMERIC-SOCIAL PIC 999999999 COMP-3.
MOVE SOCIAL-SECURITY-NUMBER TO NUMERIC-SOCIAL.
IIRC, this does not work.
(the patent app is still crap though)
When they want to send a message, they hatch an egg, and then tie the message to one of the chicken's legs before sending it flying back to base (I forgot to say they are also issued a catapult)
Probably no less plausible an approach than these "infofuses".
I won't be truly impressed until they learn how to bribe the referees.
Strictly speaking, to be recycled urine, wouldn't you have to wait until the Astronauts urinated after drinking the processed water. Seems like the story is premature.
I soak the belt in water before I set off and then I can always find north by checking on which side the moss is growing.
Join the Army! Travel the World! Meet lots of interesting people, and kill them. (Spike Milligan; The Greate McGonigal, the Truth at Last)
So why does every update to Windows cost me $100?
Cancel out isn't quite correct. L2 is further away from the sun than earth and in line with it. An object there goes around the sun once a year, just like earth. The earth is providing the extra gravitational pull to keep it in orbit. Obviously, an object further away from the sun would normally orbit slower than the earth or else would fly off in an elliptical orbit if started with the same angualr velocity as the earth.
What did the losing teams use? If they all used Linux then the fact that the winning team did so is uninteresting. I assume that the teams were required to provide some set of services as well otherwise a winning strategy would be to simply pull the network connections.
We were at a trade show and needed to make a change to the file but edit, for some strange reason, was missing from the machine, so it was the only thing we had to make the edit.
After that I made sure I always had a floppy with key tools with me.
In any case, if only pigs caught it would we really have so much hysteria?
We should immediately show our sensitivity to these issues, and also a love of the short stories of Saki, by renaming it the unswine flu.
Classic COBOL is something of a special case:
No real user types. There were things you could do to fake this but its hard to maintain.
Very limited procedure capability. There is a perform A through B capability (so the extent of the routine is defined at the call site! - but there is a way to avoid that using SECTIONs or internal labels) but there is no way to pass parameters - other than as global data. You can also write a subroutine as a separate compilation unit.
Modifiable (at run time) GOTO statements. Nobody in their right mind would allow this in new code even back in the late seventies (well, I wouldn't at least) but there was a lot of legacy code written by people not in their right mind. If I remember correctly PERFORMing a bunch of code would mess with the last paragraph so that if you subsequently fell through that code it would not in fact fall through. Doing this is, of course, evil, but see remarks above.
A large number of subsets. The language allowed you to subset. For example, one really nice feature was the report writer that would allow you to bang out a report program in a couple of hours, but lots of processors did not implement it. I actually had my own report program generator to avoid this problem.
What all this means is while its not that much easier to write bad programs in COBOL than in other languages, if you work at it, you can really make life difficult for someone coming to clean up your mess later.
I certainly hope they deem half naked (or worse!) anthropomorphic rabbits as inappropriate. Especially as this stuff tends to end up in the hands of children!
Unless they were playing 20/20, I think the Led Zep would still work.
This creates a user incentive to use one mother-of application from Microsoft for everything possible. By dividing things up into 3 essential Apps, they could lock out third party apps completely.
I once drove a Ford Fiesta
Note that I am not recommending this approach. I am simply noting its existence. As the Oxford dictionary says, descriptive not prescriptive. Wise management works to avoid doing things this way.
Not at all, the law bans the rich, as well as the poor, from sleeping under bridges.
Chorus helps hide the fact that a singer is of key. Seems very appropriate.
it engulfs its first white lab coated scientist.
Couldn't find it, and I got soaking wet.
The taxpayers of course - you were expecting someone else?
Yes, its a pain. I only speak Hindi with a thick English accent and they have trouble understanding me.
As for retardation, we could have done with more of that in Victoria recently.
Lets just hope none of the lost ones were armed.
The most likely person to get bitten was Gates himself in any case. Unless you hold some radical theories about his state of health.