Xref: news-dnh.mv.net comp.os.msdos.djgpp:294
Path: news-dnh.mv.net!mv!news.sprintlink.net!pipex!sunic!sunic.sunet.se!news.uni-c.dk!diku.dk!terra
From: terra AT diku DOT dk (Morten Welinder)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: VOTE: CODE STANDARDS
Date: 9 Jun 1995 16:52:29 GMT
Organization: Department of Computer Science, U of Copenhagen
Lines: 22
Sender: terra AT tyr DOT diku DOT dk
References: <D9sABM DOT Hqw AT jade DOT mv DOT net> <3r3lc4$30a AT news DOT telebyte DOT com> <3r9d67$6j3 AT harbinger DOT cc DOT monash DOT edu DOT au>
Nntp-Posting-Host: odin.diku.dk
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

junaid AT barney DOT eng DOT monash DOT edu DOT au (Junaid A. Walker) writes:

>	As mensioned, the go32 sources are.....well....interesting
>to understand. There is some truth that go32 will go away in favour
>of cwsdpmi; one wonders exactly why go32 needed to be dropped
>and parts re-written.

If the last sentence is meant to imply that the commenting level
played any role whatsoever in that decision, well, it's wrong.
To reiterate:

1. DJGPP is a C-compiler and as such a competitor to several Borland
   products.  That makes severe restrictions on distribution of a
   part (like GO32) that is linked with Borland's libraries.

2. Providing one of four different environments for programs is a
   wrong design.  It didn't start out that way, but rather evolved.

3. GO32 was designed to host only one 32-bit program.  Nesting 
   used a lot of memory.

Morten