delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2003/02/10/18:22:37

Date: Mon, 10 Feb 2003 18:22:22 -0500
Message-Id: <200302102322.h1ANMMA08187@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <3e482e8d_3@corp.newsgroups.com> (some.net@delorie.com)
Subject: Re: DJGPP design
References: <3e482e8d_3 AT corp DOT newsgroups DOT com>
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

> Does anyone (including DJ) know how the compiler was designed. I know
> parsers are designed with lexicon ggenerators. Since DOS isn't a "true" OS,
> is the compiler and preprocesser connected to system calls?

DOS is a true OS.  With DJGPP on top of it, it's even mostly
compatible with POSIX.  But that has nothing to do with the compiler.

The compiler is a stand-alone application that runs on a variety of
platforms, from MacOS to OS/2 to DOS, Unix, VMS, and Windows.  It uses
standard C runtime functions to interact with the operating system,
which makes it very portable.

As for the design of the compiler, that is independent of DJGPP and
better asked on the gcc discussion list (see http://gcc.gnu.org/).

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019