Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!rutgers!caip!brl-adm!brl-smoke!smoke!00R0DHESI%bsu.csnet@CSNET-RELAY.ARPA
From: 00R0DHESI%bsu.csnet@CSNET-RELAY.ARPA (Rahul Dhesi)
Newsgroups: net.lang.c
Subject: Re:  Tools/MS-DOS Development/BSD
Message-ID: <4368@brl-smoke.ARPA>
Date: Sun, 5-Oct-86 18:00:09 EDT
Article-I.D.: brl-smok.4368
Posted: Sun Oct  5 18:00:09 1986
Date-Received: Tue, 7-Oct-86 20:40:21 EDT
Sender: news@brl-smoke.ARPA
Lines: 16

Answering the query by Mark Donnelly (!ihnp4!motown!mergvax!donnelly):

If you are willing to do all program development in C, get Microsoft C
for the MS-DOS machine and just do program development in C on 4.1BSD.
Constantly refer to the Microsoft C manual and use only those features
that are portable to it.  The major difference will be in names of
flags to I/O routines and the unavailability of fork().  If you're
careful your C programs will recompile and run on the MS-DOS machine
without a hitch.  

Thomas Plum in "Reliable Data Structures in C" discusses the creation
of macros that let you write calls to I/O functions in a portable
manner.

                                Rahul Dhesi <dhesi%bsu@csnet-relay.ARPA>
                                !seismo!csnet-relay.ARPA!bsu!dhesi