I see your point, but this will not solve the prime problem of providing maximal living space. A rigid set of concentric cylindrical shells, all rotating together about their common long axis (same angular velocity for all shells), does so admirably - you can have full Earth gravity at the outer shell, going down as you get closer to the main cylinder's axis. If you have a non-rigid set of shells (each shell rotating with a different angular velocity), you must have some sort of arrangement to keep the shells rotating smoothly past each other. Moving from one shell to another is much more difficult proposition, and God help the inhabitants if the "ball bearings" seize up... The rigid set of shells can solve the docking problem very nicely. Docking is always at the axis. Either your spacecraft match rotation with the space station and dock, or there is a counter-rotating docking station at the axis, which (after the spacecraft has undocked) speeds up in order to let the passengers cross into the space station. IIRC, the second choice is the one used by Heinlein, Clarke, and others. If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack. --Winston Churchill

Read Documentation???? What a novel idea :laugh: It's pretty obvious that the default thread affinity is to use the same processor the creation thread is using. Don't know how to get a list of processors or which one is being used by the main thread. DateTime seems to do very well at picking a thread that is idle to make its timing updates. So the recommended process produces wildly inaccurate results while the not recommended process seems to produce fairly accurate results. I'll stick with the not recommended process. PS Thanks for the link to the online documentation.

Michael Martin wrote: The other error he had was UKians when he meant to say, the rest of the world. True. When will the rest of the world wake up and realize the fastest changing value to the slowest in left to right order doesn't make sense... :-D We USA'ns do like to bury our heads in the sand. Long live the foot!(Ugh. Our CDE's marathon is measured in KM, cones in M and clearance in CM. Why use a rational measurement when the irrational ones work? Sort of.) Well, Celsius is based on impure water at sea-level! (Think of the accidents when distilled water is heated in the microwave and bursts into steam when sugar is added. Saw that one on Myth Busters. Would the rest of the world even know about M-B?)

Kent Sharkey wrote: iPod Touch ~~ iPad 2 Is that how we measure processing speed, these days? In that case, my EUR 150 android tab = 2 ipad 3s. How strange that 2 ipad 3s also = EUR 1200. I wanna be a eunuchs developer! Pass me a bread knife!

I remember investigating one application that tried to jump to an invalid location. That app was innocent. Some other code used COMMON to reach what happened to be that program's current memory location, re-wrote the computer instructions including the said jump statement. The app was just running it's instructions when all of a sudden it wasn't their instruction set anymore.

Sounds like it was written by someone who doesn't really know SQL. They are only worth keeping around if they can be trained to do it the right way. If they argue that their way is perfectly fine, then chuck them out the door. Just because the code works, it doesn't mean that it is good code.

It's a bit of a nothing article, short on concrete examples and basically boiling down to 'be consistent, use sensible names and don't comment when you don't need to'. Which I agree with, but it's so high level as to be meaningless. I don't agree that you should always Jdoc/Ndoc public methods; these go out of date as often as other comments and out of date comments are worse than none. They also take up space in the source file and make it harder to see the bits that actually do stuff. If the method has a meaningful name and so do its parameters then the documentation is superfluous. The exception to this is a library, where (i) the signature and therefore comment won't need to change, and (ii) it may be referenced from a release mode binary where parameter names are lost. I wouldn't put a space between a cast expression and the thing it's casting, either. The tight binding between those two things should be shown in layout, imo.

Sadly you took out the d@nish wrote: wohoo oo oo oo oo feature while fixing all the bugs. Bad developer! Bad! ;P

I'm on childish mood. So feeling grt :-D All the best, Dan

But why are they doing the mod operation? They're not using variables, so it would have been better to just say 1<<8. It's java so it's already stupid, but that just more or less confirms that it's stupid. In fact, why do the unnecessary shift left operation at all? They're just being ass-hats at this point. ".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 modified on Saturday, July 23, 2011 9:30 AM

Thanks to both of you even if only one of you sees it. Yes, you were first. Cudos.