Date: Wed, 26 May 1999 16:07:34 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Jeff Williams <jeffw AT darwin DOT sfbr DOT org>
cc: djgpp-workers AT delorie DOT com, frank AT tim DOT gerwinski DOT de
Subject: Re: __dpmi_yield()
In-Reply-To: <199905261223.HAA07125@darwin.sfbr.org>
Message-ID: <Pine.SUN.3.91.990526160503.23994B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 26 May 1999, Jeff Williams wrote:

> % gcc -c dpmi_yld.c
> % gcc dpmi_yld.o -o dpmi_yld.exe
> % dpmi_yld.exe
> 27
> 128
> 
> This is on a 386/387 notebook with MS-DOS 5.0, djgpp v2.02,
> cwsdpmi 0.90+ (r4), gcc 2.7.2.1, bash 1.14.7(1) r3 w/multibyte extension.

Thanks.

This is expected behavior: DOS is not a multitasking OS, so it doesn't 
hook Int 2Fh, and the call returns immediately with an error code.  Since 
there's no scheduler, there's no meaning to yielding the time slice in DOS.

Windows and Linux are another matter.