Then the compiler is not compliant with the standard. Since it defined the constant 0 (and only the constant 0 not for example 1-1) in a pointer context as being converted to the NULL pointer at compile time. The only times 0 isn't correct is as an argument to a function with no prototype (which no one does anymore, right:) and as an argument to a varargs function call - since in both those cases there is no pointer context to trigger the conversion.
(And yes, gcc will throw a warning if you compare a function pointer with 0 instead of NULL)
That better not be true... Since ANSI C says that NULL is 0.
And in fact I know it isn't, since the C library my installation of gcc is using has the following in stdlib.h and all my programs that compare function pointers with NULL compile without warnings:
#define NULL 0
You couldn't take 10 seconds to actually test your idiotic claim?
What's he going to do when one of his kids decides to follow a different religion? Have a different secual orientation? Cheer for a different sports team?
Using a search engine... my god... that man has problems.
There were no sentitivities. And I'm not non-australian.
I just wondered if there was a reason for using the two words or if it was just random (ie. you could have used them in the other order with no change to your intended meaning).
Are you just using random words for fun? Or did his son spam people in Australian territories that aren't part of the Australian continent (which is more likely with email than phones I guess)...
Children learn to catch a ball through trial and error, over time they notice what they need to do to succeed. It's not calculus, it's just that experience allows them to predict where the ball will end up. They aren't doing calculations they have just seen enough balls thrown to be able to make a prediction because they have seen how a ball travels when thrown. Just like children learn that screaming gets the TV to display their favourite show, and that flipping the light switch makes the lights turn on and off - they don't know the mechanism they've just done it enough to be able to make a prediction based on past behaviours.
It was one of several calls made by Smith to numbers not linked with his defense attorney that officials at the Elk River facility monitored and recorded.
Remember, when you're going to call someone from jail to discuss killing a witness have them steal your attorney's cell phone first...
Well you could use a different encryption system for backups. In fact you're likely to unless you have some fancy filesystem which lets you track changes or if you are doing non-incremental backups all the time. Personally I use duplicity for encrypted backups (and would do so from an encrypted file system too - you really want to be able to diff the unencrypted data and then encrypt the backups seperately).
If you have no where to copy the data then clearly you also have no backups in which case the data clearly isn't worth a lot to you anyway. When a disk I ordered the other day finally arrives I have the fun task of moving a bunch of data around in order to turn the drives into RAID-5 - I don't have enough disk elsewhere for all the meantime and the disk it's currently on is to be part of the RAID... So all the stuff I don't use/care about too much is just going to stay on the 40 or so DVDs it's also on while the stuff I use gets transferred to a smaller drive and copied back after the conversion. I'd add encryption to the RAID volume, but I don't think the tiny little device running it with it's 32MB of RAM and underpowered CPU would like it:)
Yes restoring backups is a PITA, but less time than hoping for forum answers to questions of the form "I used this deprecated format and upgraded my system and the deprecated format was removed and now I can't access the data, how do I get it back?"...
I'd be annoyed too if I did such a thing to myself, but seriously doing an upgrade when your actively using something marked deprecated just isn't something you do. At least not without making the procedure roll backable (by copying / somewhere else and keeping the old kernel around so you can boot them together, for example). Staying away from kernel/user space combinations is perfectly reasonable, but so is just making sure you don't stay with deprecated features through an upgrade.
Also I see no reason why you couldn't make a bootable CD with the right kernel and user space to get at the data if such an upgrade disaster occurs.
Backing out the upgrade shouldn't be difficult. At the very worst you install whatever version it was on a UCB pen drive and boot from it... (or CD-R or HDD or whatever you have available). The old rescue disk might even be good enough...
But as I said deprecated means what it says, doing an upgrade when you are relying on something marked deprecated is pretty foolish - unless you checked the release notes to make sure they say it hasn't been removed of course.
1. boot into the old kernel/backout the upgrade. 2. Mount encrypted filesystem and copy data elsewhere 3. Create encrypted filesystem such that you don't get deprecated warnings. 4. Copy the data back.
I really can't understand continuing with something marked deprecated anyway - certainly not doing an upgrade while doing so. What do you think deprecated means? I'd be doing steps 2-4 as soon as the deprecated option was needed.
Slashdot Mirror
Then the compiler is not compliant with the standard. Since it defined the constant 0 (and only the constant 0 not for example 1-1) in a pointer context as being converted to the NULL pointer at compile time. The only times 0 isn't correct is as an argument to a function with no prototype (which no one does anymore, right :) and as an argument to a varargs function call - since in both those cases there is no pointer context to trigger the conversion.
You need a better compiler.
Notice the word or. NULL can be 0 or NULL can be (void*)0.
Since 0 is a perfectly valid definition of NULL according to the standard then if (p==0) is also perfectly valid when p is a pointer to a function.
(And yes, gcc will throw a warning if you compare a function pointer with 0 instead of NULL)
That better not be true... Since ANSI C says that NULL is 0.
And in fact I know it isn't, since the C library my installation of gcc is using has the following in stdlib.h and all my programs that compare function pointers with NULL compile without warnings:
#define NULL 0
You couldn't take 10 seconds to actually test your idiotic claim?
Enemies going flying in Morrowind was non-existant compared to Oblivion. If you shot, let's say a Cliff Racer, it fell straight down.
Floated straight down seems a better description.
Try reading the rest of the article.
Yes, because there weren't any obvious bugs in Daggerfall.
Robbery (which the article is actually about) is not the same as theft.
Yeah that's smart, instead of holding a radio transmitter up to your head, clip one onto (and into) your ear.
Much better.
The US drop out rate is 4.5%, so it's not like the same thing doesn't push up their average too.
Car Wars, Ogre, Frag.
Surely you must like at least one of those...
What a dickhead.
What's he going to do when one of his kids decides to follow a different religion? Have a different secual orientation? Cheer for a different sports team?
Using a search engine... my god... that man has problems.
Because memory is mentioned in the bloody post...
There were no sentitivities. And I'm not non-australian.
I just wondered if there was a reason for using the two words or if it was just random (ie. you could have used them in the other order with no change to your intended meaning).
Are you just using random words for fun? Or did his son spam people in Australian territories that aren't part of the Australian continent (which is more likely with email than phones I guess)...
I really doubt it.
Children learn to catch a ball through trial and error, over time they notice what they need to do to succeed. It's not calculus, it's just that experience allows them to predict where the ball will end up. They aren't doing calculations they have just seen enough balls thrown to be able to make a prediction because they have seen how a ball travels when thrown. Just like children learn that screaming gets the TV to display their favourite show, and that flipping the light switch makes the lights turn on and off - they don't know the mechanism they've just done it enough to be able to make a prediction based on past behaviours.
That creature is a fish|not a fish. That creature is a mammal; or it lays eggs and has a bill, so it is a bird (ummm, bad example, on second thought).
Curse those platypus...
Remember, when you're going to call someone from jail to discuss killing a witness have them steal your attorney's cell phone first...
I hate to be break the news to you, but the FIAT Group owns the Ferrari. This has been the case since 1969...
I'm a recent immigrant. More than a few phone calls have been made to Iran from my phone. The wiretap bit doesn't seem that unlikely...
Well you could use a different encryption system for backups. In fact you're likely to unless you have some fancy filesystem which lets you track changes or if you are doing non-incremental backups all the time. Personally I use duplicity for encrypted backups (and would do so from an encrypted file system too - you really want to be able to diff the unencrypted data and then encrypt the backups seperately).
If you have no where to copy the data then clearly you also have no backups in which case the data clearly isn't worth a lot to you anyway. When a disk I ordered the other day finally arrives I have the fun task of moving a bunch of data around in order to turn the drives into RAID-5 - I don't have enough disk elsewhere for all the meantime and the disk it's currently on is to be part of the RAID... So all the stuff I don't use/care about too much is just going to stay on the 40 or so DVDs it's also on while the stuff I use gets transferred to a smaller drive and copied back after the conversion. I'd add encryption to the RAID volume, but I don't think the tiny little device running it with it's 32MB of RAM and underpowered CPU would like it :)
Yes restoring backups is a PITA, but less time than hoping for forum answers to questions of the form "I used this deprecated format and upgraded my system and the deprecated format was removed and now I can't access the data, how do I get it back?"...
I'd be annoyed too if I did such a thing to myself, but seriously doing an upgrade when your actively using something marked deprecated just isn't something you do. At least not without making the procedure roll backable (by copying / somewhere else and keeping the old kernel around so you can boot them together, for example). Staying away from kernel/user space combinations is perfectly reasonable, but so is just making sure you don't stay with deprecated features through an upgrade.
Also I see no reason why you couldn't make a bootable CD with the right kernel and user space to get at the data if such an upgrade disaster occurs.
No.
Backing out the upgrade shouldn't be difficult. At the very worst you install whatever version it was on a UCB pen drive and boot from it... (or CD-R or HDD or whatever you have available). The old rescue disk might even be good enough...
But as I said deprecated means what it says, doing an upgrade when you are relying on something marked deprecated is pretty foolish - unless you checked the release notes to make sure they say it hasn't been removed of course.
Why bother waiting so long:
1. boot into the old kernel/backout the upgrade.
2. Mount encrypted filesystem and copy data elsewhere
3. Create encrypted filesystem such that you don't get deprecated warnings.
4. Copy the data back.
I really can't understand continuing with something marked deprecated anyway - certainly not doing an upgrade while doing so. What do you think deprecated means? I'd be doing steps 2-4 as soon as the deprecated option was needed.
Or maybe http://www.imdb.com/gallery/scrapbook/47/Sbk/47/55 497_1_9.jpg
There is no "fair use" in Australian copyright law. There's "fair dealing" but it doesn't cover parody.