home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.programmer
- Path: sparky!uunet!spool.mu.edu!wupost!darwin.sura.net!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!uchinews!ellis!sip1
- From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
- Subject: Re: Inline assembler code with GNU GCC
- Message-ID: <1992Sep12.022307.19408@midway.uchicago.edu>
- Keywords: GNU C++, assembler, inline
- Sender: news@uchinews.uchicago.edu (News System)
- Reply-To: sip1@midway.uchicago.edu
- Organization: Dept. of Econ., Univ. of Chicago
- References: <1992Sep10.121235.1891@fzi.de>
- Date: Sat, 12 Sep 1992 02:23:07 GMT
- Lines: 21
-
- In article <1992Sep10.121235.1891@fzi.de> fzi.de writes:
- >last week I tried to port an editor from DOS to OS/2. I got the following
- >problem: since the editor used the DOS mouse interface, which is accessible
- >through an interrupt call, I used inline assembler statements in the DOS C code.
- >When trying to compile this file with GCC, I got several error messages.
- >So, how can I in general use inline assembler statements when using GCC ?
- >And further, will the mouse interface still be accessible through that old
- >interrupt under OS/2, or will I have to reprogram the whole thing with
- >PM-calls?
-
- No, the mouse is supported using 16-bit VIO calls. You need to
- translate your DOS mouse interface to the OS/2 equivalent.
-
- These mouse calls are documented in most OS/2 1.x programming
- references.
-
- --
- Timothy F. Sipples | The OS/2 FREQ. ASKED QUESTIONS LIST is avail. from
- sip1@ellis.uchicago.edu | 128.123.35.151, anonymous ftp, in /pub/os2/all/faq.
- Dept. of Econ., Univ. | Or from LISTSERV@BLEKUL11.BITNET (send "HELP").
- of Chicago, 60637 | Family Values Means a Job
-