Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Henderson Newsgroups: comp.lang.java.programmer Subject: Re: Arithmetic overflow checking Date: Fri, 22 Jul 2011 00:27:16 -0400 Organization: e1 Lines: 29 Message-ID: References: <015aeb15-57db-48ab-9cd4-77f8448b632f@w24g2000yqw.googlegroups.com> <2rydnez7l-H5BYnTnZ2dnUVZ_vGdnZ2d@earthlink.com> <9LWdnZH2hdfmyYvTnZ2dnUVZ_vidnZ2d@posted.palinacquisition> <1K2dnVVEK60FcoTTnZ2dnUVZ_hKdnZ2d@earthlink.com> <4e288eaa$0$316$14726298@news.sunsite.dk> NNTP-Posting-Host: h1MICDOSuUTFyvkTQ7BjNQ.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: WinVN 0.99.12z (x86 32bit) X-Notice: Filtered by postfilter v. 0.8.2 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:6394 On 21/07/2011 7:06 PM, Martin Gregorie wrote: > Agreed: apart from anything else you'd have problems using more than one > interactive app at a time on those tiny screens. In fact those early > smart phones had to have some rudimentary multitasking ability, at least > equivalent to what the early Macs could do, or the phone couldn't accept > an incoming call if its owner was using an app. A lot of phone apps save their exact state when you use the phone's menu button to close them and return to the phone's menus. The effect for many users is similar to true multitasking, in that they can leave work in progress in one app, switch to another, and return to the first afterward and continue where they left off. It's just they can't have a background job grinding away while they do something else; if they have, say, something rendering an animation and switch to another app the render makes no progress when they're not in the rendering app. I think later-generation phones are starting to introduce the ability to have daemon threads. One irritation with phone apps saving their state is that they can get wedged and be difficult to unwedge. The Safari browser on the iPhone is a frequent culprit. There's an obscure reset procedure for the iPhone that involves powering it off for 15 seconds and doing some magic dance, maybe not in that order, that will reset apps to their installed states. You lose work in progress but if Safari, or another app, got b0rked it will work again. Unfortunately you can't reset just the b0rked app. There's a still more severe reset that wipes the phone to factory state; if you do that, better have synched it with your iTunes or you've lost everything on the phone, possibly including paid apps.