From: "Alexei A. Frounze" Newsgroups: comp.os.msdos.djgpp Subject: Re: 3rd Try: Maybe an asm problem? (Problems linking) Date: Mon, 01 May 2000 21:29:14 +0400 Organization: MTU-Intel ISP Lines: 51 Message-ID: <390DBEEA.7C0F281@mtu-net.ru> References: <390D7DD9 DOT F55A5EF6 AT mtu-net DOT ru> <390DABE4 DOT 903187FC AT maths DOT unine DOT ch> NNTP-Posting-Host: ppp101-205.dialup.mtu-net.ru Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Trace: gavrilo.mtu.ru 957202350 52319 212.188.101.205 (1 May 2000 17:32:30 GMT) X-Complaints-To: usenet-abuse AT mtu DOT ru NNTP-Posting-Date: 1 May 2000 17:32:30 GMT X-Mailer: Mozilla 4.72 [en] (Win95; I) X-Accept-Language: en,ru To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Gautier wrote: > > > > __dpmi_yield is not for task switching, it's for releasing the current > > > time slice allotted by Windows (or any other multi-tasking scheduler). > > Alexei: > > > Just some kind of a synonym. :) > > Sorry to contradict, but the "task switching" jargon is for the user > choosing manually and delibarately a task to be foreground of his/her display. > It's rather an antonym! Sure I know difference current task for an OS and current task for a user. :) If a task/thread/process/whatever switch occurs after releasing the timeslice, is that antonym? > > Do you bother about that while you're programming? I.e. do you write a custom > > keyboard read function that calls that thing? > > In an OO environment that provides events like Turbovision, it suffices to > put a call to the "Release time slice" for the "idle event" case! I know that, if .HandleEvent(Event) encounters a null/empty Event (Event.What=evNothing or something like that) it calls .Idle. Parhaps TV has that call to Int 2f in the deeppest Idle procedure. > > Or maybe we all develop applications for background that should work and be > > invisible? I dboubt. :) > > Inexact: that "Release time slice" can act when your program is at foreground > and visible. It helps the background tasks to run faster! May be. > > How about old DOS programs? Are you sure all they release timeslice? > > Surely that if you unassemble a commercial DOS app. (e.g. DOS interactive > commands) you'll find plenty of them... *Commercial*... :) bye. Alexei A. Frounze ----------------------------------------- Homepage: http://alexfru.chat.ru Mirror: http://members.xoom.com/alexfru