I don't see how. In the case that both a and b are properties, and the properties have read methods, which is not necessarily the case (most often it's not in fact), then the read methods must complete entirely before the expression can be calculated. The result is stored in a, which might be a write method, but this happens only after the read method has completed, so we are ok.
Essentially a property is not much different from a method without arguments, and it should be treated as such, and not as a standard variable. Actually you can also have properties with arguments in certain cases. They work mostly like arrays. You can even use a string as the array key.
At least with actual functions/messages/methods/etc these things can actually be understood by mortals:)
The major point is that you should always consider calling a property to be the same as calling a method. Methods can cast exceptions if they feel like it, and a method could take an unexpected amount of time. It's nothing more than a very convinient interface. When I say "used right" I am mainly saying that nothing unexpected should occur when you call a property. And that it might take a while to complete should not be unexpected if you consider a property to be equal to a method. Documentation is important here. Every possible side effect should be documented.
Properties are worthless and good at hiding side effects.
Properties are fantastically useful, and the fact that you can hide side effects is totally cool. Of course it's something that must be respected and not used carelessly, but if it's used right it is a very neat feature.
Headers make things vastly more efficient when dealing with system libraries; it would be crazy to compile everything
There is no reason the compiler shouldn't be able to ignore the implementation section when you are just using the interface. Of course you need the entire source, instead of just the header files, but that's a minor inconvinience in my opinion.
And whether it makes coding easier is a matter of taste.
In any case this version of Sober is truely the nastiest I have seen hitting my server as of yet. First recognized by ClamAV on the 21st of november. I havent got a precise count but it's got to be at least 400 emails in quaranteene up to now, and they just keep coming in. Excluding phishing emails that are also blocked by ClamAV it probably at least a 400% increase in average amount of quaranteened mails per day.
"Change it yourself" is like saying "if skinheads painted Nazi slogans on your house wall, just repaint it". Is that really OK and is all that should be done? Nobody should be pursued for this?
It's actually more like..
- So you are telling me that some skinheads painted Nazi slogans on my house?
- oh.. Well sorry, I was too busy to notice. The paint is over there, feel free to change it to something you find more to your liking!
The release candidate has been on alioth since mid november. Those packages are considered highly experimental!
On the other hand major KDE releases does seem to get shorter and shorter time between them, and I have a sneaky suspicion that they are cutting features off their roadmaps to get the release out at a certain time and not telling people about it. I can't prove that though.
I do think KDE needs to reconsider how they do quality control, and think more about stability vs. features.
I have often mentioned my disbelief in common astronomical theories to my fellow students at the Niels Bohr Institute here in Copenhagen, and not once have I been meet with an attitude like the one you describe. (For instance I don't believe such a thing as a GR-black hole actually exists..)
In my oppinion your fellow students are seriously lacking in their scientifical education if they are unable to accept that alternative theories should be considered seriously but critically.
Perhaps with quantum mechanics as the only possible exception (because QM is true and that's just the way it is..:), I have never had the experience that any scientific theory has been considered unquestionably true.
You don't get it. You can't infiltrate the trust circle. Those inside would shove you out, once they find out you are no good, so your basic premise fails.
The lights saber props are basically wooden sticks with reflective coating. Originally the idea was that the reflectivity would hopefully look futuristic enough not to need having any FX done on them. In post production they realised that really what they looked most like was.. reflective wooden sticks..
However, it turned out that the reflective coat was an excellent base for painting the finished light sabers over. They were painted on by hand frame by frame.
What is the status on KDE 3.4.1 and accompanying addons becoming current with X.org currently kludging its way through Sid?[alioth hasn't updated its 3.4.1 packages since early June, long before Branden submitted X.org into Sid.]
Everybody is working on the transition from GCC 3.3 to GCC 4. A big pile of packages have still to be rebuild. During that time the X Strike Force is working on getting Xorg to compile on all architectures. Once all that is in place. KDE 3.4.1 will be uploaded, and the bug squishing on that will begin. I'm guessing a month or so before a fully working KDE 3.4.1 is in sid, give a couple of months/take a week..;)
In the meantime you can still use Alioth KDE 3.4.1 packages with sid and xorg (Yes, Really!). You need to delete all aspell and libjack packages from sid, and get libaspell and libjack from testing, then KDE will install without problems. And hold off on upgrading once you have something that works, unless you are prepared to sort out the dependency issues that are bound to arise
It's a valid concern, but I think one should think of this as a way to get people who otherwise wouldn't be able to move around much, to excercise their muscles more than they would have without this aid. Any workout counts, so I think for many this would be a good thing. Also one day it could possibly help permanently paralized to walk again, which would be a great thing in my opinion.
I think you misunderstand. Those are two seperate cases. In one case I slowly read through content, and thus move the mouse slowly. In my experience the mouse tends to drift off to the side after a while, thus the text suddenly shifts position without me wanting it. In the other case i just grap the scroll bar and move it all the way to one end, without looking at the content. For instance when you are editing some text and want to add some new text at the end.
I'd say that the drag area extends just under 2 inches out from the bar on my 19 inch monitor, which runs in 1280x1024. But to me any size is too small, and I think you just got used to a 'misfeature' in windows, so much so that now you can't live without it. I am used to not having it this way, so I hate the feature. We probably will never agree on whats the best solution. If only we could get a config option to turn off that behaviour, we would both be happy.
Because many times you will want to drag a page for a long time while reading or looking though some stuff. After a while you can't be expected to hold your precision with the pointer exactly to the small area in which the drag works. Eventually the pointer will venture out because you are not keeping an eye on what you are doing with it. So suddenly while you are reading something, the text jumps up to it's original position. Then you have to remove your attention from the material and focus on bringing the scrollbar under control. Totally annoying!
Another point. A lot of times on smaller scroll areas you just want to scroll all the way to the top or bottom. In all other OS's you can just click on the scrollbar and move the mouse very fast to the bottom of the screen and let go, and you know you will get the result you want. Not so in windows. Because you have to keep the mouse pointer in close proximity of the scrollbar for scrolling to work correctly you have to be very carefull about not making too erratic mouse movements. So it slows down the work yet again because you have to focus your attention on scrolling and not on the content you are looking at.
Fortunately edge dragging (on touch pads) and mouse wheels alleviate many of the problems with windows scroll bars. Otherwise I think I would go insane..
You are probably just trolling, but heck I'll bite this one.
Why oh why would you ever want this? The standard way of canceling a mouse drag action is to right click. That should be enought. And no other OS has this. That should give you some hint that it is a bad idea.
This is somewhat akeen to the stupidest "feature" in Windows, when you are dragging a scrollbar and move the mouse too far away from the bar, it will jump back to it's original position. Fucking moronic.
You may not have a complete upgrade if you haven't seen this. The upgrade will hold back some packages that causes this conflict if you don't do anything manually. In that case you are probably still running xfree86 instead of xorg.
Or the packages may have already been rebuild. I can't check that right now though.
The changes has broken the experimental packages of KDE 3.4.1 on Alioth because of unfulfilled dependencies.
If you use those packages you should hold off with this upgrade for a while as it will cause many of the core KDE packages to uninstall breaking KDE completely.
Slashdot Mirror
Can this fail?
a = a + b;
I don't see how. In the case that both a and b are properties, and the properties have read methods, which is not necessarily the case (most often it's not in fact), then the read methods must complete entirely before the expression can be calculated. The result is stored in a, which might be a write method, but this happens only after the read method has completed, so we are ok.
Essentially a property is not much different from a method without arguments, and it should be treated as such, and not as a standard variable. Actually you can also have properties with arguments in certain cases. They work mostly like arrays. You can even use a string as the array key.
At least with actual functions/messages/methods/etc these things can actually be understood by mortals :)
The major point is that you should always consider calling a property to be the same as calling a method. Methods can cast exceptions if they feel like it, and a method could take an unexpected amount of time. It's nothing more than a very convinient interface. When I say "used right" I am mainly saying that nothing unexpected should occur when you call a property. And that it might take a while to complete should not be unexpected if you consider a property to be equal to a method. Documentation is important here. Every possible side effect should be documented.
Properties are worthless and good at hiding side effects.
Properties are fantastically useful, and the fact that you can hide side effects is totally cool. Of course it's something that must be respected and not used carelessly, but if it's used right it is a very neat feature.
Headers make things vastly more efficient when dealing with system libraries; it would be crazy to compile everything
There is no reason the compiler shouldn't be able to ignore the implementation section when you are just using the interface. Of course you need the entire source, instead of just the header files, but that's a minor inconvinience in my opinion.
And whether it makes coding easier is a matter of taste.
Btw: I am a total Delphi fan..
That site sets off my bullshit alarm bigtime..
In any case this version of Sober is truely the nastiest I have seen hitting my server as of yet. First recognized by ClamAV on the 21st of november. I havent got a precise count but it's got to be at least 400 emails in quaranteene up to now, and they just keep coming in. Excluding phishing emails that are also blocked by ClamAV it probably at least a 400% increase in average amount of quaranteened mails per day.
"Change it yourself" is like saying "if skinheads painted Nazi slogans on your house wall, just repaint it". Is that really OK and is all that should be done? Nobody should be pursued for this?
It's actually more like..
- So you are telling me that some skinheads painted Nazi slogans on my house?
- oh.. Well sorry, I was too busy to notice. The paint is over there, feel free to change it to something you find more to your liking!
Not entirely true.
As you can readily verify by looking at the developer information for the kdelibs source package, kde 3.5 has not been uploaded into Debian yet.
The release candidate has been on alioth since mid november. Those packages are considered highly experimental!
On the other hand major KDE releases does seem to get shorter and shorter time between them, and I have a sneaky suspicion that they are cutting features off their roadmaps to get the release out at a certain time and not telling people about it. I can't prove that though.
I do think KDE needs to reconsider how they do quality control, and think more about stability vs. features.
4. The laptop's hard drive was destroyed.
Hey? No pictures?!?!!!
Try telling the kids that these days, and they won't believe you..
I have often mentioned my disbelief in common astronomical theories to my fellow students at the Niels Bohr Institute here in Copenhagen, and not once have I been meet with an attitude like the one you describe. (For instance I don't believe such a thing as a GR-black hole actually exists..)
In my oppinion your fellow students are seriously lacking in their scientifical education if they are unable to accept that alternative theories should be considered seriously but critically.
Perhaps with quantum mechanics as the only possible exception (because QM is true and that's just the way it is.. :), I have never had the experience that any scientific theory has been considered unquestionably true.
Sure! And Debian Sarge should be released any day now!
oh wait..
What do you mean, next stop? RFID theft is where the trip starts!!
Parent is correct. This was posted a few months ago.
No no! There are hot pools. Just wait. In the future this spot will be a prime tourist destination in the solar system.
Get the Enceladus Spa Experience before your neighbour!
You don't get it. You can't infiltrate the trust circle. Those inside would shove you out, once they find out you are no good, so your basic premise fails.
The lights saber props are basically wooden sticks with reflective coating. Originally the idea was that the reflectivity would hopefully look futuristic enough not to need having any FX done on them. In post production they realised that really what they looked most like was.. reflective wooden sticks..
However, it turned out that the reflective coat was an excellent base for painting the finished light sabers over. They were painted on by hand frame by frame.
More info at wikipedia
6.51940523 × 10^-12 Parsecs
What is the status on KDE 3.4.1 and accompanying addons becoming current with X.org currently kludging its way through Sid?[alioth hasn't updated its 3.4.1 packages since early June, long before Branden submitted X.org into Sid.]
Everybody is working on the transition from GCC 3.3 to GCC 4. A big pile of packages have still to be rebuild. During that time the X Strike Force is working on getting Xorg to compile on all architectures. Once all that is in place. KDE 3.4.1 will be uploaded, and the bug squishing on that will begin. I'm guessing a month or so before a fully working KDE 3.4.1 is in sid, give a couple of months/take a week.. ;)
In the meantime you can still use Alioth KDE 3.4.1 packages with sid and xorg (Yes, Really!). You need to delete all aspell and libjack packages from sid, and get libaspell and libjack from testing, then KDE will install without problems. And hold off on upgrading once you have something that works, unless you are prepared to sort out the dependency issues that are bound to arise
It's a valid concern, but I think one should think of this as a way to get people who otherwise wouldn't be able to move around much, to excercise their muscles more than they would have without this aid. Any workout counts, so I think for many this would be a good thing. Also one day it could possibly help permanently paralized to walk again, which would be a great thing in my opinion.
I think you misunderstand. Those are two seperate cases. In one case I slowly read through content, and thus move the mouse slowly. In my experience the mouse tends to drift off to the side after a while, thus the text suddenly shifts position without me wanting it. In the other case i just grap the scroll bar and move it all the way to one end, without looking at the content. For instance when you are editing some text and want to add some new text at the end.
I'd say that the drag area extends just under 2 inches out from the bar on my 19 inch monitor, which runs in 1280x1024. But to me any size is too small, and I think you just got used to a 'misfeature' in windows, so much so that now you can't live without it. I am used to not having it this way, so I hate the feature. We probably will never agree on whats the best solution. If only we could get a config option to turn off that behaviour, we would both be happy.
Oh forgot this..
Why is it annoying?
Because many times you will want to drag a page for a long time while reading or looking though some stuff. After a while you can't be expected to hold your precision with the pointer exactly to the small area in which the drag works. Eventually the pointer will venture out because you are not keeping an eye on what you are doing with it. So suddenly while you are reading something, the text jumps up to it's original position. Then you have to remove your attention from the material and focus on bringing the scrollbar under control. Totally annoying!
Another point. A lot of times on smaller scroll areas you just want to scroll all the way to the top or bottom. In all other OS's you can just click on the scrollbar and move the mouse very fast to the bottom of the screen and let go, and you know you will get the result you want. Not so in windows. Because you have to keep the mouse pointer in close proximity of the scrollbar for scrolling to work correctly you have to be very carefull about not making too erratic mouse movements. So it slows down the work yet again because you have to focus your attention on scrolling and not on the content you are looking at.
Fortunately edge dragging (on touch pads) and mouse wheels alleviate many of the problems with windows scroll bars. Otherwise I think I would go insane..
You are probably just trolling, but heck I'll bite this one.
Why oh why would you ever want this? The standard way of canceling a mouse drag action is to right click. That should be enought. And no other OS has this. That should give you some hint that it is a bad idea.
Hear hear!
This is somewhat akeen to the stupidest "feature" in Windows, when you are dragging a scrollbar and move the mouse too far away from the bar, it will jump back to it's original position. Fucking moronic.
Resticting mouse movement is bad.
libglu1-mesa conflicts with xlibmesa-glu IIRC.
You may not have a complete upgrade if you haven't seen this. The upgrade will hold back some packages that causes this conflict if you don't do anything manually. In that case you are probably still running xfree86 instead of xorg.
Or the packages may have already been rebuild. I can't check that right now though.
The changes has broken the experimental packages of KDE 3.4.1 on Alioth because of unfulfilled dependencies.
If you use those packages you should hold off with this upgrade for a while as it will cause many of the core KDE packages to uninstall breaking KDE completely.