Date:	Thu, 14 Jul 94 08:55:42 EDT
From:	jcrigler AT iplmaster DOT orl DOT mmc DOT com (Jim Crigler)
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	(fwd) SIOD 3.0 for MS-DOS offer
Newsgroups:	comp.lang.scheme

Path: iplmail.orl.mmc.com!news.den.mmc.com!news.coop.net!cs.umd.edu!haven.umd.edu!news.umbc.edu!europa.eng.gtefsd.com!howland.reston.ans.net!swrinde!news.dell.com!tadpole.com!uunet!thehulk!mitech!gjc
Newsgroups: comp.lang.scheme
Subject: SIOD 3.0 for MS-DOS offer
Message-ID: <26 DOT 2e2326e9 AT mitech DOT com>
From: gjc AT mitech DOT com
Date: 12 Jul 94 23:27:36 EDT
Organization: Mitech Corporation, Acton MA
Lines: 27

There does seem to be demand for SIOD on good old vanilla MS-DOS,
so here is my offer:

- You choose the C compiler you want me to use,
  and buy a copy of it from your local store and mail it to me.

- You tell me what memory models you want things optimized for.

- I port the latest SIOD, add compile time switches for the optimizations
  and memory models you want.

- provide you with source and binaries on floppies.

- Then make the new source and the binaries available on the net,
  including the usual ms-dos binary archives and perhaps compuserve.

--------

I never bothered doing this before because the WINDOWS NT port was
already done with SIOD 3.0 and WIN32 exists for MS-WINDOWS on INTEL,
and I remember that a previous SIOD compiled and ran quite easily
for me a few years back using the microsoft C for MS-DOS.
And Chicago is around the corner which will change everything.
Otherwise I would have at least done a Windows 3.1 SDK build of SIOD.

However, there is the issue of these 'palm-top' computers.

- Raw text -