Modules· Home· Acronyms · AvantGo · Catalog Store · Content · Downloads · Feedback · Forums · Jargon · NukeONTD · Online Games · OurTube · PDF Manuals · PowerBlog · Private Messages · Recommend Us · RFCs · Stories Archive · TagCloud · Thriller · Top 10 · Topics · Your Account Who's OnlineThere are currently, 1080 guest(s) and 10 member(s) that are online. You are Anonymous user. You can register for free by clicking here OurTubeNukeONTD· 'Bling Ring's' Katie Ch.. · Meet Ahmed Angel: The .. · Hayden Christensen Pos.. · Kelly Rowland, Demi Lo.. · Emma Stone @ 2013 Peac.. · Bradley Cooper: 'Jane.. NukeTAGSLanguagesSelect Interface Language: | 1. [numerical analysis] Said of an algorithm or computational method that tends to blow up because of accumulated roundoff error or poor convergence properties. 2. [obs.] Software that bypasses the defined OS interfaces to do things (like screen, keyboard, and disk I/O) itself, often in a way that depends on the hardware of the machine it is running on or which is nonportable or incompatible with other pieces of software. In the MS-DOS world, there was a folk theorem (nearly true) to the effect that (owing to gross inadequacies and performance penalties in the OS interface) all interesting applications were ill-behaved. See also bare metal. Oppose well-behaved. See also mess-dos. 3. In modern usage, a program is called ill-behaved if it uses interfaces to the OS or other programs that are private, undocumented, or grossly non-portable. Another way to be ill-behaved is to use headers or files that are theoretically private to another application. |