Correct. They are a development tool. There is no reason to have one remaining in embedded code that is declared to be releasable (and you're lazy if you do it in desktop code, too).
If you can grep "assert" in your code, you have work left to do.
Yes, people who actually know how to use asserts are quite rare. 99% of people use them incorrectly, causing more problems than they solve. If you put an assert in a piece of code you've instrumented temporarily to do some debugging, I won't mind. But if that crap ends up in the release db, I'm going to walk you to the door. For three reasons:
1. You shouldn't trust that all code will be compiled with -NDEBUG for release. Mistakes happen in makefiles, especially on large projects with iffy design documentation.
2. Most people don't do anything resembling safe and graceful when using an assert, because why should they?
3. If there's a part of the code you think needs an assert, then I ask why do you think that? Why can't you take action to recover from it? Or put in some sort of exception handling that can do something safe and graceful, that the user can recover from intelligently, and that may also retain some information we can use to characterize the problem?
And remember, this is an embedded system. The BSOD is not an option, nor usually is any sort of text output, which is all assert can give you.
Asserts have one valid use: to wrap something you know you haven't completed and that you know (or are hoping) will break. And if you're releasing stuff you know will break I don't want to pay you.
The rules for scrutinizing code for aircraft are based on the danger involved in not scrutinizing it enough. And the military doesn't have the same edict to follow them as commercial aviation does.
Since drones are unmanned, their code would get less scrutiny than manned aircraft, if it gets any scrutiny at all.
Normally, it will be scrutinized, inspected, tested, qualified, etc. But if anything goes wrong, the military can waive the requirement and take what it gets in order to meet a deadline.
Given that the criminal codes lay out a range of punishments from which the court can choose, not a single number the court must impose, you will find cases involving every number in the range. As for how the court decides, that might as well be a coin toss, because if the lawyers are doing their jobs, if one side or the other doesn't capitulate before the gavel comes down, it will be a coin toss.
Oh. So your post was a non sequitur. I doubt the OP knows about UK sentencing, either. I also doubt the UK gives a short sentence for possession of an AK, much less brandishing an AK, much less in a robbery. The other things as well.
What I got from it was that Leslie Sobon wrote a thousand words and ended it with a recommendation to buy her company's product, and is now getting a hundred thousand hits on it that she wasn't expecting.
That's why she's the VP of Marketing at a multi-billion-dollar corporation, while we think/. is still pretty cool.
I was using American sentencing. Uniform Criminal Code, q.v., plus a goulash of state laws. "The noose" is a figure of speech; "the needle" just wasn't distinctive enough to make my point as distinctively as I wanted.
The fact is, the crimes OP listed come with longer sentences on a count-by-count basis than CP does. And this case is not a single count of CP, it's two counts of CP plus one count of making the police chase the wrong guy. Interestingly, it omits any counts that directly speak to the offense the perp committed against the victim by making the police chase him, though maybe that's accounted for under the other count.
Armed Robbery with an AK-47 amounts to an aggravated felony (robbery aggravated by use of a weapon) plus a weapons charge (assuming the AK is not legally owned) that would run a couple of decades' jail time.
Shooting into a crowd would be 18-1/2 years at least, times one count per bullet fired. Add more if anyone gets injured. Add the noose if anyone dies.
Selling heroin to children also 18-1/2 years, per count.
You may have anecdotal evidence that judges have given out smaller sentences for such things, but there would be mitigation such as cooperation in other investigations, lack of intent, etc, to get those reductions.
I think they want a third thing, that would connect government to corporate entities.
Because the country is rapidly moving towards overt corporate control of government, and they don't want to have to fly to Washington to pull the strings.
Redirects are a minor inconvenience on the net. Much more insidious is the enormous number of sites that have to be accessed to get all the content on many webpages. Add to that the layers and layers of CSS needed to render them. And the massive, often buggy stack of scripts they bring. Not to mention the server-side scripting that slows down fetching the pages and embedded content and CSS pages and scripts before you get them.
It'd be interesting to see the average number of bytes transacted to render one byte of information to the screen. And the average loading time of a page.
Rocks coming from space arrive at speeds from slightly less than escape velocity to much more than escape velocity*. A rock following the planet in a similar orbit may enter the planet's gravity well at a speed relatively near to 0, but by the time it hits atmosphere the relative speed will be very high. And a rock falling towards the sun on an elongated elliptical orbit that intersects the Earth's will be going extremely fast at the point it reaches the atmosphere.
The incident angle is more of a factor here. A direct descent through 100 km of progressively increasing density of air will have only a few seconds to decelerate and will make a much bigger dent than a grazing trajectory that goes through hundreds or thousands of km of atmosphere, losing speed sometimes to the point it's at terminal velocity. Although terminal velocity for a solid hunk of iron is going to be several hundred kph at least, which would make it as destructive as a cannonball.
If the meteor explodes due to atmospheric heating, pieces can go in any direction with any speed from the point of the explosion, so it might be possible for a rock to have a fairly small speed on impact with the ground.
But more likely the case for the martian meteorite here is that it hit at an oblique angle and bounced and rolled to where it sits now. Follow its track back and you'll likely find a fair sized hole that may or may not be round (impact craters are funny in that they come out round for a wide range of angles of impact).
* - Escape velocity for Earth is 11 km/s (about 25k mph).
Actually, anyone who was exposed to Syphilis in the 18th century knows what "infection" really means, and it wasn't known as a disease of the rich for nothing.
Slashdot Mirror
asserts are for preventing programming errors
Correct. They are a development tool. There is no reason to have one remaining in embedded code that is declared to be releasable (and you're lazy if you do it in desktop code, too).
If you can grep "assert" in your code, you have work left to do.
The judge in the losing cases should be making sure it's expensive to lose, as well. Countersuits should come into play, too.
Unless that's per day, it's not nearly enough.
Here, you dropped this:
you insensitive clods!
He's just getting you back for all the times you played kitchen-implement drums while he was trying to nap.
Hug him for it.
Yes, people who actually know how to use asserts are quite rare. 99% of people use them incorrectly, causing more problems than they solve. If you put an assert in a piece of code you've instrumented temporarily to do some debugging, I won't mind. But if that crap ends up in the release db, I'm going to walk you to the door. For three reasons:
1. You shouldn't trust that all code will be compiled with -NDEBUG for release. Mistakes happen in makefiles, especially on large projects with iffy design documentation.
2. Most people don't do anything resembling safe and graceful when using an assert, because why should they?
3. If there's a part of the code you think needs an assert, then I ask why do you think that? Why can't you take action to recover from it? Or put in some sort of exception handling that can do something safe and graceful, that the user can recover from intelligently, and that may also retain some information we can use to characterize the problem?
And remember, this is an embedded system. The BSOD is not an option, nor usually is any sort of text output, which is all assert can give you.
Asserts have one valid use: to wrap something you know you haven't completed and that you know (or are hoping) will break. And if you're releasing stuff you know will break I don't want to pay you.
You're fired.
Dude. That's been common knowledge for years.
If you put an assert in any embedded code I would fire you.
The rules for scrutinizing code for aircraft are based on the danger involved in not scrutinizing it enough. And the military doesn't have the same edict to follow them as commercial aviation does.
Since drones are unmanned, their code would get less scrutiny than manned aircraft, if it gets any scrutiny at all.
Normally, it will be scrutinized, inspected, tested, qualified, etc. But if anything goes wrong, the military can waive the requirement and take what it gets in order to meet a deadline.
Like I said. Anecdotes.
Given that the criminal codes lay out a range of punishments from which the court can choose, not a single number the court must impose, you will find cases involving every number in the range. As for how the court decides, that might as well be a coin toss, because if the lawyers are doing their jobs, if one side or the other doesn't capitulate before the gavel comes down, it will be a coin toss.
Oh. So your post was a non sequitur. I doubt the OP knows about UK sentencing, either. I also doubt the UK gives a short sentence for possession of an AK, much less brandishing an AK, much less in a robbery. The other things as well.
What I got from it was that Leslie Sobon wrote a thousand words and ended it with a recommendation to buy her company's product, and is now getting a hundred thousand hits on it that she wasn't expecting.
That's why she's the VP of Marketing at a multi-billion-dollar corporation, while we think /. is still pretty cool.
I was using American sentencing. Uniform Criminal Code, q.v., plus a goulash of state laws. "The noose" is a figure of speech; "the needle" just wasn't distinctive enough to make my point as distinctively as I wanted.
The fact is, the crimes OP listed come with longer sentences on a count-by-count basis than CP does. And this case is not a single count of CP, it's two counts of CP plus one count of making the police chase the wrong guy. Interestingly, it omits any counts that directly speak to the offense the perp committed against the victim by making the police chase him, though maybe that's accounted for under the other count.
It's not up to him to keep his computer secure. It's up to the miscreant not to commit the crime.
None of the above.
Armed Robbery with an AK-47 amounts to an aggravated felony (robbery aggravated by use of a weapon) plus a weapons charge (assuming the AK is not legally owned) that would run a couple of decades' jail time.
Shooting into a crowd would be 18-1/2 years at least, times one count per bullet fired. Add more if anyone gets injured. Add the noose if anyone dies.
Selling heroin to children also 18-1/2 years, per count.
You may have anecdotal evidence that judges have given out smaller sentences for such things, but there would be mitigation such as cooperation in other investigations, lack of intent, etc, to get those reductions.
I think they want a third thing, that would connect government to corporate entities.
Because the country is rapidly moving towards overt corporate control of government, and they don't want to have to fly to Washington to pull the strings.
You mean "a network based on protocols developed for The Internet" and "The Internet".
I suppose we could go outside or something...
nah.
Redirects are a minor inconvenience on the net. Much more insidious is the enormous number of sites that have to be accessed to get all the content on many webpages. Add to that the layers and layers of CSS needed to render them. And the massive, often buggy stack of scripts they bring. Not to mention the server-side scripting that slows down fetching the pages and embedded content and CSS pages and scripts before you get them.
It'd be interesting to see the average number of bytes transacted to render one byte of information to the screen. And the average loading time of a page.
Rocks coming from space arrive at speeds from slightly less than escape velocity to much more than escape velocity*. A rock following the planet in a similar orbit may enter the planet's gravity well at a speed relatively near to 0, but by the time it hits atmosphere the relative speed will be very high. And a rock falling towards the sun on an elongated elliptical orbit that intersects the Earth's will be going extremely fast at the point it reaches the atmosphere.
The incident angle is more of a factor here. A direct descent through 100 km of progressively increasing density of air will have only a few seconds to decelerate and will make a much bigger dent than a grazing trajectory that goes through hundreds or thousands of km of atmosphere, losing speed sometimes to the point it's at terminal velocity. Although terminal velocity for a solid hunk of iron is going to be several hundred kph at least, which would make it as destructive as a cannonball.
If the meteor explodes due to atmospheric heating, pieces can go in any direction with any speed from the point of the explosion, so it might be possible for a rock to have a fairly small speed on impact with the ground.
But more likely the case for the martian meteorite here is that it hit at an oblique angle and bounced and rolled to where it sits now. Follow its track back and you'll likely find a fair sized hole that may or may not be round (impact craters are funny in that they come out round for a wide range of angles of impact).
* - Escape velocity for Earth is 11 km/s (about 25k mph).
So you're saying it was 100% fatal! Aiieeeeeeee!
It puts them about 50 years behind the US and the Russians in extraterrestrial exploration.
I don't see why it's at all fishy.
BTW, they don't serve cat at Chinese restaurants, either.
Actually, anyone who was exposed to Syphilis in the 18th century knows what "infection" really means, and it wasn't known as a disease of the rich for nothing.
He's responsible for discovering that he could change the color of texts.
He's not responsible for cross-linking to porn sites.
And he's no doubt not the first to try it, just the first since Twitter borked their own countermeasures against such things.