| delorie.com/archives/browse.cgi | search |
| Date: | Tue, 2 May 2000 13:16:07 +0300 (IDT) |
| From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
| X-Sender: | eliz AT is |
| To: | Ian Chapman <ichapman AT nortelnetworks DOT com> |
| cc: | djgpp AT delorie DOT com |
| Subject: | Re: 3rd Try: Maybe an asm problem? (Problems linking) |
| In-Reply-To: | <390DBE89.2BA84777@nortelnetworks.com> |
| Message-ID: | <Pine.SUN.3.91.1000502131547.21668F-100000@is> |
| MIME-Version: | 1.0 |
| Reply-To: | djgpp AT delorie DOT com |
| Errors-To: | nobody AT delorie DOT com |
| X-Mailing-List: | djgpp AT delorie DOT com |
| X-Unsubscribes-To: | listserv AT delorie DOT com |
On Mon, 1 May 2000, Ian Chapman wrote: > this thread is a bit above the level that I think about. If I have: > cin >> buf; // do I need to worry about __dpmi_yield? If your program does this a lot, like most interactive programs do, then IMHO yes, you should worry about it. > I guess it should be used by people writing cin type functions not > users. You are right. Some library functions in DJGPP really do that for you. But if library functions don't do that, the application should.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |