So it is allowed by Estonian laws to install trojans on the computers of unsuspecting victims, to redirect accesses to legitimate sites through DNS redirection to unrelated sites, to claim bogus virus infection on fake versions of legitimate sites and offer expensive fake "antivirus" software as "cure"?
Given that the code snippet only used operator*=, an overloaded operator= would have had no effect at all. An overloaded operator*= on the other hand...... and of course, somewhere deeply hidden in a header, there might be something like
#define i (*some_function(j,k))
where of course j and k are to be provided by the code using the macro.
The reason I consider goto evil is because it obfuscates control flow for the reader. They must search for the label to find out where control is going to. Return, break and continue do not have this effect.
For break/continue, they have to search for the beginning/end of the construct it belongs to instead. And unlike a label, you cannot just use your editor's search function. Also, if you are in a switch inside a loop, break will apply to the switch, while continue will apply to the loop. Now you might argue that if you have any problems to find the beginning/end of your loop, then you probably have a design problem. But the same holds if you can't find your label.
Actually, I've never actually found the need to have a goto in my code. However if I ever come across a case where it makes sense, I'll not hesitate to use it. There only strict rule about goto IMHO is:
Never use a goto to jump into a block. This includes "blocks" formed by a goto and its label.
Similarly, the "there shall be only one exit from a function" is often used as a tautology by some.
AFAIK they even removed alternate return arguments from Fortran. At the same time, exceptions are added to modern languages, which are noting but a different way to specify alternate return paths. The same is of course true for C's longjmp.
However, for any language which offers neither exceptions (or similar mechanisms like longjmp) nor alternate return arguments, the "only one exit from a function" is a tautology (i.e. it's automatically true). You probably actually meant return statements inside the function, but that's not an alternate return path, but just a "goto end_of_function" inside the function. You'll end up in the calling code exactly at the same place as with a return at the end.
I especially like the ones where one of the tokens is standing over the shoulder and pointing something out to another token (normally a female), who is sitting down looking at a computer screen.
The male one points out something to the female one? Isn't the female one able to figure it out for herself? That's sexualism!:-)
No, what parent is trying to say that it's generally a good idea to picture the sort of people you expect to sell to. If you want to sell to farmers, you'll not show bankers in your ads, and vice versa. Since there are very few black people in Poland, there's no point in showing black people in ads (unless you want to convey a specific message by doing so). Of course photoshopping away the black person is silly. After all, Microsoft should be able to afford shooting the picture again with white people (possibly even Polish-looking people!).
Re:and if these companies made profit?
on
NASA May Outsource
·
· Score: 1
But outsourcing would have a big advantage for NASA: The next time their launch vehicle explodes, they can just point to the producers and say "it was their fault, not ours!"
So people who don't have cars should have to pay extra for those who do? Why are there tolls on roads and bridges? So that the people who use the service pay for it and those that do not are not burded with that tax liability. I would be willing to bet money you would be the first one to whine when they raise taxes to pay for things YOU don't use. The implementation might be screwed, but the idea of paying only for the services you use is a great idea.
2 * 1 = 2 < 3 = 6 * 1/2
Core dumped.
Since they redirect your DNS queries through a trojan, I don't see how they couldn't.
So it is allowed by Estonian laws to install trojans on the computers of unsuspecting victims, to redirect accesses to legitimate sites through DNS redirection to unrelated sites, to claim bogus virus infection on fake versions of legitimate sites and offer expensive fake "antivirus" software as "cure"?
Early 200210? Obviously it took quite some time for the tax reform to show positive effects. :-)
Actually it's easy to test: Duplicate earth, but without the humans. If both show the same trend, it's natural. Otherwise it's man-made. :-)
So now we know who's really responsible for the current financial crisis. :-)
Given that the code snippet only used operator*=, an overloaded operator= would have had no effect at all. An overloaded operator*= on the other hand ... ... and of course, somewhere deeply hidden in a header, there might be something like
where of course j and k are to be provided by the code using the macro.
There is an assumption that code is always meant for humans to read.
Well, some people like trivial literature, others like to read something more demanding. :-)
Well, if you are programming C++ (the proper way), RAII handles that for you.
For break/continue, they have to search for the beginning/end of the construct it belongs to instead. And unlike a label, you cannot just use your editor's search function. Also, if you are in a switch inside a loop, break will apply to the switch, while continue will apply to the loop. Now you might argue that if you have any problems to find the beginning/end of your loop, then you probably have a design problem. But the same holds if you can't find your label.
Actually, I've never actually found the need to have a goto in my code. However if I ever come across a case where it makes sense, I'll not hesitate to use it. There only strict rule about goto IMHO is:
Never use a goto to jump into a block. This includes "blocks" formed by a goto and its label.
AFAIK they even removed alternate return arguments from Fortran. At the same time, exceptions are added to modern languages, which are noting but a different way to specify alternate return paths. The same is of course true for C's longjmp.
However, for any language which offers neither exceptions (or similar mechanisms like longjmp) nor alternate return arguments, the "only one exit from a function" is a tautology (i.e. it's automatically true). You probably actually meant return statements inside the function, but that's not an alternate return path, but just a "goto end_of_function" inside the function. You'll end up in the calling code exactly at the same place as with a return at the end.
So if you both hate and distrust other groups, you're not xenophobic?
Well, actually your definition is wrong anyway: Xenophobia is by definition the fear of other groups (phobia = fear).
The male one points out something to the female one? Isn't the female one able to figure it out for herself? That's sexualism! :-)
Adobe.
The fuck? Now the god damn porn has to be PC?!
You really don't want Mac porn!
No, what parent is trying to say that it's generally a good idea to picture the sort of people you expect to sell to. If you want to sell to farmers, you'll not show bankers in your ads, and vice versa. Since there are very few black people in Poland, there's no point in showing black people in ads (unless you want to convey a specific message by doing so).
Of course photoshopping away the black person is silly. After all, Microsoft should be able to afford shooting the picture again with white people (possibly even Polish-looking people!).
Simply ask that man with the beard.
If it is a minefield, it may indeed be a good idea to ask Osama bin Laden. After all, he should have experience in explosives.
That's what he wants you to believe. :-)
I read a blessed scroll of taming.
Not to mention dressing while driving. :-)
What about the lung cancer not caused by smoking?
But outsourcing would have a big advantage for NASA: The next time their launch vehicle explodes, they can just point to the producers and say "it was their fault, not ours!"
You pay car tax for a car you don't have?
Well, there's this thing called tax, which exists for exactly this reason.