home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
TC4OS22.ZIP
/
TC4OS2.TXT
< prev
next >
Wrap
Text File
|
1989-02-27
|
2KB
|
47 lines
Copyright (C) 1988, 1989 by FreeLance Programming - All rights reserved.
Use Turbo C to write code for OS/2? Sure! The following restrictions
should be noted:
1) Many of the Turbo C library routines will NOT work (and some of them
will even cause unresolved external errors at link time). In general
you should use the OS/2 API calls rather than the Turbo C library
routines.
2) The replacement startup code has a hard-coded stack size (2.5k). If
you wish to change stack sizes, you will need to reassemble this module.
Dynamic stack size setting is *not* currently implemented.
3) No support is provided for the 80x87 or for Turbo C 2.0+'s graphics
capabilities.
4) Only the LARGE memory model is supported (though it is easy enough
to modify C0.ASM to change this).
5) You *must* use the OS/2 linker; TLINK will *not* work. See the
enclosed .CMD file for an example of a correct link.
6) For some reason, programs developed using this package will *not*
run correctly as BOUND executables. I will be looking into this
problem for a possible future enhancement.
A couple of short sample programs are provided that have been verified
to work with this (somewhat kludgy) setup. I developed this code only
to start playing with OS/2 while waiting for my MSC 5.1 package to
arrive, and I strongly recommend that if you are doing serious OS/2
development work that you purchase a language with real OS/2 support.
However, this module *will* let you write OS/2 programs using Turbo C
if you're so inclined. If there is any real interest in this package,
perhaps I'll develop replacement run-time routines for the Borland
provided DOS-only ones.
For questions, support, other OS/2 (or DOS) programs, and lots of
fine discussions (among other things), please call:
The Wizard's Workshop
300/1200/2400 - 24hrs
(301) - 322 - 8678